[Koha] Continued koha-common Upgrade Challenges

[skaman.tx at gmail.com]

I am open to anything at this point.  The Debian 10 host is a VM.  I honestly have had no real exposure to docker containers but am fairly adept on Linux and in learning new systems, command line, scripting, etc.  I just need the koha instance to be stable and relatively simplistic to update.  I’ve been running this koha instance for well over a decade and this upgrade from 20.05.xx is the first “brick wall” we have encountered.  Can you first give me the benefits of running as a docker container and how updating would differ than using Debian apt packages?

 

Scott

 

From: Javi Legido <javi at legido.com> 
Sent: Wednesday, April 28, 2021 11:19 AM
To: skaman.tx at gmail.com
Cc: koha <koha at lists.katipo.co.nz>
Subject: Re: [Koha] Continued koha-common Upgrade Challenges

 

Hi there.

 

Not sure if in your scenario there's the option, but I would strongly recommend start using docker instead of installing packages.

 

If you agree with this approach let me know, I can give you some hints.

 

Cheers.

 

Javier

 

On Wed, 28 Apr 2021 at 17:55, <skaman.tx at gmail.com <mailto:skaman.tx at gmail.com> > wrote:

Our koha installation is on Debian 10.  I have previously engaged the list for upgrade challenges specifically related to the outcome of the Debian package koha-common upgrade scripts. We are stuck at koha-common version 20.05.xx at this point.  My latest attempt to upgrade to 20.11.04-1 resulted in the following three error messages.  Is there any way to manually alter the correct table(s) to fix the database issues? I'm not sure what the "Failed to enable unit" message means.

----------------------------
Setting up koha-common (20.11.04-1) ...
Installing new version of config file /etc/cron.daily/koha-common ...
Installing new version of config file /etc/init.d/koha-common ...
Installing new version of config file /etc/koha/SIPconfig.xml ...
Installing new version of config file /etc/koha/apache-shared-intranet-plack.conf ...
Installing new version of config file /etc/koha/apache-shared-intranet.conf ...
Installing new version of config file /etc/koha/apache-shared-opac.conf ...
Installing new version of config file /etc/koha/koha-conf-site.xml.in <http://koha-conf-site.xml.in>  ...
Installing new version of config file /etc/koha/log4perl-site.conf.in <http://log4perl-site.conf.in>  ...
Installing new version of config file /etc/koha/plack.psgi ...
Installing new version of config file /etc/koha/zebradb/etc/phrases-icu.xml ...
Installing new version of config file /etc/koha/zebradb/etc/word-phrase-utf.chr ...
Upgrading database schema for [database]
.......
Upgrade to 20.06.00.031 done [10:19:38]: Bug 22789 - Add non_priority column on reserves and old_reserves tables
DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE `items` ADD COLUMN `exclude_from_local_holds_priority` tinyint(1) default NULL AFTER `new_status`"] at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl <http://updatedatabase.pl>  line 22709.

DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE `deleteditems` ADD COLUMN `exclude_from_local_holds_priority` tinyint(1) default NULL AFTER new_status`"] at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl <http://updatedatabase.pl>  line 22715.
......
Failed to enable unit: Unit /run/systemd/generator.late/koha-common.service is transient or generated.

----------------------------

NOTE: When I then run "/usr/share/koha/bin/migration_tools/rebuild_zebra.pl <http://rebuild_zebra.pl>  -b -a -z" in this post-upgrade state I get the following error for each biblio record:


DBD::mysql::st execute failed: Unknown column 'me.exclude_from_local_holds_priority' in 'field list' [for Statement "SELECT `me`.`itemnumber`, `me`.`biblionumber`, `me`.`biblioitemnumber`, `me`.`barcode`, `me`.`dateaccessioned`, `me`.`booksellerid`, `me`.`homebranch`, `me`.`price`, `me`.`replacementprice`, `me`.`replacementpricedate`, `me`.`datelastborrowed`, `me`.`datelastseen`, `me`.`stack`, `me`.`notforloan`, `me`.`damaged`, `me`.`damaged_on`, `me`.`itemlost`, `me`.`itemlost_on`, `me`.`withdrawn`, `me`.`withdrawn_on`, `me`.`itemcallnumber`, `me`.`coded_location_qualifier`, `me`.`issues`, `me`.`renewals`, `me`.`reserves`, `me`.`restricted`, `me`.`itemnotes`, `me`.`itemnotes_nonpublic`, `me`.`holdingbranch`, `me`.`timestamp`, `me`.`location`, `me`.`permanent_location`, `me`.`onloan`, `me`.`cn_source`, `me`.`cn_sort`, `me`.`ccode`, `me`.`materials`, `me`.`uri`, `me`.`itype`, `me`.`more_subfields_xml`, `me`.`enumchron`, `me`.`copynumber`, `me`.`stocknumber`, `me`.`new_status`, `me`.`exclude_from_local_holds_priority` FROM `items` `me` WHERE ( `me`.`itemnumber` = ? )" with ParamValues: 0=1] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836.
error retrieving biblio 1 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl <http://rebuild_zebra.pl>  line 686.

Any help would be greatly appreciated.  I fear we are getting farther and farther behind on koha-common versions since we cannot seem to get past the database schema upgrade errors.

Scott Leafe
Scriptel Ministries
Houston, Texas

_______________________________________________

Koha mailing list  http://koha-community.org
Koha at lists.katipo.co.nz <mailto:Koha at lists.katipo.co.nz> 
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha