Hey Doug, I misspoke a bit below. My upgrade is from 20.06 to 20.11 and I am on Debian Stretch. The Koha update/upgrade gives me a fit. I've held back the koha-common update since 20.06 because it fails when updating the database schema during the package install and breaks Koha altogether. It appears the package installer does not do full checks of some of the config files when it is doing the database updates and fails when it hits a missing database column or the such. One thing I am finding on Koha upgrades in Debian is if you have consistently accepted the installed version of the config files when doing updates, the result is missing config information. For example, in koha-conf.xml I had a missing log4perl_conf entry that crashed the upgrade. This entry was apparently added in a prior upgrade, but I answered "Y" to keep the existing koha-conf.xml file all along so it was not added. I fixed that issue, but other database structure errors still persist when I try to upgrade to 20.11.
Note that I've even done a clean koha install of 20.11 on a clean install of Buster and tried importing the database from 19.05 into the clean install. I run koha-upgrade-schema on the imported database but still no dice. I still get some errors and Koha will not display any information even after reindexing in Zebra. I think it would be nice if the Debian package updates did some critical checks to ensure keeping the existing koha-conf.xml, or any other config files, will break koha in the end. Sorry if my mistake about going from 19.05 to 20.11 causes you any inconvenience. Our problems look similar in some ways and that is why I jumped in. I recall some database upgrade errors in Debian going from 19.05 to 20.06 but they did not tank Koha altogether. 20.06 to 20.11 though is another story. Scott -----Original Message----- From: Doug Dearden <[email protected]> Sent: Monday, February 22, 2021 4:05 PM To: [email protected] Cc: [email protected] Subject: RE: [Koha] Help debugging Internal Server Error Hey Scott, What version of Debian are you running? I updated my /etc/apt/sources.list.d/koha.list file to point to stable and my /etc/apt/sources.list file to point to buster and did the upgrades at the same time. A foolish move in retrospect, I think I should have upgraded to buster first and made sure everything worked there. Unless someone else on the list has an idea of why the upgrade isn't working I am going to have to remove 20.11/reinstall 19.05/restore the db and see what happens. Thanks, Doug -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, February 19, 2021 12:32 PM To: Doug Dearden <[email protected]>; 'Alvaro Cornejo' <[email protected]> Cc: [email protected] Subject: RE: [Koha] Help debugging Internal Server Error Doug, I would love to hear the same. I have been unsuccessfully fighting an upgrade from 19.05 to 20.11.x for two months now. All errors are missing SQL columns that are not fixed by koha-upgrade-schema. Just doing an upgrade using the Debian package manager kills Koha altogether. Hope someone can share this information. Scott -----Original Message----- From: Koha <[email protected]> On Behalf Of Doug Dearden Sent: Friday, February 19, 2021 1:22 PM To: Alvaro Cornejo <[email protected]> Cc: [email protected] Subject: Re: [Koha] Help debugging Internal Server Error Hey Everyone, Thank you Alvaro and Jonathan for your help, I wanted to report back that I got this fixed and what the problem was in case someone else runs into this. An error in the plack-opac-error.log appears, and the same warning appears when I did koha-rebuild-zebra with the –v option: DBD::mysql::st execute failed: Unknown column 'me.exclude_from_local_holds_priority' I created a new instance, and found that column in the items table on the new instance but not on the old instance. I added the column with the SQL command: ALTER TABLE items ADD exclude_from_local_holds_priority tinyint(1) and that fixed it. I’m not sure why koha-upgrade-schema didn’t fix this. I have another instance that we stopped using and combined with an existing one. I tried doing koha-remove, then koha-restore, the koha-upgrade-schema on that instance and it didn’t work. I am concerned that there may be other database alterations between version 19.05 and 20.11.02.000 that also didn’t make it into the database. I found a reference to database changes on the wiki but it ends in the 3.x series. How do I find out what other database schema changes have been implemented between 19.05 and 20.11.02.000? Thanks, Doug Dearden Director / Information Technology School for Advanced Research (SAR) PO Box 2188 / Santa Fe / NM / 87504-2188 505.954.7220 / www.sarweb.org<http://www.sarweb.org/> EXPLORING HUMANITY. UNDERSTANDING OUR WORLD. Receive the SAR monthly E-News: SIGN UP HERE <https://sarweb.org/about/e-news-signup/> _______________________________________________ Koha mailing list http://koha-community.org [email protected] Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org [email protected] Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
