[Koha] Database upgrade problems from KOHA 19.05 to KOHA 21.11

[Harald Schaefer]

¡Hola Tomas!

see below

Saludos, Harald

Am 01.04.22 um 17:57 schrieb Tomas Cohen Arazi:
> Those lines are only printed if it upgraded the db correctly. So it 
> doesn't really look like it stopped.
>
> What is pointing you to the conclusion something went wrong?

I have upgraded koha-common to version 21.11, the database upgrade stops 
after 21.05, it should run to 21.11.

In the KOHA error.log I see messages like

opac-MARCdetail.pl: Use of uninitialized value in concatenation (.) or 
string at /usr/share/koha
/opac/cgi-bin/opac/opac-MARCdetail.pl line 312.: 
/usr/share/koha/opac/cgi-bin/opac/opac-MARCdetail.pl

or

End of script output before headers: opac-detail.pl

which indicates to me that there are some errors


It seems that the not executed database upgrade scripts are in
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/db_revs

> Is it that Koha keeps prompting you too do an upgrade?
No, I would apreciate such a prompt
> If such is the case then it is a caching issue and Mason's advice 
> should fix it!
>
> El jue, 31 mar 2022 20:48, Harald Schaefer <fechsaer at gmail.com> escribió:
>
>     Thanks for the answer.
>
>     I omitted same parts of the test run, it ends with
>
>     Upgrade to 21.11.02.004  [17:49:53]: Bug 29943 - Fix typo in
>     NOTIFY_MANAGER notice
>     Upgrade to 21.11.03.000  [17:49:53]: Koha 21.11.03 release
>
>     KOHA 21.11.03 is the release I want to upgrade to
>
>     My question is:
>
>     Is it save to run
>
>          sudo perl
>     /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
>     <http://updatedatabase.pl>
>
>     to add the missing database steps from 21.05 to 21.11.
>
>     Regards Harald
>
>     Am 31.03.22 um 20:34 schrieb Katrin Fischer:
>     > Hi,
>     >
>     > actually the test run is the one that looks a little odd:
>     >
>     > Upgrade to 21.06.00.000  [17:49:33]: Increase DBRev for 21.06
>     >         Run, rabbit run. 
>     >        Dig that hole, forget the sun,
>     >        And when at last the work is done
>     >        Don't sit down it's time to dig another one.
>     >
>     > Is the first database change after the release of 21.05 and it
>     marks the
>     > begin of the development cycle.
>     >
>     > Upgrade to 21.05.00.000  [19:01:13]: Koha 21.05.00 release
>     >
>     > Is correct as the last update step for 21.05, a stable release.
>     >
>     > Hope this helps
>     >
>     > Katrin
>     >
>     > I am not sure what might have happened, maybe a difference in how
>     >
>     > On 31.03.22 12:15, Harald Schaefer wrote:
>     >> Dear all,
>     >>
>     >> now I am promoted from a plain KOHA user to the system
>     administrator
>     >> of the computer hosting a KOHA installation of a railway museum in
>     >> Germany.
>     >>
>     >> My first task was to upgrade the system from Ubuntu 16.04 to
>     20.04 and
>     >> upgrading the KOHA system. I have tried this first twice on
>     some local
>     >> copies. In the test runs the database upgrade works fine.
>     >>
>     >> In the update run of the production system it stops at this point:
>     >>
>     >> Upgrade to 20.12.00.049  [19:01:13]: Bug 28108 - Move action logs
>     >> 'SERIAL CLAIM' and 'ACQUISITION CLAIM' to a new 'CLAIMS' module
>     >> Upgrade to 20.12.00.050  [19:01:13]: Bug 28108 - Add new
>     >> systempreference OpacHiddenItemsHidesRecord
>     >> Upgrade to 21.05.00.000  [19:01:13]: Koha 21.05.00 release
>     >>
>     >> Log started: 2022-03-29  19:04:34 # some other program
>     >>
>     >> In thetest runs it continues
>     >>
>     >> Upgrade to 21.05.00.000  [17:49:33]: Koha 21.05.00 release
>     >> Upgrade to 21.06.00.000  [17:49:33]: Increase DBRev for 21.06
>     >>         Run, rabbit run. 
>     >>        Dig that hole, forget the sun,
>     >>        And when at last the work is done
>     >>        Don't sit down it's time to dig another one.
>     >>
>     >> The rabbitmq log show these entries for the time
>     >>
>     >> 2022-03-29 19:00:36.018 [info] <0.595.0> started TCP listener on
>     >> [::]:5672
>     >> 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step
>     >> cluster_name defined by app rabbit
>     >> 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step
>     >> direct_client defined by app rabbit
>     >> 2022-03-29 19:00:36.158 [notice] <0.103.0> Changed loghwm of
>     >> /var/log/rabbitmq/rabbit at tools.log to 50
>     >> 2022-03-29 19:00:36.496 [info] <0.8.0> Server startup complete; 0
>     >> plugins started.
>     >> 2022-03-29 19:03:25.195 [info] <0.777.0> rabbit_stomp: default user
>     >> 'guest' enabled
>     >> 2022-03-29 19:03:25.281 [info] <0.793.0> started STOMP TCP
>     listener on
>     >> [::]:61613
>     >> 2022-03-29 19:03:25.329 [info] <0.765.0> Plugins changed; enabled
>     >> [amqp_client,rabbitmq_stomp]
>     >> 2022-03-29 19:03:27.678 [info] <0.800.0> RabbitMQ is asked to
>     stop...
>     >>
>     >> Is there any way to continue the database upgrade? I have other
>     >> applications running on the system and I do not want to start the
>     >> complete upgrade process again.
>     >>
>     >> It seems that the not executed scripts are in
>     >> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/db_revs
>     >>
>     >> Basically the upgraded KOHA is running.
>     >>
>     >> Best regards Harald
>     >>
>     >>
>     >>
>     >> _______________________________________________
>     >>
>     >> Koha mailing list http://koha-community.org
>     >> Koha at lists.katipo.co.nz
>     >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>     > _______________________________________________
>     >
>     > Koha mailing list http://koha-community.org
>     > Koha at lists.katipo.co.nz
>     > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>     _______________________________________________
>
>     Koha mailing list http://koha-community.org
>     Koha at lists.katipo.co.nz
>     Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>