[Koha] upgrade of Koha from 22.05.19.000 to 22.05.20.000 required Zebra to be started manually or no search in OPAC - typo

[Dwight Walker]

I meant to say:

When I first upgraded in About tab on console it said Zebra was not
running not Zoha.

-- 
Dwight Walker
WWWalker Web Development Pty Ltd
https://wwwalker.com.au

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] upgrade of Koha from 22.05.19.000 to 22.05.20.000 required Zebra to be started manually or no search in OPAC

[Dwight Walker]

After I upgraded Koha from 22.05.19.000 to 22.05.20.000 on Debian 11 using

apt-get update; apt-get upgrade

I had to start Zebra manually or there was no searching on items in OPAC.

When I first upgraded in About tab on console it said Zoha was not running.

Here is how I started Zebra:

koha-list

koha-zebra --start 
Zebra running for 

-- 
Dwight Walker
WWWalker Web Development Pty Ltd
https://wwwalker.com.au

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Database discrepancy flagged after Koha upgrade

[City & Guilds of London Art School Admin]

Hello,

Platform: Ubuntu 20.04.6 LTS
DB: 10.3.38-MariaDB
Koha Version: 23.11

Since the most recent upgrade (using the package manager) from 23.05.x to
23.11.00, the following is returned in *About Koha -> System Information*

==

Data problems

Some of your tables have problems with their auto_increment values which
may lead to data loss.

You should not ignore this warning.

The problem is that InnoDB does not keep auto_increment across SQL server
restarts (it is only set in memory). So on server startup the
auto_increment values are set to max(table.id)+1.

To know how to avoid this problem see the related wiki page: DBMS auto
increment fix
Problems found
Bibliographic records

The following IDs exist in both tables biblio and deletedbiblioitems:

2 , 3 , 4

==

Note that the fix here:
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix has been
implemented since we started with Koha, and that the five tests for data
corruption documented there return empty sets. The mysql error.log reports
no issues with parsing the bespoke init file etc.

Investigating further I see that indeed:

> select biblionumber, timestamp from deletedbiblioitems where biblionumber
<= '8';
+--+-+
| biblionumber | timestamp   |
+--+-+
|1 | 2023-01-13 11:00:38 |
|2 | 2021-06-09 14:06:34 |
|3 | 2021-06-09 14:06:52 |
|4 | 2021-06-09 14:06:57 |
|5 | 2021-06-09 14:07:00 |
|6 | 2021-06-09 14:07:06 |
|7 | 2021-06-09 14:07:10 |
|8 | 2021-06-09 14:07:13 |
+--+-+
8 rows in set (0.000 sec)

Whereas:

> select biblionumber, timestamp from biblio where biblionumber <= '8';
+--+-+
| biblionumber | timestamp   |
+--+-+
|2 | 2021-11-04 16:32:46 |
|3 | 2022-01-17 16:50:10 |
|4 | 2022-08-02 16:00:02 |
+--+-+
3 rows in set (0.001 sec)

Also:

> select biblionumber, timestamp from deletedbiblio where biblionumber <=
'8';
+--+-+
| biblionumber | timestamp   |
+--+-+
|1 | 2023-01-13 11:00:39 |
|5 | 2021-06-09 14:07:02 |
|6 | 2021-06-09 14:07:07 |
|7 | 2021-06-09 14:07:12 |
|8 | 2021-06-09 14:07:14 |
+--+-+
5 rows in set (0.000 sec)

Correct me if I'm wrong, but my understanding is that Koha row counts
should *always* be identical for the pair of tables: *biblio* and
*biblioitems*, and also be identical for the pair *deletedbiblio* and
*deletedbiblioitems*, since the latter is copied from the former. However,
we have:

> select count(*) from biblio;
+--+
| count(*) |
+--+
|11508 |
+--+
1 row in set (0.006 sec)

> select count(*) from biblioitems;
+--+
| count(*) |
+--+
|11508 |
+--+
1 row in set (0.033 sec)

> select count(*) from deletedbiblioitems;
+--+
| count(*) |
+--+
|15777 |
+--+
1 row in set (0.072 sec)

> select count(*) from deletedbiblio;
+--+
| count(*) |
+--+
|15774 |
+--+
1 row in set (0.011 sec)

Also, I was able to ascertain from backups that this discrepancy went back
some way - at least till mid October '23 (which as as far back as our
backups go), however, Koha did not report on it till after the most recent
upgrade from 23.05 to 23.11.00.

While this is easy enough to "solve" by removing records 2 - 4 from
*deletedbiblioitems*, I have the following questions:


*1.* If I run a query modeled on the existing queries for data corruption
in the linked wiki page, unsurprisingly I get:

> SELECT b.biblionumber   FROM biblio bJOIN deletedbiblioitems dbON
b.biblionumber=db.biblionumber;
+--+
| biblionumber |
+--+
|2 |
|3 |
|4 |
+--+
3 rows in set (0.000 sec)

So I'm wondering if the documented fix needs updating since it was last
reviewed (11th December 2020). My guess is that an additional corruption
test comparing *deletedbiblio* and *deletedbiblioitems*, and something like
the below may be needed, but I would prefer someone a *lot* more
knowledgeable about SQL (and Koha) to give their input, since my SQL skills
are pretty basic:

SET @new_AI_deletedbiblio = ( SELECT GREATEST( IFNULL( ( SELECT
MAX(biblioitemnumber) FROM deletedbiblio ), 0 ), IFNULL( ( SELECT
MAX(biblioitemnumber) FROM deletedbiblioitems ), 0 ) ) + 1 );
SET @sql = CONCAT( 'ALTER TABLE deletedbiblio AUTO_INCREMENT = ',
@new_AI_deletedbiblio );
PREPARE st FROM @sql;
EXECUTE st;

2. Although I can only check actual backups of the db back to mid October,
it seems logical that this error has always existed since we got beyond 4
deleted records (presumably June 2021). So I'm 

Re: [Koha] Upgrade question: 22.05 -> 23.05 better directly or via 22.11?

[Katrin Fischer]

Hi Anke,

assuming you will do a test run of the update anyway, I don't think
there is an advantage in updating to 22.05 first. It's very common to
jump over multiple versions and you should always end up with the exact
same database structure, no matter where you are coming from.

Hope this helps,

Katrin

On 20.07.23 10:39, Bruns, Anke wrote:

Hi all,

we are considering an upgrade from 22.05 to 23.05 - in your experience would
it be good to upgrade directly or to go first to 22.11 and then from there
to 23.05?

Thanks and best regards,
Anke


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade question: 22.05 -> 23.05 better directly or via 22.11?

[Nicolas Legrand]

Hey,

Le jeu. 20 juil. 2023 à 10:40, Bruns, Anke  a écrit :

> Hi all,
>
> we are considering an upgrade from 22.05 to 23.05 - in your experience
> would
> it be good to upgrade directly or to go first to 22.11 and then from there
> to 23.05?
>

I usually find it pretty straightforward to jump versions while upgrading.
We do this because we have quite a lot of plugins to adapt, so we roughly
update once per year. We plan to update from 21.11 to either 23.05 or
23.11. So far, we haven't encountered many issues (we use aptitude to avoid
conflicts and add an encryption_key entry to koha-conf.xml; see
https://lists.katipo.co.nz/public/koha/2022-June/058016.html). The rest
involves checking the homebrew plugins for changes in the Koha libraries.

have a great day,

-- 
Nicolas
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade question: 22.05 -> 23.05 better directly or via 22.11?

[Bruns, Anke]

Hi all,

we are considering an upgrade from 22.05 to 23.05 - in your experience would
it be good to upgrade directly or to go first to 22.11 and then from there
to 23.05?

Thanks and best regards,
Anke

-- 
Anke Bruns M.A. (LIS)
Arbeitsgruppe "Anwendungs- und Informationssysteme"
E-Mail: anke.br...@gwdg.de
-
Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG)
Burckhardtweg 4, 37077 Göttingen, URL: https://gwdg.de

Support: Tel.: +49 551 39-3, URL: https://gwdg.de/support
Sekretariat: Tel.: +49 551 39-30001, E-Mail: g...@gwdg.de 

Geschäftsführer: Prof. Dr. Ramin Yahyapour
Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger
Sitz der Gesellschaft: Göttingen
Registergericht: Göttingen, Handelsregister-Nr. B 598
-
Zertifiziert nach ISO 9001 und ISO 27001
-

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha Upgrade to 23.05.00.002 Error

[Sami M. Rasheed]

Dear All,
Hi,
While I am upgrading Koha to 23.05.00.002, I have an error:
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate key name 
'illrequests_bibfk' at /usr/share/koha/lib/C4/Installer.pm line 741

I use Ubuntu 20.04koha 23.05

Thanks.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade 22.11.6 to 23.5.00 upgrade-schema error

[MASTeR Library]

It working,
Thanks you Jonathan and all supports .

On Wed, 7 Jun 2023, 12:48 pm Jonathan Druart, <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hey, put a proper key there! Not "__ENCRYPTION_KEY__"!
> It can be generated using the following command `pwgen 32`
>
> Le mer. 7 juin 2023 à 07:41, Сычев Игорь Алексеевич  a écrit :
>
> > Hi!
> >
> > I added the lines:
> >  
> >  __ENCRYPTION_KEY__
> >
> > The update went through without a problem.
> >
> > https://github.com/Koha-Community/Koha/blob/master/etc/koha-conf.xml
> >
> > Good Luck!
> >
> > Igor A. Sychev
> > Tomsk Polytechnic University
> > https://lib.tpu.ru
> >
> >
> > ___
> >
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade 22.11.6 to 23.5.00 upgrade-schema error

[Jonathan Druart]

Hey, put a proper key there! Not "__ENCRYPTION_KEY__"!
It can be generated using the following command `pwgen 32`

Le mer. 7 juin 2023 à 07:41, Сычев Игорь Алексеевич  a écrit :

> Hi!
>
> I added the lines:
>  
>  __ENCRYPTION_KEY__
>
> The update went through without a problem.
>
> https://github.com/Koha-Community/Koha/blob/master/etc/koha-conf.xml
>
> Good Luck!
>
> Igor A. Sychev
> Tomsk Polytechnic University
> https://lib.tpu.ru
>
>
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade 22.11.6 to 23.5.00 upgrade-schema error

[Сычев Игорь Алексеевич]

Hi!

I added the lines:
 
 __ENCRYPTION_KEY__

The update went through without a problem.

https://github.com/Koha-Community/Koha/blob/master/etc/koha-conf.xml

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha upgrade 22.11.6 to 23.5.00 upgrade-schema error

[MASTeR Library]

Hi All

Just upgraded tonight from Koha 212.11.06.000 to 23.05.00
That all went fine.

The About Koha page now says:
"Warning:


   - Upgrade to 22.12.00.041 [09:43:21]: Bug 30649 - Increase the vendor
   EDI account password field to 256 characters
   ERROR: Exception 'Koha::Exceptions::MissingParameter' thrown 'No
   encryption_key in koha-conf.xml'

Please help.

 Thanking you..

Librarian,
MAMCET 
Trichy-Chennai Trunk Road,
Siruganur, Tiruchirappalli-621 105.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] upgrade error running koha-upgrade-schema

[Paulo Neto]

Hello Jonathan,

Thank you for the quick reply.

The problem was the table engine used, that was diferent on the two tables. For 
the table authorised_values i had myisam and for illrequests i had InnoDB

In a situation like that you cant create foreign keys between columns of one 
table, referencing another table.

Changing the database engine of the authorised_values to InnoDB did the trick 
and now i’ve upgraded the database schema sucessfully.

This can help other people in similar situations because its not na obvious 
data integrity situation.

Best regards,

Paulo Neto

De: Jonathan Druart 
mailto:jonathan.dru...@bugs.koha-community.org>>
Enviada: 6 de junho de 2023 11:06
Para: Paulo Neto mailto:pn...@dgadr.pt>>
Cc: koha mailto:koha@lists.katipo.co.nz>>
Assunto: Re: [Koha] upgrade error running koha-upgrade-schema

Hi Paulo,
You have values in illrequests.illrequests_safk that are not defined in the 
authorised_values values.
Regards,
Jonathan

Le mar. 6 juin 2023 à 11:20, Paulo Neto mailto:pn...@dgadr.pt>> 
a écrit :
Hello all,

I've been trying to upgrade my koha 18.11 to version 22.11.

When i run the comand koha-upgrade-schema to upgrade the database schema i am 
getting this error:

" UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't create table 
`koha_dgadr`.`illrequests` (errno: 150 "Foreign key constraint is incorrectly 
formed")  at /usr/share/perl5/DBIx/Class/Schema.pm line 1118 "

This is happening on 18.12.00.016 step list in da script 
updatedatabase.pl<http://updatedatabase.pl> (line17406) Corresponding to this 
line of code, in my case the  illrequests_safk doesnt existe before running the 
script:

if ( !foreign_key_exists( 'illrequests', 'illrequests_safk' ) ) {
$dbh->do( "ALTER TABLE illrequests ADD CONSTRAINT illrequests_safk 
FOREIGN KEY (status_alias) REFERENCES authorised_values(authorised_value) ON 
UPDATE CASCADE ON DELETE SET NULL" );
}

I do have some equal values for the column authorised_value on the table 
authorised_value and i think its probably the reason it cant create the foreign 
key on the table illrequests,

Is there a way to correct this?

Yours sincerely,

Paulo Neto
___

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

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] upgrade error running koha-upgrade-schema

[Jonathan Druart]

Hi Paulo,
You have values in illrequests.illrequests_safk that are not defined in the
authorised_values values.
Regards,
Jonathan

Le mar. 6 juin 2023 à 11:20, Paulo Neto  a écrit :

> Hello all,
>
> I've been trying to upgrade my koha 18.11 to version 22.11.
>
> When i run the comand koha-upgrade-schema to upgrade the database schema i
> am getting this error:
>
> " UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't create table
> `koha_dgadr`.`illrequests` (errno: 150 "Foreign key constraint is
> incorrectly formed")  at /usr/share/perl5/DBIx/Class/Schema.pm line 1118 "
>
> This is happening on 18.12.00.016 step list in da script updatedatabase.pl
> (line17406) Corresponding to this line of code, in my case the
> illrequests_safk doesnt existe before running the script:
>
> if ( !foreign_key_exists( 'illrequests', 'illrequests_safk' ) ) {
> $dbh->do( "ALTER TABLE illrequests ADD CONSTRAINT illrequests_safk
> FOREIGN KEY (status_alias) REFERENCES authorised_values(authorised_value)
> ON UPDATE CASCADE ON DELETE SET NULL" );
> }
>
> I do have some equal values for the column authorised_value on the table
> authorised_value and i think its probably the reason it cant create the
> foreign key on the table illrequests,
>
> Is there a way to correct this?
>
> Yours sincerely,
>
> Paulo Neto
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] upgrade error running koha-upgrade-schema

[Paulo Neto]

Hello all,

I've been trying to upgrade my koha 18.11 to version 22.11.

When i run the comand koha-upgrade-schema to upgrade the database schema i am 
getting this error:

" UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't create table 
`koha_dgadr`.`illrequests` (errno: 150 "Foreign key constraint is incorrectly 
formed")  at /usr/share/perl5/DBIx/Class/Schema.pm line 1118 "

This is happening on 18.12.00.016 step list in da script updatedatabase.pl 
(line17406) Corresponding to this line of code, in my case the  
illrequests_safk doesnt existe before running the script:

if ( !foreign_key_exists( 'illrequests', 'illrequests_safk' ) ) {
$dbh->do( "ALTER TABLE illrequests ADD CONSTRAINT illrequests_safk 
FOREIGN KEY (status_alias) REFERENCES authorised_values(authorised_value) ON 
UPDATE CASCADE ON DELETE SET NULL" );
}

I do have some equal values for the column authorised_value on the table 
authorised_value and i think its probably the reason it cant create the foreign 
key on the table illrequests,

Is there a way to correct this?

Yours sincerely,

Paulo Neto
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] koha-upgrade-schema

[Jonathan Druart]

Hi,
I've reported the problem on bug 30649.
You should edit the $KOHA_CONF file and add a new encryption_key entry with
a key (that can be generated with `pwgen 32`).

Le lun. 5 juin 2023 à 05:47, Сычев Игорь Алексеевич  a écrit :

> Hello!
>
> Koha 23.05
> After the update.
> How to fix the error?
>
> root@koha2:~# koha-upgrade-schema lib
> Upgrading database schema for lib
> Upgrade to 22.12.00.041  [09:37:28]: Bug 30649 - Increase the vendor EDI
> account password field to 256 characters
> ERROR - Exception 'Koha::Exceptions::MissingParameter' thrown 'No
> encryption_key in koha-conf.xml'
>
> Good Luck!
>
> Igor A. Sychev
> Tomsk Polytechnic University
> https://lib.tpu.ru<https://lib.tpu.ru/>
>
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] koha-upgrade-schema

[Сычев Игорь Алексеевич]

Hello!

Koha 23.05
After the update.
How to fix the error?

root@koha2:~# koha-upgrade-schema lib
Upgrading database schema for lib
Upgrade to 22.12.00.041  [09:37:28]: Bug 30649 - Increase the vendor EDI 
account password field to 256 characters
ERROR - Exception 'Koha::Exceptions::MissingParameter' thrown 'No 
encryption_key in koha-conf.xml'

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru<https://lib.tpu.ru/>

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade error

[Mason James]

hi folks

the new package should fix this problem 


On 30/05/23 12:23 am, Tomas Cohen Arazi wrote:

We are about to roll a new package with that fixed. Thanks for reporting.

El lun, 29 may 2023 a las 8:11, Daniel F. Twum ()
escribió:








 Upgrade to 22.11.05.010 [10:48:17]: Bug 33489 - Add indices to
default patron search fields
 ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed:
BLOB/TEXT column 'middle_name' used in key specification without a key
length at /usr/share/koha/lib/C4/Installer.pm line 743



--
8181 Robinson Jefferson Drive
APT 410
Elkridge, Maryland 21075-7271
USA

1 (404) 369-3966

--


http://www.mobilelinux.net





___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha






___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade error

[Tomas Cohen Arazi]

We are about to roll a new package with that fixed. Thanks for reporting.

El lun, 29 may 2023 a las 8:11, Daniel F. Twum ()
escribió:

>
>
>
>
>
>
> Upgrade to 22.11.05.010 [10:48:17]: Bug 33489 - Add indices to
> default patron search fields
> ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed:
> BLOB/TEXT column 'middle_name' used in key specification without a key
> length at /usr/share/koha/lib/C4/Installer.pm line 743
>
>
>
> --
> 8181 Robinson Jefferson Drive
> APT 410
> Elkridge, Maryland 21075-7271
> USA
>
> 1 (404) 369-3966
>
> --
>
>
> http://www.mobilelinux.net
>
>
>
>
>
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>


-- 
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha upgrade error

[Daniel F. Twum]

Upgrade to 22.11.05.010 [10:48:17]: Bug 33489 - Add indices to default 
patron search fields
ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: BLOB/TEXT 
column 'middle_name' used in key specification without a key length at 
/usr/share/koha/lib/C4/Installer.pm line 743



--
8181 Robinson Jefferson Drive 
APT 410
Elkridge, Maryland 21075-7271
USA

1 (404) 369-3966

--


http://www.mobilelinux.net





___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] KOHA upgrade from V20.05 to V22.11 (Browse by last name error)

[Jonathan Druart]

This has been raised on IRC yesterday, please have a look at the log:
https://irc.koha-community.org/koha/2023-04-26#i_2483964
The problem is some borrowers.date_renewed that would be -00-00

Le mer. 26 avr. 2023 à 06:09, zen zenitram  a écrit :
>
> Hello
>
> I finished upgrading koha version 20.05 to version 22.11, but when i tried
> to search for patron  by clicking the letter of the last name this message
> shows ( Something went wrong when loading table . 500 Internal server
> error. then lots of " Month out of range message".
>
> How do i fix this kind of error?
>
> I tried to overwrite the patron by uploading new list of patrons but
> nothing change.
>
> Thank you!
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] KOHA upgrade from V20.05 to V22.11 (Browse by last name error)

[zen zenitram]

Hello

I finished upgrading koha version 20.05 to version 22.11, but when i tried
to search for patron  by clicking the letter of the last name this message
shows ( Something went wrong when loading table . 500 Internal server
error. then lots of " Month out of range message".

How do i fix this kind of error?

I tried to overwrite the patron by uploading new list of patrons but
nothing change.

Thank you!
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade Schema Issue

[Mason James]

hi Taimoor,

what koha version are you upgrading from/to?


what does the following command say?

$ sudo koha-mysql library -e  ' select value from systempreferences where variable = 
"version" '
++
| value  |
++
| 21.1117000 |  <
++



On 12/04/23 3:18 pm, Taimoor Memon wrote:

Hello everyone,
I'm facing an issue in the upgradation of Koha, terminal is executing the
following error:

DBD::mysql::st execute failed: Table 'koha_library.systempreferences'
doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::st execute failed: Table 'koha_library.systempreferences'
doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152.
Use of uninitialized value in numeric lt (<) at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 78.
DBD::mysql::db do failed: Table 'koha_library.bookshelf' doesn't exist at
/usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.shelfcontents' doesn't exist
at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't
exist at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't
exist at /usr/share/koha/lib/Koha/Database.pm line 152.
Undefined subroutine ::DropAllForeignKeys called at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 86.




___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade Schema Issue

[Taimoor Memon]

Hello everyone,
I'm facing an issue in the upgradation of Koha, terminal is executing the
following error:

DBD::mysql::st execute failed: Table 'koha_library.systempreferences'
doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::st execute failed: Table 'koha_library.systempreferences'
doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152.
Use of uninitialized value in numeric lt (<) at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 78.
DBD::mysql::db do failed: Table 'koha_library.bookshelf' doesn't exist at
/usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.shelfcontents' doesn't exist
at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't
exist at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't
exist at /usr/share/koha/lib/Koha/Database.pm line 152.
Undefined subroutine ::DropAllForeignKeys called at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 86.

-- 
Regards:


*Irfan Taimoor Memon*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade KOHA 20.05 to KOHA 21.11

[zen zenitram]

good day!

I encountered this

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change
column 'borrowernumber': used in a foreign key constraint 'issues_ibfk_1'
at /usr/share/koha/lib/C4/Installer.pm line 739


Thank you!
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Bruce A. Metcalf]

On 3/15/23 23:44, Mason James wrote:

On 15/03/23 11:22 am, Bruce A. Metcalf wrote:

On 3/14/23 01:05, Mason James wrote:

On 14/03/23 5:53 pm, Mason James wrote:

On 13/03/23 5:13 am, Bruce A. Metcalf wrote:

On 3/12/23 10:34, Katrin Fischer wrote:



There is a log3perl.conf file in my /etc/koha/sites/(instance)/ 
directory, and it looks just like the one suggested.


did you restart koha? - specifically after you upgraded?

/etc/init.d/koha-common restart



No change.



did the following error stop?

AH01215: Configuration not defined at 
/usr/share/perl5/Log/Log4perl/Config.pm line 579.: 
/usr/share/koha/intranet/cgi-bin/mainpage.pl



I don't see that error.

Line 579 of the first file is:

die "Configuration not defined" unless defined $config;

Two lines earlier, I see:

my($config) = @_;

Which suggests to me that something is missing, but I don't know the 
language so can't tell what.




do you have new errors in your log files?



The only error I see in the logs right now is:

root@store:/var/log/koha/library# tail worker-output.log
Error connecting to localhost:61613: Connection refused at
/usr/share/perl5/Net/Stomp.pm line 26.
Failed to connect: Error connecting to localhost:61613: Connection
refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at
/usr/share/perl5/Net/Stomp.pm line 26.
Cannot connect to the message broker, the jobs will be processed anyway
(Failed to connect: Error connecting to localhost:61613: Connection
refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at
/usr/share/perl5/Net/Stomp.pm line 27.
) at /usr/share/koha/bin/background_jobs_worker.pl line 28.

Which doesn't mean anything to me, and without a date stamp, I'm not
even sure when it showed up.

At least this feels like we're getting close.

Thanks all,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Mason James]

On 15/03/23 11:22 am, Bruce A. Metcalf wrote:

On 3/14/23 01:05, Mason James wrote:

On 14/03/23 5:53 pm, Mason James wrote:

On 13/03/23 5:13 am, Bruce A. Metcalf wrote:

On 3/12/23 10:34, Katrin Fischer wrote:



There is a log3perl.conf file in my /etc/koha/sites/(instance)/ directory, and 
it looks just like the one suggested.

Perhaps it's something else. Any other ideas?



hi Bruce

did you restart koha? - specifically after you upgraded?

  /etc/init.d/koha-common restart


did the following error stop?
 
  AH01215: Configuration not defined at /usr/share/perl5/Log/Log4perl/Config.pm line 579.: /usr/share/koha/intranet/cgi-bin/mainpage.pl



do you have new errors in your log files?
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Mason James]

On 15/03/23 11:22 am, Bruce A. Metcalf wrote:

On 3/14/23 01:05, Mason James wrote:

On 14/03/23 5:53 pm, Mason James wrote:

On 13/03/23 5:13 am, Bruce A. Metcalf wrote:

On 3/12/23 10:34, Katrin Fischer wrote:



There is a log3perl.conf file in my /etc/koha/sites/(instance)/ directory, and 
it looks just like the one suggested.

Perhaps it's something else. Any other ideas?



hi Bruce

did you restart koha? - specifically after you upgraded?

  /etc/init.d/koha-common restart


did the following error stop?
 
  AH01215: Configuration not defined at /usr/share/perl5/Log/Log4perl/Config.pm line 579.: /usr/share/koha/intranet/cgi-bin/mainpage.pl



do you have new errors in your log files?
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] KOHA Upgrade fails from v20.05 to v22.11

[Katrin Fischer]

Hi,

all I found was your bug report :(

*Bug 32762*
 -
Duplicate entry '10434' for key 'PRIMARY' at
/usr/share/koha/lib/C4/Installer.pm line 739

Maybe someone else has an idea?

Katrin

On 13.03.23 06:16, zen zenitram wrote:

Good day!


Anyone encountered this kind of error while upgrading KOHA?

Upgrading database schema for lrc
Upgrade to 22.06.00.063  [05:39:06]: Bug 31569
  -
Add primary key for import_biblios
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
entry '11545' for key 'import_biblios.PRIMARY' at
/usr/share/koha/lib/C4/Installer.pm line 739

and this one

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
entry '24064' for key 'import_biblios.import_biblios_ibfk_1' at
/usr/share/koha/lib/C4/Installer.pm line 739


need help with this.


THank you!
___

Koha mailing listhttp://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Bruce A. Metcalf]

On 3/14/23 01:05, Mason James wrote:

On 14/03/23 5:53 pm, Mason James wrote:

On 13/03/23 5:13 am, Bruce A. Metcalf wrote:

On 3/12/23 10:34, Katrin Fischer wrote:

To review, an upgrade to 21.11 (OldOldStable) and Debian 10 results 
in [Internal Server Error] screens.


the short version is that your koha instance is probably missing a 
log4perl.conf file


a simple way to correct the problem would be to create a new instance, 
then copy the missing log4perl.conf file from the new instance



I'll check to see if I have room for this.


here is an example of a log4perl.conf file - please search/replace it, 
as required :)


# cat /etc/koha/sites/tp3/log4perl.conf



I had to create the tp3 directory to do this. Now the system reports two 
instances, my original and tp3. Does this sound wrong?


There is a log3perl.conf file in my /etc/koha/sites/(instance)/ 
directory, and it looks just like the one suggested.


Perhaps it's something else. Any other ideas?

Cheers,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Mason James]

On 14/03/23 5:53 pm, Mason James wrote:

On 13/03/23 5:13 am, Bruce A. Metcalf wrote:

On 3/12/23 10:34, Katrin Fischer wrote:


the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.



I've looked at the tail of all logs in /var/log/koha/(instance)/, but most are 
empty and the others don't give me any meaning.

One example, intranet-error.log gives:

[Sun Mar 12 09:18:00.882412 2023] [cgi:error] [pid 25446] [client 
185.224.128.17:41784] AH01215: Configuration not defined at 
/usr/share/perl5/Log/Log4perl/Config.pm line 579.: 
/usr/share/koha/intranet/cgi-bin/mainpage.pl

I've viewed both files listed, but not being a programmer, I can't see what 
might be wrong with them.


To review, an upgrade to 21.11 (OldOldStable) and Debian 10 results in 
[Internal Server Error] screens.


hi Bruce
the short version is that your koha instance is probably missing a 
log4perl.conf file

a simple way to correct the problem would be to create a new instance, then 
copy the missing log4perl.conf file from the new instance

then do a search/replace on instance_name, in the file




here is an example of a log4perl.conf file - please search/replace it, as 
required :)



# cat /etc/koha/sites/tp3/log4perl.conf

log4perl.logger.intranet = WARN, INTRANET
log4perl.appender.INTRANET=Log::Log4perl::Appender::File
log4perl.appender.INTRANET.filename=/var/log/koha/tp3/intranet-error.log
log4perl.appender.INTRANET.mode=append
log4perl.appender.INTRANET.layout=PatternLayout
log4perl.appender.INTRANET.layout.ConversionPattern=[%d] [%p] %m %l%n
log4perl.appender.INTRANET.utf8=1

log4perl.logger.opac = WARN, OPAC
log4perl.appender.OPAC=Log::Log4perl::Appender::File
log4perl.appender.OPAC.filename=/var/log/koha/tp3/opac-error.log
log4perl.appender.OPAC.mode=append
log4perl.appender.OPAC.layout=PatternLayout
log4perl.appender.OPAC.layout.ConversionPattern=[%d] [%p] %m %l%n
log4perl.appender.OPAC.utf8=1

log4perl.logger.z3950 = WARN, Z3950
log4perl.appender.Z3950=Log::Log4perl::Appender::File
log4perl.appender.Z3950.filename=/var/log/koha/tp3/z3950-error.log
log4perl.appender.Z3950.mode=append
log4perl.appender.Z3950.layout=PatternLayout
log4perl.appender.Z3950.layout.ConversionPattern=[%d] [%p] %m %l%n
log4perl.appender.Z3950.utf8=1

log4perl.logger.api = WARN, API
log4perl.appender.API=Log::Log4perl::Appender::File
log4perl.appender.API.filename=/var/log/koha/tp3/api-error.log
log4perl.appender.API.mode=append
log4perl.appender.API.layout=PatternLayout
log4perl.appender.API.layout.ConversionPattern=[%d] [%p] %m %l%n
log4perl.appender.API.utf8=1

log4perl.logger.sip = DEBUG, SIP
log4perl.appender.SIP=Log::Log4perl::Appender::File
log4perl.appender.SIP.filename=/var/log/koha/tp3/sip.log
log4perl.appender.SIP.mode=append
log4perl.appender.SIP.layout=PatternLayout
log4perl.appender.SIP.layout.ConversionPattern=[%d] [%P] [%p] %m %l%n
log4perl.appender.SIP.utf8=1


log4perl.logger.plack-opac = WARN, PLACKOPAC
log4perl.appender.PLACKOPAC=Log::Log4perl::Appender::File
log4perl.appender.PLACKOPAC.filename=/var/log/koha/tp3/plack-opac-error.log
log4perl.appender.PLACKOPAC.mode=append
log4perl.appender.PLACKOPAC.layout=PatternLayout
log4perl.appender.PLACKOPAC.layout.ConversionPattern=[%d] [%p] %m
log4perl.appender.PLACKOPAC.utf8=1

log4perl.logger.plack-api = WARN, PLACKAPI
log4perl.appender.PLACKAPI=Log::Log4perl::Appender::File
log4perl.appender.PLACKAPI.filename=/var/log/koha/tp3/plack-api-error.log
log4perl.appender.PLACKAPI.mode=append
log4perl.appender.PLACKAPI.layout=PatternLayout
log4perl.appender.PLACKAPI.layout.ConversionPattern=[%d] [%p] %m
log4perl.appender.PLACKAPI.utf8=1

log4perl.logger.plack-intranet = WARN, PLACKINTRANET
log4perl.appender.PLACKINTRANET=Log::Log4perl::Appender::File
log4perl.appender.PLACKINTRANET.filename=/var/log/koha/tp3/plack-intranet-error.log
log4perl.appender.PLACKINTRANET.mode=append
log4perl.appender.PLACKINTRANET.layout=PatternLayout
log4perl.appender.PLACKINTRANET.layout.ConversionPattern=[%d] [%p] %m
log4perl.appender.PLACKINTRANET.utf8=1

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Mason James]

On 13/03/23 5:13 am, Bruce A. Metcalf wrote:

On 3/12/23 10:34, Katrin Fischer wrote:


the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.



I've looked at the tail of all logs in /var/log/koha/(instance)/, but most are 
empty and the others don't give me any meaning.

One example, intranet-error.log gives:

[Sun Mar 12 09:18:00.882412 2023] [cgi:error] [pid 25446] [client 
185.224.128.17:41784] AH01215: Configuration not defined at 
/usr/share/perl5/Log/Log4perl/Config.pm line 579.: 
/usr/share/koha/intranet/cgi-bin/mainpage.pl

I've viewed both files listed, but not being a programmer, I can't see what 
might be wrong with them.


To review, an upgrade to 21.11 (OldOldStable) and Debian 10 results in 
[Internal Server Error] screens.


hi Bruce
the short version is that your koha instance is probably missing a 
log4perl.conf file

a simple way to correct the problem would be to create a new instance, then 
copy the missing log4perl.conf file from the new instance

then do a search/replace on instance_name, in the file


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] KOHA Upgrade fails from v20.05 to v22.11

[zen zenitram]

Good day!


Anyone encountered this kind of error while upgrading KOHA?

Upgrading database schema for lrc
Upgrade to 22.06.00.063  [05:39:06]: Bug 31569
 -
Add primary key for import_biblios
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
entry '11545' for key 'import_biblios.PRIMARY' at
/usr/share/koha/lib/C4/Installer.pm line 739

and this one

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
entry '24064' for key 'import_biblios.import_biblios_ibfk_1' at
/usr/share/koha/lib/C4/Installer.pm line 739


need help with this.


THank you!
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Bruce A. Metcalf]

On 3/12/23 10:34, Katrin Fischer wrote:


the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.



I've looked at the tail of all logs in /var/log/koha/(instance)/, but 
most are empty and the others don't give me any meaning.


One example, intranet-error.log gives:

[Sun Mar 12 09:18:00.882412 2023] [cgi:error] [pid 25446] [client 
185.224.128.17:41784] AH01215: Configuration not defined at 
/usr/share/perl5/Log/Log4perl/Config.pm line 579.: 
/usr/share/koha/intranet/cgi-bin/mainpage.pl


I've viewed both files listed, but not being a programmer, I can't see 
what might be wrong with them.



To review, an upgrade to 21.11 (OldOldStable) and Debian 10 results in 
[Internal Server Error] screens.


TIA,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Katrin Fischer]

Hi Bruce,

the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.

Hope this helps,

Katrin

On 11.03.23 20:48, Asst. Sec. Bruce A. Metcalf wrote:

Hi gang

Back again after a forced suspension of work.

I am trying to upgrade from Koha 21.05 on Debian 9 to 21.11
(OldOldStable) on Debian 10.

The upgrade appears to go through, but both public and staff interface
display [Internal Server Error].

System was working fine on 21.05/9, and all but Koha work under Debian
10.

All suggestions will be appreciated.

Cheers,
/ Bruce /
Bruce A. Metcalf, Librarian
Augustan Library

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Asst. Sec. Bruce A. Metcalf]

Hi gang

Back again after a forced suspension of work.

I am trying to upgrade from Koha 21.05 on Debian 9 to 21.11 
(OldOldStable) on Debian 10.


The upgrade appears to go through, but both public and staff interface 
display [Internal Server Error].


System was working fine on 21.05/9, and all but Koha work under Debian 10.

All suggestions will be appreciated.

Cheers,
/ Bruce /
Bruce A. Metcalf, Librarian
Augustan Library

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] KOHA upgrade error

[Katrin Fischer]

Hi,

I believe it's probably the same error here:

*Bug 32762*
 -
Duplicate entry '10434' for key 'PRIMARY' at
/usr/share/koha/lib/C4/Installer.pm line 739

Unfortunately, I doesn't have a fix or solution yet.

Hope that helps,

Katrin

On 20.02.23 01:16, zen zenitram wrote:

Good morning all, we are trying to upgrade our koha database but too many
duplicate entry shows.

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry
'ar' for key 'PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 739


This is the first error i encountered when upgrading koha from v20.05 to
the latest version that is 22.11 and i already found the fix.

The next error is " ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do
failed: Duplicate entry '20534' for key 'import_biblios.PRIMARY' at
/usr/share/koha/lib/C4/Installer.pm line 739".

we tried to locate this duplicate entry and it points to biblios in
reservoir entry.



Anyone of you encountered this kind of error while upgrading?


I need help on how we gonna fix it.


Thank you!
___

Koha mailing listhttp://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade - Error - Missing - Koha?

[MJ Ray]

Le 17 février 2023 11:09:33 GMT+00:00, "Chief Librarian, SAIACS" 
 a écrit :
>E: Failed to fetch
>http://security.ubuntu.com/ubuntu/pool/main/a/apache2/apache2-data_2.4.41-4ubuntu3.13_all.deb
> 500  Internal Server Error [IP: 185.125.190.39 80]
>E: Unable to fetch some archives, maybe run apt-get update or try with
>--fix-missing?
>
>Could someone share insights on how to fix this?.

Can you download 
http://security.ubuntu.com/ubuntu/pool/main/a/apache2/apache2-data_2.4.41-4ubuntu3.13_all.deb
 in a browser?

If not, there may be some problem accessing that server somewhere between you 
and it, or the security.ubuntu server might have been down (but it isn't now).

If so, maybe some cute firewall between your server and security.ubuntu is 
messing up.

Hope that helps,
-- 
MJR
software.coop koha support
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] KOHA upgrade error

[zen zenitram]

Good morning all, we are trying to upgrade our koha database but too many
duplicate entry shows.

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry
'ar' for key 'PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 739


This is the first error i encountered when upgrading koha from v20.05 to
the latest version that is 22.11 and i already found the fix.

The next error is " ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do
failed: Duplicate entry '20534' for key 'import_biblios.PRIMARY' at
/usr/share/koha/lib/C4/Installer.pm line 739".

we tried to locate this duplicate entry and it points to biblios in
reservoir entry.



Anyone of you encountered this kind of error while upgrading?


I need help on how we gonna fix it.


Thank you!
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade - Error - Missing - Koha?

[Chief Librarian, SAIACS]

Hi Friends,

I am getting error while running upgrade command
sudo apt-get upgrade

Ign:1 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64
apache2-data all 2.4.41-4ubuntu3.13
Ign:1 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64
apache2-data all 2.4.41-4ubuntu3.13
Ign:1 http://security.ubuntu.com/ubuntu focal-updates/main amd64
apache2-data all 2.4.41-4ubuntu3.13
Err:1 http://security.ubuntu.com/ubuntu focal-updates/main amd64
apache2-data all 2.4.41-4ubuntu3.13
  500  Internal Server Error [IP: 185.125.190.39 80]
E: Failed to fetch
http://security.ubuntu.com/ubuntu/pool/main/a/apache2/apache2-data_2.4.41-4ubuntu3.13_all.deb
 500  Internal Server Error [IP: 185.125.190.39 80]
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?

Could someone share insights on how to fix this?.

OS Ubuntu 20.4, Focal

Thanks


__

*Dr. Yesan Sellan, * *MLISc., PGDLAN, BCS., UGC-NET., PhD*


*Strategic | Learner | Achiever | Responsibility | Intellection*


*Chief Librarian*

South Asia Institute of Advanced Christian Studies (SAIACS)

363 Dodda Gubbi Cross Road, Kothanur P.O., Bangalore 77, India

Phone: 91 80 2846 5235/5344/ 5649, Fax: 91 80 28465412, Mobile:
91-9972348251

www.saiacs.org Alternative Email: yes...@gmail.com

https://orcid.org/-0002-0501-5661




__

IMPORTANT : This message is intended only for the addressee. It may contain
confidential information. Any unauthorized disclosure is strictly
prohibited. If you have received this message in error, please notify us
immediately so that we may correct our internal records. Please then delete
the original message. Thank you.



P Please consider the environment before printing this email*.*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from - 17.11.02

[MASTeR Library]

Koha Upgrade the old stable version.
https://libpowertech.blogspot.com/2019/11/how-to-upgrade-koha.html
https://wiki.koha-community.org/wiki/Koha_on_Debian

On Mon, Feb 13, 2023 at 1:21 PM Laxmi Lal Menaria 
wrote:

> Good Morning All!
>
> We have installed koha - 17.11.02, and would like to upgrade to the latest
> version. Please let me know the steps I need to use.
>
> Is there any help link where I can see the steps? Please help me.
>
> Thanks in advance.
> --
>
> Thanks,
> Laxmilal Menaria | +91 982 955 3793 | http://cloud-computing.solutions/
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>


-- 
 Thanking you..

Librarian,
MAMCET <http://mamcet.com/>
Trichy-Chennai Trunk Road,
Siruganur, Tiruchirappalli-621 105.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade from - 17.11.02

[Laxmi Lal Menaria]

Good Morning All!

We have installed koha - 17.11.02, and would like to upgrade to the latest
version. Please let me know the steps I need to use.

Is there any help link where I can see the steps? Please help me.

Thanks in advance.
-- 

Thanks,
Laxmilal Menaria | +91 982 955 3793 | http://cloud-computing.solutions/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha upgrade and restore issue

[vinod mishra]

Hello
I wish to restore the database from one server to other in same version
(22.05.07.000) but while running the " *sudo koha-upgrade-schema library*"
command it through following error. Almost same error getting while running
" *sudo koha-rebuild-zebra -v -f library* " command. Please suggest the
possible issue.

root@koha-OptiPlex-9010:/home/koha# sudo koha-upgrade-schema library
Upgrading database schema for library
DBD::mysql::st execute failed: Table 'koha_library.systempreferences'
doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::st execute failed: Table 'koha_library.systempreferences'
doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152.
Use of uninitialized value in numeric lt (<) at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 78.
DBD::mysql::db do failed: Table 'koha_library.bookshelf' doesn't exist at
/usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.shelfcontents' doesn't exist
at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't
exist at /usr/share/koha/lib/Koha/Database.pm line 152.
DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't
exist at /usr/share/koha/lib/Koha/Database.pm line 152.
Undefined subroutine ::DropAllForeignKeys called at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 86.
root@koha-OptiPlex-9010:/home/koha#

With Regards,

Vinod Kumar Mishra,
Assistant Librarian,
Biju Patnaik Central Library (BPCL),
NIT Rourkela,
Sundergadh-769008,
Odisha,
India.
Mob:91+9439420860
URL: http://vinod.itshelp.co.in/
ORCID ID: http://orcid.org/-0003-4666-7874
Scopus ID: 57223138343

*"Spiritual relationship is far more precious than physical. Physical
relationship divorced from spiritual is body without soul" -- Mahatma
Gandhi*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 22.11 System Prefernces

[Elaine Bradtke]

I just changed the language setting to  English (en) and removed the
(eng-GB) translation.  Now the menus are correct in the system preferences.
Our production system is running 22.05.05 and it also has the same problem
with menus (the test site is on 22.11).
Is there a bug already filed?
I wonder if this happens in other languages or is it just en-GB

Thanks, at least I know our system isn't fatally corrupted.
I've got a partial list of the affected menu items if that's any use.
Elaine
VWML 



On Sun, Dec 18, 2022 at 11:34 PM Katrin Fischer 
wrote:

> Hi Elaine,
>
> you mention problems with the translations - does everything work ok
> with English (en) or are the problems with the system preferences also
> present there?
>
> If the problem is present without translations too, could you create a
> report and show the results?
>
> SELECT * from systempreferences where variable = "name of preference";
>
> Hope this helps,
>
> Katrin
>
> On 13.12.22 20:55, Elaine Bradtke wrote:
> > Something is weird about the System Preferences after upgrading (using
> the
> > latest version of Chrome).  The contents of the pulldown menus in some
> > preferences are just odd.
> >   For instance:  Share anonymous Koha usage data with the Koha community:
> >No religious organisationNo, let me
> think
> > about it   .
> > If that doesn't display it says Share anonymous Koha usage data with the
> > Koha community: religious organisation
> >
> > When we upgraded our test site, the language preference changed back to
> > English (eng) though it had been set to English United Kingdom (eng-GB).
> It
> > says you can reorder the language choices, but that doesn't seem to work.
> > I don't know if it's a translation problem or what?
> > Elaine Bradtke
> > VWML
> > English Folk Dance and Song Society
> > Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> > Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance
> and
> > Song Society in London, England. If you wish to phone me personally, send
> > an e-mail first. I work off site)
> >
> --
> > Registered Company No. 297142
> > Charity Registered in England and Wales No. 305999
> > ___
> >
> > Koha mailing listhttp://koha-community.org
> > Koha@lists.katipo.co.nz
> > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 22.11 System Prefernces

[Katrin Fischer]

Hi Elaine,

you mention problems with the translations - does everything work ok
with English (en) or are the problems with the system preferences also
present there?

If the problem is present without translations too, could you create a
report and show the results?

SELECT * from systempreferences where variable = "name of preference";

Hope this helps,

Katrin

On 13.12.22 20:55, Elaine Bradtke wrote:

Something is weird about the System Preferences after upgrading (using the
latest version of Chrome).  The contents of the pulldown menus in some
preferences are just odd.
  For instance:  Share anonymous Koha usage data with the Koha community:
   No religious organisationNo, let me think
about it   .
If that doesn't display it says Share anonymous Koha usage data with the
Koha community: religious organisation

When we upgraded our test site, the language preference changed back to
English (eng) though it had been set to English United Kingdom (eng-GB). It
says you can reorder the language choices, but that doesn't seem to work.
I don't know if it's a translation problem or what?
Elaine Bradtke
VWML
English Folk Dance and Song Society
Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
Song Society in London, England. If you wish to phone me personally, send
an e-mail first. I work off site)
--
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
___

Koha mailing listhttp://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade to 22.11 System Prefernces

[Elaine Bradtke]

Something is weird about the System Preferences after upgrading (using the
latest version of Chrome).  The contents of the pulldown menus in some
preferences are just odd.
 For instance:  Share anonymous Koha usage data with the Koha community:
  No religious organisationNo, let me think
about it   .
If that doesn't display it says Share anonymous Koha usage data with the
Koha community: religious organisation

When we upgraded our test site, the language preference changed back to
English (eng) though it had been set to English United Kingdom (eng-GB). It
says you can reorder the language choices, but that doesn't seem to work.
I don't know if it's a translation problem or what?
Elaine Bradtke
VWML 
English Folk Dance and Song Society 
Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
Song Society in London, England. If you wish to phone me personally, send
an e-mail first. I work off site)
--
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Bruce A. Metcalf]

Jonathan Druart wrote:

> Yes, definitely, it must be owned by the  $INSTANCE-koha user


PETRIDIS wrote:


Just checked my system’s files and log4perl.conf is indeed owned by root,
however has rw set for all.



FWIW, in order to get back to work, I restored from backup and found:

-rw-r--r-- 1 root root 2134 Dec 19  2020 
/etc/koha/sites/library/log4perl.conf


Which works properly.


I also discovered that 21.11 needs Debian 10 or 11, and I'm still on 
Debian 9, so my bad.


After the next system backup, I'll try to upgrade Debian to 10, followed 
by an upgrade of Koha to 21.11. No news is good news.


Thanks to all for the suggestions.

Regards,
/ Bruce /
Bruce A. Metcalf
Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Manos PETRIDIS]

Just checked my system’s files and log4perl.conf is indeed owned by root,
however has rw set for all.

Στις Τετ 30 Νοε 2022 στις 9:24 πμ ο χρήστης Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> έγραψε:

> Yes, definitely, it must be owned by the  $INSTANCE-koha user
>
> Le lun. 28 nov. 2022 à 21:38, Bruce A. Metcalf <
> libr...@augustansociety.org>
> a écrit :
>
> > On 11/28/22 16:52, Jonathan Druart wrote:
> >
> > > Did you upgrade using the debian packages?
> >
> >
> > Yes; always.
> >
> >
> > > The error is saying you don't have the log4perl config file, which
> > > needs to be at /etc/koha/sites/$INSTANCE/log4perl.conf
> >
> >
> > This file exists, but I note that it's owned by "root", and not
> > "instance-koha". Could this be the issue?
> >
> > Regards,
> > / Bruce /
> > Bruce A. Metcalf
> > Augustan Library
> > ___
> >
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Jonathan Druart]

Yes, definitely, it must be owned by the  $INSTANCE-koha user

Le lun. 28 nov. 2022 à 21:38, Bruce A. Metcalf 
a écrit :

> On 11/28/22 16:52, Jonathan Druart wrote:
>
> > Did you upgrade using the debian packages?
>
>
> Yes; always.
>
>
> > The error is saying you don't have the log4perl config file, which
> > needs to be at /etc/koha/sites/$INSTANCE/log4perl.conf
>
>
> This file exists, but I note that it's owned by "root", and not
> "instance-koha". Could this be the issue?
>
> Regards,
> / Bruce /
> Bruce A. Metcalf
> Augustan Library
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Bruce A. Metcalf]

On 11/28/22 16:52, Jonathan Druart wrote:


Did you upgrade using the debian packages?



Yes; always.



The error is saying you don't have the log4perl config file, which
needs to be at /etc/koha/sites/$INSTANCE/log4perl.conf



This file exists, but I note that it's owned by "root", and not 
"instance-koha". Could this be the issue?


Regards,
/ Bruce /
Bruce A. Metcalf
Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Jonathan Druart]

Did you upgrade using the debian packages?

The error is saying you don't have the log4perl config file, which
needs to be at /etc/koha/sites/$INSTANCE/log4perl.conf

Le lun. 28 nov. 2022 à 15:34, Bruce A. Metcalf
 a écrit :
>
> On 11/28/22 15:07, Jonathan Druart wrote:
>
> > Did you restart koha-common?
>
>
> Yes, I rebooted the whole virtual machine. No change.
>
>
> > Do you have an error in the Koha logs?
>
>
> intranet-error.log
>
> [Mon Nov 28 09:30:06.112562 2022] [cgi:error] [pid 13388] [client ... ]
> AH01215: Configuration not defined at
> /usr/share/perl5/Log/Log4perl/Config.pm line 579.:
> /usr/share/koha/opac/cgi-bin/opac/errors/500.pl
> [Mon Nov 28 09:30:06.148729 2022] [cgi:error] [pid 13388] [client ... ]
> End of script output before headers: 500.pl
>
> Doesen't give me a clue. Anyone else?
>
> Thanks,
> / Bruce /
> Bruce A. Metcalf
> Augustan Library
>
>
> >> Yes, I'm slow on the uptake, I've been running oldoldstable for some
> >> time now. With the release of 22.11, it's time for me to move up.
> >>
> >> My system was installed from deb packages under Debian 10, and has been
> >> updating fine.
> >>
> >> After an update (with no error messages), I find I am unable to access
> >> either the OPAC or the admin interfaces. Both give an "Internal Server
> >> Error" message, with a note that a 500 error was thrown by the
> >> ErrorDocument handler as well.
> >>
> >> Probably something simple, but not something I can see or find in the
> >> release notes. Help!
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Bruce A. Metcalf]

On 11/28/22 15:07, Jonathan Druart wrote:


Did you restart koha-common?



Yes, I rebooted the whole virtual machine. No change.



Do you have an error in the Koha logs?



intranet-error.log

[Mon Nov 28 09:30:06.112562 2022] [cgi:error] [pid 13388] [client ... ] 
AH01215: Configuration not defined at 
/usr/share/perl5/Log/Log4perl/Config.pm line 579.: 
/usr/share/koha/opac/cgi-bin/opac/errors/500.pl
[Mon Nov 28 09:30:06.148729 2022] [cgi:error] [pid 13388] [client ... ] 
End of script output before headers: 500.pl


Doesen't give me a clue. Anyone else?

Thanks,
/ Bruce /
Bruce A. Metcalf
Augustan Library



Yes, I'm slow on the uptake, I've been running oldoldstable for some
time now. With the release of 22.11, it's time for me to move up.

My system was installed from deb packages under Debian 10, and has been
updating fine.

After an update (with no error messages), I find I am unable to access
either the OPAC or the admin interfaces. Both give an "Internal Server
Error" message, with a note that a 500 error was thrown by the
ErrorDocument handler as well.

Probably something simple, but not something I can see or find in the
release notes. Help!

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 Fails

[Jonathan Druart]

Hello,

Did you restart koha-common? Do you have an error in the Koha logs?
Run the following command for watch the logs: tail -f /var/log/koha/*/*.log

Regards,
Jonathan

Le lun. 28 nov. 2022 à 13:19, Bruce A. Metcalf
 a écrit :
>
> Greetings,
>
> Yes, I'm slow on the uptake, I've been running oldoldstable for some
> time now. With the release of 22.11, it's time for me to move up.
>
> My system was installed from deb packages under Debian 10, and has been
> updating fine.
>
> After an update (with no error messages), I find I am unable to access
> either the OPAC or the admin interfaces. Both give an "Internal Server
> Error" message, with a note that a 500 error was thrown by the
> ErrorDocument handler as well.
>
> Probably something simple, but not something I can see or find in the
> release notes. Help!
>
> Regards,
> / Bruce /
> Bruce A. Metcalf
> Augustan Library
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade to 21.11 Fails

[Bruce A. Metcalf]

Greetings,

Yes, I'm slow on the uptake, I've been running oldoldstable for some 
time now. With the release of 22.11, it's time for me to move up.


My system was installed from deb packages under Debian 10, and has been 
updating fine.


After an update (with no error messages), I find I am unable to access 
either the OPAC or the admin interfaces. Both give an "Internal Server 
Error" message, with a note that a 500 error was thrown by the 
ErrorDocument handler as well.


Probably something simple, but not something I can see or find in the 
release notes. Help!


Regards,
/ Bruce /
Bruce A. Metcalf
Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade assistance

[Katrin Fischer]

Hi Steve,

please have a look at this bug and the comments:

*Bug 31673*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31673> - DB
update of bug 31086
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31086> fails:
Cannot change column 'branchcode': used in a foreign key constraint

Hope this helps,

Katrin

On 05.10.22 14:10, Steve Nickerson wrote:

Thanks for the reference bug and the command.  Unfortunately, when I execute 
the command suggested I receive:

ERROR 1832 (HY000): Cannot change column 'branchcode': used in a foreign key 
constraint 'reserves_ibfk_4'



Any other thoughts?

Thanks again!

Steve



From: Evan Mungai Njoroge
Sent: Wednesday, October 05, 2022 2:16 AM
To: Steve Nickerson
Cc: koha
Subject: Re: [Koha] Upgrade assistance



I had the same issue upgrading from Koha 22.05.04.001 to 22.05.05.000.

This came in handy 
-https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31086


SOLUTION:

Log in to MySQL/Maria, change database to the instance DB;

Run;


ALTER TABLE reserves MODIFY COLUMN `branchcode` varchar(10) COLLATE 
utf8mb4_unicode_ci NOT NULL DEFAULT 0;



Upgrade Schema.



Your upgrade will complete.



Regards



EM Njoroge





On Wed, Oct 5, 2022 at 4:51 AM Steve Nickerson mailto:stevenanicker...@gmail.com>  > wrote:

Good evening everyone,

I'm trying to upgrade a Koha environment from 19.11.03.000 to the latest
22.05.04.000, including upgrading Debian OS from jessie to stretch.  This
was originally a package install on Debian Jessie. I did the upgrade
successfully in a "test" environment and am now trying on my production
system.   After my first attempt I got the "welcome to Koha, please login
using the default Koha user' screen, so I deleted that DB completely and
restored from the backup I took right before the upgrade.   Now when I try
to execute 'koha-upgrade-schema ' I get:

Upgrade to 22.05.04.002  [21:40:11]: Bug 31086 - Do not allow null values in
branchcodes for reserves

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change
column 'branchcode': used in a foreign key constraint 'reserves_ibfk_4' at
/usr/share/koha/lib/C4/Installer.pm line 739



Any ideas?



Thanks!

Steve

___

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

___

Koha mailing listhttp://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade assistance

[Steve Nickerson]

Thanks for the reference bug and the command.  Unfortunately, when I execute 
the command suggested I receive:

ERROR 1832 (HY000): Cannot change column 'branchcode': used in a foreign key 
constraint 'reserves_ibfk_4'

 

Any other thoughts?

Thanks again!

Steve

 

From: Evan Mungai Njoroge  
Sent: Wednesday, October 05, 2022 2:16 AM
To: Steve Nickerson 
Cc: koha 
Subject: Re: [Koha] Upgrade assistance

 

I had the same issue upgrading from Koha 22.05.04.001 to 22.05.05.000.

This came in handy - 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31086


SOLUTION:

Log in to MySQL/Maria, change database to the instance DB;

Run;


ALTER TABLE reserves MODIFY COLUMN `branchcode` varchar(10) COLLATE 
utf8mb4_unicode_ci NOT NULL DEFAULT 0;

 

Upgrade Schema.

 

Your upgrade will complete.

 

Regards



EM Njoroge

 

 

On Wed, Oct 5, 2022 at 4:51 AM Steve Nickerson mailto:stevenanicker...@gmail.com> > wrote:

Good evening everyone,

   I'm trying to upgrade a Koha environment from 19.11.03.000 to the latest
22.05.04.000, including upgrading Debian OS from jessie to stretch.  This
was originally a package install on Debian Jessie. I did the upgrade
successfully in a "test" environment and am now trying on my production
system.   After my first attempt I got the "welcome to Koha, please login
using the default Koha user' screen, so I deleted that DB completely and
restored from the backup I took right before the upgrade.   Now when I try
to execute 'koha-upgrade-schema ' I get:

Upgrade to 22.05.04.002  [21:40:11]: Bug 31086 - Do not allow null values in
branchcodes for reserves

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change
column 'branchcode': used in a foreign key constraint 'reserves_ibfk_4' at
/usr/share/koha/lib/C4/Installer.pm line 739



Any ideas?



Thanks!

Steve

___

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

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade assistance

[Evan Mungai Njoroge]

I had the same issue upgrading from Koha 22.05.04.001 to 22.05.05.000.
This came in handy -
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31086

*SOLUTION:*
Log in to MySQL/Maria, change database to the instance DB;
Run;


*ALTER TABLE reserves MODIFY COLUMN `branchcode` varchar(10) COLLATE
utf8mb4_unicode_ci NOT NULL DEFAULT 0;*

Upgrade Schema.

Your upgrade will complete.

Regards

**
*EM Njoroge*


On Wed, Oct 5, 2022 at 4:51 AM Steve Nickerson 
wrote:

> Good evening everyone,
>
>I'm trying to upgrade a Koha environment from 19.11.03.000 to the latest
> 22.05.04.000, including upgrading Debian OS from jessie to stretch.  This
> was originally a package install on Debian Jessie. I did the upgrade
> successfully in a "test" environment and am now trying on my production
> system.   After my first attempt I got the "welcome to Koha, please login
> using the default Koha user' screen, so I deleted that DB completely and
> restored from the backup I took right before the upgrade.   Now when I try
> to execute 'koha-upgrade-schema ' I get:
>
> Upgrade to 22.05.04.002  [21:40:11]: Bug 31086 - Do not allow null values
> in
> branchcodes for reserves
>
> ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change
> column 'branchcode': used in a foreign key constraint 'reserves_ibfk_4' at
> /usr/share/koha/lib/C4/Installer.pm line 739
>
>
>
> Any ideas?
>
>
>
> Thanks!
>
> Steve
>
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade assistance

[Steve Nickerson]

Good evening everyone,

   I'm trying to upgrade a Koha environment from 19.11.03.000 to the latest
22.05.04.000, including upgrading Debian OS from jessie to stretch.  This
was originally a package install on Debian Jessie. I did the upgrade
successfully in a "test" environment and am now trying on my production
system.   After my first attempt I got the "welcome to Koha, please login
using the default Koha user' screen, so I deleted that DB completely and
restored from the backup I took right before the upgrade.   Now when I try
to execute 'koha-upgrade-schema ' I get:

Upgrade to 22.05.04.002  [21:40:11]: Bug 31086 - Do not allow null values in
branchcodes for reserves

ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change
column 'branchcode': used in a foreign key constraint 'reserves_ibfk_4' at
/usr/share/koha/lib/C4/Installer.pm line 739

 

Any ideas?

 

Thanks!

Steve

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade

[Michael Kuhn]

Hi D. Gnanasekaran

You wrote:

> I am using the version 19.05 and would like to upgrade to the higher
> versions. May I know the step by step procedures for the upgrade?
> with thanks,

You will find the official upgrading instructions at
https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrading_Koha

Of course it is also a good idea to create a backup before trying to 
upgrade.


Hope this helps.

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade

[KARE- LIBRARY]

Hi,
I am using the version 19.05 and would like to upgrade to the higher
versions. May I know the step by step procedures for the upgrade?
with thanks,
D.Gnanasekaran

-- 
With thanks,
Dr. D. Gnanasekaran
University Librarian
Kalasalingam Academy of Research and Education
(Deemed to be University)
Krishnankoil - 626 126
Virudhunagar District
Tamil Nadu
Ph: 9710906899
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade error from 1905 to 21.11

[Sunita Barve]

Hi

Thanks for the reply.

I had asked today on IRC as well and had got answer from mtj and could
solve the error.

Thanks for your reply.

reg

Sunita Barve

On Thu, Sep 15, 2022 at 3:39 PM Mason James  wrote:

> hi Sunita
> you seem to have a problem with OpenAPI, perhaps installed via CPAN?
>
>
> follow this guide... https://wiki.koha-community.org/wiki/REST_API_Debug
>
> take a look at the following section
>1.4 Check 3 API packages are not installed via CPAN
>
>
>
> On 14/09/22 11:01 pm, Sunita Barve wrote:
> > I wanted to upgrade my koha to latest version.
> > While upgrading when I ran upgrade directly it threw error hence ?I tried
> > upgrading from 19.05 to 19.11 then from 19.11 to 20.11 then from 20.11 to
> > 21.11 there were no errors and upgrade was successful. Before upgrading
> to
> > 20.11 I had installed Mojolicious::Plugin::OpenAPI and then ran upgrades
> of
> > 20.11 and 21.11.
> >
> > 1. I am unable to see my libraries name in under Global System
> Preferences
> > under libraries option.
> > 2. We are unable to circulate books through RFId and I found error as
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> > 'koha-ncl.issuingrules" does not exist.
> > 3. Here are my latest log entries in intranet-error.log
> > [Wed Sep 14 16:15:40.809002 2022] [cgi:error] [pid 3589] [client
> > 172.16.3.14:33246] AH01215: [2022-09-14 16:15:40.80837] [3608] [error]
> > [pFebfFcy8Vis] Can't use an undefined value as an ARRAY reference at
> > /usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm line 296.:
> > /usr/share/koha/api/v1/app.pl, referer:
> > http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> > [Wed Sep 14 16:15:40.809064 2022] [cgi:error] [pid 3589] [client
> > 172.16.3.14:33246] AH01215: : /usr/share/koha/api/v1/app.pl, referer:
> > http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> > [Wed Sep 14 16:15:40.809293 2022] [cgi:error] [pid 3589] [client
> > 172.16.3.14:33246] AH01215: Can't use an undefined value as an ARRAY
> > reference at /usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm
> > line 296.: /usr/share/koha/api/v1/app.pl, referer:
> > http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> > [Wed Sep 14 16:15:40.841776 2022] [cgi:error] [pid 3589] [client
> > 172.16.3.14:33246] End of script output before headers: app.pl, referer:
> > http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> > [Wed Sep 14 16:15:42.531300 2022] [cgi:error] [pid 3589] [client
> > 172.16.3.14:33246] AH01215: Use of uninitialized value in string eq at
> > /usr/share/koha/lib/C4/Context.pm line 784.:
> > /usr/share/koha/intranet/cgi-bin/errors/500.pl, referer:
> > http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> >
> > 4. I have tried to uninstall koha-common and changed my koha.list to
> > following
> >
> > deb http://debian.koha-community.org/koha 21.11 main bionic
> >
> > I then reinstalled koha-common but no luck.
> >
> > Can someone help.
> >
> > with reg
> >
> > Sunita Barve, Ph. D.
> > Head, KRC/Library
> > CSIR-National Chemical Laboratory
> > Dr, Homi Bhaba Road
> > Pune 411008, INDIA
> > Email :sunitaba...@gmail.com ; sa.ba...@ncl.res.in
> > http://sunitabarve.googlepages.com
> > ___
> >
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
>

-- 
Sunita Barve, Ph. D.
Head, KRC/Library
CSIR-National Chemical Laboratory
Dr, Homi Bhaba Road
Pune 411008, INDIA
Email :sunitaba...@gmail.com ; sa.ba...@ncl.res.in
http://sunitabarve.googlepages.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade error from 1905 to 21.11

[Mason James]

hi Sunita
you seem to have a problem with OpenAPI, perhaps installed via CPAN?


follow this guide... https://wiki.koha-community.org/wiki/REST_API_Debug

take a look at the following section
  1.4 Check 3 API packages are not installed via CPAN



On 14/09/22 11:01 pm, Sunita Barve wrote:

I wanted to upgrade my koha to latest version.
While upgrading when I ran upgrade directly it threw error hence ?I tried
upgrading from 19.05 to 19.11 then from 19.11 to 20.11 then from 20.11 to
21.11 there were no errors and upgrade was successful. Before upgrading to
20.11 I had installed Mojolicious::Plugin::OpenAPI and then ran upgrades of
20.11 and 21.11.

1. I am unable to see my libraries name in under Global System Preferences
under libraries option.
2. We are unable to circulate books through RFId and I found error as
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
'koha-ncl.issuingrules" does not exist.
3. Here are my latest log entries in intranet-error.log
[Wed Sep 14 16:15:40.809002 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: [2022-09-14 16:15:40.80837] [3608] [error]
[pFebfFcy8Vis] Can't use an undefined value as an ARRAY reference at
/usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm line 296.:
/usr/share/koha/api/v1/app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:40.809064 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: : /usr/share/koha/api/v1/app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:40.809293 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: Can't use an undefined value as an ARRAY
reference at /usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm
line 296.: /usr/share/koha/api/v1/app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:40.841776 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] End of script output before headers: app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:42.531300 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: Use of uninitialized value in string eq at
/usr/share/koha/lib/C4/Context.pm line 784.:
/usr/share/koha/intranet/cgi-bin/errors/500.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl

4. I have tried to uninstall koha-common and changed my koha.list to
following

deb http://debian.koha-community.org/koha 21.11 main bionic

I then reinstalled koha-common but no luck.

Can someone help.

with reg

Sunita Barve, Ph. D.
Head, KRC/Library
CSIR-National Chemical Laboratory
Dr, Homi Bhaba Road
Pune 411008, INDIA
Email :sunitaba...@gmail.com ; sa.ba...@ncl.res.in
http://sunitabarve.googlepages.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade error from 1905 to 21.11

[vinod mishra]

Hello
issuingrules table do not exist and it has been replaced with
circulation_rules in new versions



On Wed, 14 Sep, 2022, 16:32 Sunita Barve,  wrote:

> I wanted to upgrade my koha to latest version.
> While upgrading when I ran upgrade directly it threw error hence ?I tried
> upgrading from 19.05 to 19.11 then from 19.11 to 20.11 then from 20.11 to
> 21.11 there were no errors and upgrade was successful. Before upgrading to
> 20.11 I had installed Mojolicious::Plugin::OpenAPI and then ran upgrades of
> 20.11 and 21.11.
>
> 1. I am unable to see my libraries name in under Global System Preferences
> under libraries option.
> 2. We are unable to circulate books through RFId and I found error as
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'koha-ncl.issuingrules" does not exist.
> 3. Here are my latest log entries in intranet-error.log
> [Wed Sep 14 16:15:40.809002 2022] [cgi:error] [pid 3589] [client
> 172.16.3.14:33246] AH01215: [2022-09-14 16:15:40.80837] [3608] [error]
> [pFebfFcy8Vis] Can't use an undefined value as an ARRAY reference at
> /usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm line 296.:
> /usr/share/koha/api/v1/app.pl, referer:
> http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> [Wed Sep 14 16:15:40.809064 2022] [cgi:error] [pid 3589] [client
> 172.16.3.14:33246] AH01215: : /usr/share/koha/api/v1/app.pl, referer:
> http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> [Wed Sep 14 16:15:40.809293 2022] [cgi:error] [pid 3589] [client
> 172.16.3.14:33246] AH01215: Can't use an undefined value as an ARRAY
> reference at /usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm
> line 296.: /usr/share/koha/api/v1/app.pl, referer:
> http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> [Wed Sep 14 16:15:40.841776 2022] [cgi:error] [pid 3589] [client
> 172.16.3.14:33246] End of script output before headers: app.pl, referer:
> http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
> [Wed Sep 14 16:15:42.531300 2022] [cgi:error] [pid 3589] [client
> 172.16.3.14:33246] AH01215: Use of uninitialized value in string eq at
> /usr/share/koha/lib/C4/Context.pm line 784.:
> /usr/share/koha/intranet/cgi-bin/errors/500.pl, referer:
> http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
>
> 4. I have tried to uninstall koha-common and changed my koha.list to
> following
>
> deb http://debian.koha-community.org/koha 21.11 main bionic
>
> I then reinstalled koha-common but no luck.
>
> Can someone help.
>
> with reg
>
> Sunita Barve, Ph. D.
> Head, KRC/Library
> CSIR-National Chemical Laboratory
> Dr, Homi Bhaba Road
> Pune 411008, INDIA
> Email :sunitaba...@gmail.com ; sa.ba...@ncl.res.in
> http://sunitabarve.googlepages.com
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha upgrade error from 1905 to 21.11

[Sunita Barve]

I wanted to upgrade my koha to latest version.
While upgrading when I ran upgrade directly it threw error hence ?I tried
upgrading from 19.05 to 19.11 then from 19.11 to 20.11 then from 20.11 to
21.11 there were no errors and upgrade was successful. Before upgrading to
20.11 I had installed Mojolicious::Plugin::OpenAPI and then ran upgrades of
20.11 and 21.11.

1. I am unable to see my libraries name in under Global System Preferences
under libraries option.
2. We are unable to circulate books through RFId and I found error as
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
'koha-ncl.issuingrules" does not exist.
3. Here are my latest log entries in intranet-error.log
[Wed Sep 14 16:15:40.809002 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: [2022-09-14 16:15:40.80837] [3608] [error]
[pFebfFcy8Vis] Can't use an undefined value as an ARRAY reference at
/usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm line 296.:
/usr/share/koha/api/v1/app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:40.809064 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: : /usr/share/koha/api/v1/app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:40.809293 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: Can't use an undefined value as an ARRAY
reference at /usr/local/share/perl/5.26.1/Mojolicious/Plugin/OpenAPI.pm
line 296.: /usr/share/koha/api/v1/app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:40.841776 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] End of script output before headers: app.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl
[Wed Sep 14 16:15:42.531300 2022] [cgi:error] [pid 3589] [client
172.16.3.14:33246] AH01215: Use of uninitialized value in string eq at
/usr/share/koha/lib/C4/Context.pm line 784.:
/usr/share/koha/intranet/cgi-bin/errors/500.pl, referer:
http://kohaadmin.ncl.res.in/cgi-bin/koha/admin/branches.pl

4. I have tried to uninstall koha-common and changed my koha.list to
following

deb http://debian.koha-community.org/koha 21.11 main bionic

I then reinstalled koha-common but no luck.

Can someone help.

with reg

Sunita Barve, Ph. D.
Head, KRC/Library
CSIR-National Chemical Laboratory
Dr, Homi Bhaba Road
Pune 411008, INDIA
Email :sunitaba...@gmail.com ; sa.ba...@ncl.res.in
http://sunitabarve.googlepages.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade schema issue

[Fridolin SOMERS]

This is fixed in 22.05.03, see
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30899

Le 19/07/2022 à 00:42, Katrin Fischer a écrit :

Hi,

what error did you get?

Katrin

On 19.07.22 10:56, Sami M. Rasheed wrote:



Kindly, Koha Group
Please let me know how to correct the Koha upgrade schema issue.
The system displays the following error while I'm using the 
(koha-upgrade-schema library) to upgrade the Koha system:




DEV atomic update 
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl 
 [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint 
(30449 follow-up)


I'm using:

Koha version: 21.11

OS version: Ubuntu 20.04.4 LTS

MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 
((Ubuntu))


Thanks
Sami Abu Darbeya
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Fridolin SOMERS 
Software and system maintainer 濾
BibLibre, France
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade schema issue

[Katrin Fischer]

Hi Sami,

this is just feedback about a database update that has been run, not an
error.

The only thing strange about it is that it's a DEV update and not a
regular one. Which exact version did you update to? (21.11.?)

Hope this helps,

Katrin

On 20.07.22 06:55, Sami M. Rasheed wrote:

  Dear Kartin,
I have this error:
DEV atomic update 
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl 
 [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 
follow-up)

I'm using:

Koha version: 21.11

OS version: Ubuntu 20.04.4 LTS

MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu))
Thanks
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade schema issue

[Katrin Fischer]

Hi,

what error did you get?

Katrin

On 19.07.22 10:56, Sami M. Rasheed wrote:



Kindly, Koha Group
Please let me know how to correct the Koha upgrade schema issue.
The system displays the following error while I'm using the 
(koha-upgrade-schema library) to upgrade the Koha system:



DEV atomic update 
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl 
 [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 
follow-up)

I'm using:

Koha version: 21.11

OS version: Ubuntu 20.04.4 LTS

MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu))

Thanks
Sami Abu Darbeya
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Upgrade Error 21.11

[Fridolin SOMERS]

Ah good idea :D

Le 04/03/2022 à 18:10, Mason James a écrit :

hi folks
i added a test for this problem here...

  https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19169


On 5/03/22 8:05 am, Fridolin SOMERS wrote:

Ohhh good catch

DEV atomic updates should not exist in releases.

I've added a comment on Bug report :
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29596#c16

Best regards,

Le 03/03/2022 à 21:28, Chief Librarian, SAIACS a écrit :

Hi Friends
I was testing
koha (on ubuntu 20.04) upgrade from 21.05 throws an error as
mentioned below.
Kindly advise me, should i downgrade the koha. I have a backup of the
database on koha 21.05. Your insights would be appreciated.

Atomic updates:

    - DEV atomic update
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/
    bug_29596.pl [11:31:16]: Bug 29596 - Add Yiddish language

Update errors :

    - Upgrade to 21.11.02.003 [11:31:16]: Bug 29605 - Resync DB 
structure

    for existing installations
    ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
    entry 'ar' for key 'PRIMARY' at 
/usr/share/koha/lib/C4/Installer.pm line 738


Thanks

__

*Dr. Yesan Sellan, * *MLISc., PGDLAN, BCS., UGC-NET., PhD*


*Strategic | Learner | Achiever | Responsibility | Intellection*


*Chief Librarian*

South Asia Institute of Advanced Christian Studies (SAIACS)

363 Dodda Gubbi Cross Road, Kothanur P.O., Bangalore 77, India

Phone: 91 80 2846 5235/5344/ 5649, Fax: 91 80 28465412, Mobile:
91-9972348251

www.saiacs.org Alternative Email: yes...@gmail.com

https://orcid.org/-0002-0501-5661




__

IMPORTANT : This message is intended only for the addressee. It may 
contain

confidential information. Any unauthorized disclosure is strictly
prohibited. If you have received this message in error, please notify us
immediately so that we may correct our internal records. Please then 
delete

the original message. Thank you.



P Please consider the environment before printing this email*.*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha






--
Fridolin SOMERS 
Software and system maintainer 濾
BibLibre, France
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Upgrade Error 21.11

[Mason James]

hi folks
i added a test for this problem here...

 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19169


On 5/03/22 8:05 am, Fridolin SOMERS wrote:

Ohhh good catch

DEV atomic updates should not exist in releases.

I've added a comment on Bug report :
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29596#c16

Best regards,

Le 03/03/2022 à 21:28, Chief Librarian, SAIACS a écrit :

Hi Friends
I was testing
koha (on ubuntu 20.04) upgrade from 21.05 throws an error as
mentioned below.
Kindly advise me, should i downgrade the koha. I have a backup of the
database on koha 21.05. Your insights would be appreciated.

Atomic updates:

    - DEV atomic update
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/
    bug_29596.pl [11:31:16]: Bug 29596 - Add Yiddish language

Update errors :

    - Upgrade to 21.11.02.003 [11:31:16]: Bug 29605 - Resync DB structure
    for existing installations
    ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
    entry 'ar' for key 'PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 738

Thanks

__

*Dr. Yesan Sellan, * *MLISc., PGDLAN, BCS., UGC-NET., PhD*


*Strategic | Learner | Achiever | Responsibility | Intellection*


*Chief Librarian*

South Asia Institute of Advanced Christian Studies (SAIACS)

363 Dodda Gubbi Cross Road, Kothanur P.O., Bangalore 77, India

Phone: 91 80 2846 5235/5344/ 5649, Fax: 91 80 28465412, Mobile:
91-9972348251

www.saiacs.org Alternative Email: yes...@gmail.com

https://orcid.org/-0002-0501-5661




__

IMPORTANT : This message is intended only for the addressee. It may contain
confidential information. Any unauthorized disclosure is strictly
prohibited. If you have received this message in error, please notify us
immediately so that we may correct our internal records. Please then delete
the original message. Thank you.



P Please consider the environment before printing this email*.*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha




___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Upgrade Error 21.11

[Fridolin SOMERS]

Ohhh good catch

DEV atomic updates should not exist in releases.

I've added a comment on Bug report :
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29596#c16

Best regards,

Le 03/03/2022 à 21:28, Chief Librarian, SAIACS a écrit :

Hi Friends
I was testing
koha (on ubuntu 20.04) upgrade from 21.05 throws an error as
mentioned below.
Kindly advise me, should i downgrade the koha. I have a backup of the
database on koha 21.05. Your insights would be appreciated.

Atomic updates:

- DEV atomic update
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/
bug_29596.pl [11:31:16]: Bug 29596 - Add Yiddish language

Update errors :

- Upgrade to 21.11.02.003 [11:31:16]: Bug 29605 - Resync DB structure
for existing installations
ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
entry 'ar' for key 'PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 738

Thanks

__

*Dr. Yesan Sellan, * *MLISc., PGDLAN, BCS., UGC-NET., PhD*


*Strategic | Learner | Achiever | Responsibility | Intellection*


*Chief Librarian*

South Asia Institute of Advanced Christian Studies (SAIACS)

363 Dodda Gubbi Cross Road, Kothanur P.O., Bangalore 77, India

Phone: 91 80 2846 5235/5344/ 5649, Fax: 91 80 28465412, Mobile:
91-9972348251

www.saiacs.org Alternative Email: yes...@gmail.com

https://orcid.org/-0002-0501-5661




__

IMPORTANT : This message is intended only for the addressee. It may contain
confidential information. Any unauthorized disclosure is strictly
prohibited. If you have received this message in error, please notify us
immediately so that we may correct our internal records. Please then delete
the original message. Thank you.



P Please consider the environment before printing this email*.*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Fridolin SOMERS 
Software and system maintainer 濾
BibLibre, France
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha Upgrade Error 21.11

[Chief Librarian, SAIACS]

Hi Friends
I was testing
koha (on ubuntu 20.04) upgrade from 21.05 throws an error as
mentioned below.
Kindly advise me, should i downgrade the koha. I have a backup of the
database on koha 21.05. Your insights would be appreciated.

Atomic updates:

   - DEV atomic update
   /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/
   bug_29596.pl [11:31:16]: Bug 29596 - Add Yiddish language

Update errors :

   - Upgrade to 21.11.02.003 [11:31:16]: Bug 29605 - Resync DB structure
   for existing installations
   ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
   entry 'ar' for key 'PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 738

Thanks

__

*Dr. Yesan Sellan, * *MLISc., PGDLAN, BCS., UGC-NET., PhD*


*Strategic | Learner | Achiever | Responsibility | Intellection*


*Chief Librarian*

South Asia Institute of Advanced Christian Studies (SAIACS)

363 Dodda Gubbi Cross Road, Kothanur P.O., Bangalore 77, India

Phone: 91 80 2846 5235/5344/ 5649, Fax: 91 80 28465412, Mobile:
91-9972348251

www.saiacs.org Alternative Email: yes...@gmail.com

https://orcid.org/-0002-0501-5661




__

IMPORTANT : This message is intended only for the addressee. It may contain
confidential information. Any unauthorized disclosure is strictly
prohibited. If you have received this message in error, please notify us
immediately so that we may correct our internal records. Please then delete
the original message. Thank you.



P Please consider the environment before printing this email*.*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and Koha as a CMS)

[Isabel Pineda]

Ok, I got the static pages to work. I replaced the line 
[% IF ( OpacMainUserBlock ) %] [% PROCESS koha_news_block news => 
OpacMainUserBlock %] [% END %] in the pages.tt file with the code of the 
instruction on the site 
https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms
It is still working this way, although the original code has changed.

Thank you
Isabel Pineda


-Mensaje original-
De: Koha [mailto:koha-boun...@lists.katipo.co.nz] En nombre de Isabel Pineda
Enviado el: martes, 04 de enero de 2022 07:57 a.m.
Para: Tomas Cohen Arazi ; koha 
Asunto: Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and 
Koha as a CMS)

Hi Tomas.

Thank you so much. The coverflow is running.

Now I have to figure out how to make the static pages work again. Does anyone 
know how to do this?

Thank you for your help.
Isabel Pineda


De: Tomas Cohen Arazi [mailto:tomasco...@gmail.com] Enviado el: lunes, 03 de 
enero de 2022 06:44 p.m.
Para: Isabel Pineda 
CC: koha 
Asunto: Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and 
Koha as a CMS)

There is a comment on the coverflow configuration page about how to choose an 
id as the selector. It is important to use double quotes around the "#selector" 
because the configuration is in YAML format and as such the # symbol is 
considered a comment (i.e. Is not taken into account).

Hope it dices your issue

El lun., 3 ene. 2022 18:50, Isabel Pineda 
mailto:isabel.pin...@ds.edu.sv>> escribió:
Hi.

I know that the extensions are not strictly a part of Koha, but maybe someone 
can help me with this:

I am using the Coverflow plugin and the additional "pages" template to use Koha 
as a CMS. These things worked for me in previous Koha versions but stopped 
working after the upgrade to 21.11:

-  The Coverflow is not showing (only the "loading ..." text is there).

-  The content of the custom pages is not showing.

-  There is no error message in the web console.

-  The opac-error.log shows me a repeated error about the use of an 
uninitialized value in the file /usr/share/koha/lib/C4/XSLT.pm, but I don't 
know if this error has something to do with my problem.


What I did after the upgrade:

-  For Coverflow: I updated the Coverflow plugin to the latest version 
(2.5.0).

-  For Koha as a CMS: I overwrote the old file 
pages.pl<http://pages.pl> with a copy of the new file 
opac-main.pl<http://opac-main.pl> and followed the instructions for this file 
at 
https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms

-  For Koha as a CMS: I overwrote the old file 
pages.tt<http://pages.tt> with a copy of the new file 
opac-main.tt<http://opac-main.tt> and tried to follow the instructions for this 
file at 
https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms,
 but the line that has to be modified has changed, so here I don't know how to 
do it. But at least the content of my custom pages ought to appear without 
changing the template, I think that something must be wrong in the file 
pages.pl<http://pages.pl>.

Is there anybody who is using these extensions and can help me?

Thank you very much.
Isabel Pineda



___

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

Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and Koha as a CMS)

[Isabel Pineda]

Hi Tomas.

Thank you so much. The coverflow is running.

Now I have to figure out how to make the static pages work again. Does anyone 
know how to do this?

Thank you for your help.
Isabel Pineda


De: Tomas Cohen Arazi [mailto:tomasco...@gmail.com]
Enviado el: lunes, 03 de enero de 2022 06:44 p.m.
Para: Isabel Pineda 
CC: koha 
Asunto: Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and 
Koha as a CMS)

There is a comment on the coverflow configuration page about how to choose an 
id as the selector. It is important to use double quotes around the "#selector" 
because the configuration is in YAML format and as such the # symbol is 
considered a comment (i.e. Is not taken into account).

Hope it dices your issue

El lun., 3 ene. 2022 18:50, Isabel Pineda 
mailto:isabel.pin...@ds.edu.sv>> escribió:
Hi.

I know that the extensions are not strictly a part of Koha, but maybe someone 
can help me with this:

I am using the Coverflow plugin and the additional "pages" template to use Koha 
as a CMS. These things worked for me in previous Koha versions but stopped 
working after the upgrade to 21.11:

-  The Coverflow is not showing (only the "loading ..." text is there).

-  The content of the custom pages is not showing.

-  There is no error message in the web console.

-  The opac-error.log shows me a repeated error about the use of an 
uninitialized value in the file /usr/share/koha/lib/C4/XSLT.pm, but I don't 
know if this error has something to do with my problem.


What I did after the upgrade:

-  For Coverflow: I updated the Coverflow plugin to the latest version 
(2.5.0).

-  For Koha as a CMS: I overwrote the old file 
pages.pl<http://pages.pl> with a copy of the new file 
opac-main.pl<http://opac-main.pl> and followed the instructions for this file 
at 
https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms

-  For Koha as a CMS: I overwrote the old file 
pages.tt<http://pages.tt> with a copy of the new file 
opac-main.tt<http://opac-main.tt> and tried to follow the instructions for this 
file at 
https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms,
 but the line that has to be modified has changed, so here I don't know how to 
do it. But at least the content of my custom pages ought to appear without 
changing the template, I think that something must be wrong in the file 
pages.pl<http://pages.pl>.

Is there anybody who is using these extensions and can help me?

Thank you very much.
Isabel Pineda



___

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

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and Koha as a CMS)

[Tomas Cohen Arazi]

There is a comment on the coverflow configuration page about how to choose
an id as the selector. It is important to use double quotes around the
"#selector" because the configuration is in YAML format and as such the #
symbol is considered a comment (i.e. Is not taken into account).

Hope it dices your issue

El lun., 3 ene. 2022 18:50, Isabel Pineda 
escribió:

> Hi.
>
> I know that the extensions are not strictly a part of Koha, but maybe
> someone can help me with this:
>
> I am using the Coverflow plugin and the additional "pages" template to use
> Koha as a CMS. These things worked for me in previous Koha versions but
> stopped working after the upgrade to 21.11:
>
> -  The Coverflow is not showing (only the "loading ..." text is
> there).
>
> -  The content of the custom pages is not showing.
>
> -  There is no error message in the web console.
>
> -  The opac-error.log shows me a repeated error about the use of
> an uninitialized value in the file /usr/share/koha/lib/C4/XSLT.pm, but I
> don't know if this error has something to do with my problem.
>
>
> What I did after the upgrade:
>
> -  For Coverflow: I updated the Coverflow plugin to the latest
> version (2.5.0).
>
> -  For Koha as a CMS: I overwrote the old file pages.pl with a
> copy of the new file opac-main.pl and followed the instructions for this
> file at
> https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms
>
> -  For Koha as a CMS: I overwrote the old file pages.tt with a
> copy of the new file opac-main.tt and tried to follow the instructions
> for this file at
> https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms,
> but the line that has to be modified has changed, so here I don't know how
> to do it. But at least the content of my custom pages ought to appear
> without changing the template, I think that something must be wrong in the
> file pages.pl.
>
> Is there anybody who is using these extensions and can help me?
>
> Thank you very much.
> Isabel Pineda
>
>
>
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade to 21.11 - problems with extensions (coverflow and Koha as a CMS)

[Isabel Pineda]

Hi.

I know that the extensions are not strictly a part of Koha, but maybe someone 
can help me with this:

I am using the Coverflow plugin and the additional "pages" template to use Koha 
as a CMS. These things worked for me in previous Koha versions but stopped 
working after the upgrade to 21.11:

-  The Coverflow is not showing (only the "loading ..." text is there).

-  The content of the custom pages is not showing.

-  There is no error message in the web console.

-  The opac-error.log shows me a repeated error about the use of an 
uninitialized value in the file /usr/share/koha/lib/C4/XSLT.pm, but I don't 
know if this error has something to do with my problem.


What I did after the upgrade:

-  For Coverflow: I updated the Coverflow plugin to the latest version 
(2.5.0).

-  For Koha as a CMS: I overwrote the old file pages.pl with a copy of 
the new file opac-main.pl and followed the instructions for this file at 
https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms

-  For Koha as a CMS: I overwrote the old file pages.tt with a copy of 
the new file opac-main.tt and tried to follow the instructions for this file at 
https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms,
 but the line that has to be modified has changed, so here I don't know how to 
do it. But at least the content of my custom pages ought to appear without 
changing the template, I think that something must be wrong in the file 
pages.pl.

Is there anybody who is using these extensions and can help me?

Thank you very much.
Isabel Pineda



___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] zebra utility after koha upgrade

[Mason James]

hi George
you should not need to manually add any cronjob for indexing,

in newer koha versions (like 19.05) the indexing is handled automatically



if you are having problems with indexing, its possibly due to incorrect zebradb 
file/dir permissions

check in /var to confirm that the instance's zebra files/dirs are correctly 
owned by it's koha user

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] zebra utility after koha upgrade

[Mason James]

On 28/10/21 2:43 am, George Mikuchadze wrote:

After successful upgrading koha from v3.22.21 to v19.05.17 zebra indexer
doesn't work in the crontab.
I have the following cronjobs:
PERL5LIB=/usr/share/koha/lib
*/5 * * * * KOHA_CONF=/etc/koha/koha-conf.xml
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -z >/dev
but after 5 minutes od adding new biblioitems they are not searched.
If I run the command in the shell:
$ KOHA_CONF=/etc/koha/koha-conf.xml /usr/share/koha/bin/migration_tools/
rebuild_zebra.pl -b -a -z >/dev
the new biblioitems are appearing in serch results.
Can anybody help me to set up a crontab for the zebra rebuild utility?
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


hi George
you should not need to manually add any cronjob for indexing,

in newer koha versions (like 19.05) the indexing is handled automatically


you should see 2x 'daemon' jobs per koha instance.
 1 job for zebra searching, 1 job for zebra indexing


# /etc/init.d/koha-common status
● koha-common.service - LSB: Start required services for each Koha instance
   Loaded: loaded (/etc/init.d/koha-common; generated)
   Active: active (running) since Thu 2021-10-28 03:05:50 UTC; 3min 13s ago
 Docs: man:systemd-sysv-generator(8)
    Tasks: 4 (limit: 3394)
   Memory: 152.1M
   CGroup: /system.slice/koha-common.service
   ├─29544 daemon --name=dev1-koha-zebra --pidfiles=/var/run/koha/dev1/ 
--errlog=/var/log/koha/dev1/zebra-error.log 
--output=/var/log/koha/dev1/zebra-output.log --verb…
   ├─29547 /usr/bin/zebrasrv -v none,fatal,warn -k 1024 -f 
/etc/koha/sites/dev1/koha-conf.xml
   ├─29620 daemon --name=dev1-koha-indexer 
--errlog=/var/log/koha/dev1/indexer-error.log 
--stdout=/var/log/koha/dev1/indexer.log --output=/var/log/koha/dev1/indexer-ou…
   └─29622 /usr/bin/perl 
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 5

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] zebra utility after koha upgrade

[George Mikuchadze]

After successful upgrading koha from v3.22.21 to v19.05.17 zebra indexer
doesn't work in the crontab.
I have the following cronjobs:
PERL5LIB=/usr/share/koha/lib
*/5 * * * * KOHA_CONF=/etc/koha/koha-conf.xml
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -z >/dev
but after 5 minutes od adding new biblioitems they are not searched.
If I run the command in the shell:
$ KOHA_CONF=/etc/koha/koha-conf.xml /usr/share/koha/bin/migration_tools/
rebuild_zebra.pl -b -a -z >/dev
the new biblioitems are appearing in serch results.
Can anybody help me to set up a crontab for the zebra rebuild utility?
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade order

[Tom Burke]

Hello the list

We presently have a server with 5 instances, running 19.11.22 on Deb 9 
(stretch). Over the new few months we aim to upgrade both - from stretch to 
buster, and from 19.11 to 20.11 or maybe 21.05. Which is the best order to do 
the upgrades in? OS first, or Koha? My natural caution leads me to prefer to do 
them separately.

Tom Burke
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade procedure

[Lennon Mazonde]

Hi Tom,


a) we assume that if we wanted to move from 19.11 to 20.11, we would have to do 
it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is this a 
correct assumption?; and
It should automatically upgrade the missing versions (first 20.05 then 
20.11). I don't think you will need to specify the versions yourself.



b) does the upgrade procedure amend the database schema, etc, for 
multiple instances that are using the same Koha Common installation?


Yes, the upgrade will also automatically update the database schema for 
each of your instances if you installed Koha using packages.


I am not familiar with Debian Buster (I run my servers on Ubuntu Server 
20.04LTS) so I can't provide specific instructions for that platform. 
Here are some suggestions to get you started (I'll probably leave out 
something, so hopefully you'll get more responses from the list):


   1. Make a backup of your data. I suggest you backup your entire SQL
   database if you have any other applications running on your server,
   and any other crucial data that you can't afford to lose. Then make
   separate backups of each of your Koha instance's databases and
   config files. In Ubuntu Server, you would run the following
   (everything in red is a placeholder):
   2. To backup your entire database: *mysqldump -u username -p
   --all-databases > all-databases.sql*
   3. To backup your Koha database and configs, run this command for
   each of your instances (you can find the backups in
   /var/spool/koha/library/): *sudo koha-dump library*
   4. Copy the backup files offline or on a cloud storage service like
   Google Drive in case somethings goes awry and you can't access your
   server.
   5. Update: *sudo apt update*
   6. Upgrade: *sudo apt upgrade*
   7. You should see koha-common as one of the packages available for
   upgrading. During the upgrade, you should also see the schema being
   upgraded for each of your Koha instances. If this is not the case,
   then run:*sudo koha-upgrade-schemalibrary1 library2 etc.*

Remember to replace the commands above with Debian-specific syntax. I 
hope this helps.


Kind regards,

Lennon Mazonde
www.kohasupport.com
len...@kohasupport.com
WhatsApp @ (+1) 717.489.0195


On 8/23/21 4:50 PM, Tom Burke wrote:

Hello the list

I am a new volunteer IT help for a small number of community libraries in 
Sheffield, UK. I have been tasked with researching what we need to do to 
upgrade our Koha installation, but so far have not been able to find any 
definitive guidance. (I may of course have been looking in the wrong place.) 
I’d welcome some advice from the list, please.

We have a server running Debian Buster on which we have installed Koha 19.11 
Common. Then we have 5 actual instances configured, one each for each of the 
community libraries. We would like to upgrade from 19.11 to a later release. 
I’ve gained some experience in installing and configuring Koha to a basic 
degree on local test sites and would now like to test the upgrade procedure; 
however, I have been unable to find any documentation about the procedure to 
follow.

Among the questions I’ve got are:
a) we assume that if we wanted to move from 19.11 to 20.11, we would 
have to do it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is 
this a correct assumption?; and
b) does the upgrade procedure amend the database schema, etc, for 
multiple instances that are using the same Koha Common installation?

My apologies if I’m asking in the wrong place, or if I‘ve simply missed some 
clear instructions on all this.

Tom Burke
___

Koha mailing listhttp://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha


--
Lennon Mazonde
www.kohasupport.com
len...@kohasupport.com
WhatsApp @ (+1) 717.489.0195

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade procedure

[Lennon Mazonde]

Hi Tom,


a) we assume that if we wanted to move from 19.11 to 20.11, we would have to do 
it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is this a 
correct assumption?; and
It should automatically upgrade the missing versions (first 20.05 then 
20.11). I don't think you will need to specify the versions yourself.



b) does the upgrade procedure amend the database schema, etc, for 
multiple instances that are using the same Koha Common installation?


Yes, the upgrade will also automatically update the database schema for 
each of your instances if you installed Koha using packages.


I am not familiar with Debian Buster (I run my servers on Ubuntu Server 
20.04LTS) so I can't provide specific instructions for that platform. 
Here are some suggestions to get you started (I'll probably leave out 
something, so hopefully you'll get more responses from the list):


   1. Make a backup of your data. I suggest you backup your entire SQL
   database if you have any other applications running on your server,
   and any other crucial data that you can't afford to lose. Then make
   separate backups of each of your Koha instance's databases and
   config files. In Ubuntu Server, you would run the following
   (everything in red is a placeholder):
   2. To backup your entire database: *mysqldump -u username -p
   --all-databases > all-databases.sql*
   3. To backup your Koha database and configs, run this command for
   each of your instances (you can find the backups in
   /var/spool/koha/library/): *sudo koha-dump library*
   4. Copy the backup files offline or on a cloud storage service like
   Google Drive in case somethings goes awry and you can't access your
   server.
   5. Update: *sudo apt update*
   6. Upgrade: *sudo apt upgrade*
   7. You should see koha-common as one of the packages available for
   upgrading. During the upgrade, you should also see the schema being
   upgraded for each of your Koha instances. If this is not the case,
   then run:*sudo koha-upgrade-schemalibrary1 library2 etc.*

Remember to replace the commands above with Debian-specific syntax. I 
hope this helps.


Kind regards,

Lennon Mazonde
www.kohasupport.com
len...@kohasupport.com
WhatsApp @ (+1) 717.489.0195


On 8/23/21 4:50 PM, Tom Burke wrote:

Hello the list

I am a new volunteer IT help for a small number of community libraries in 
Sheffield, UK. I have been tasked with researching what we need to do to 
upgrade our Koha installation, but so far have not been able to find any 
definitive guidance. (I may of course have been looking in the wrong place.) 
I’d welcome some advice from the list, please.

We have a server running Debian Buster on which we have installed Koha 19.11 
Common. Then we have 5 actual instances configured, one each for each of the 
community libraries. We would like to upgrade from 19.11 to a later release. 
I’ve gained some experience in installing and configuring Koha to a basic 
degree on local test sites and would now like to test the upgrade procedure; 
however, I have been unable to find any documentation about the procedure to 
follow.

Among the questions I’ve got are:
a) we assume that if we wanted to move from 19.11 to 20.11, we would 
have to do it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is 
this a correct assumption?; and
b) does the upgrade procedure amend the database schema, etc, for 
multiple instances that are using the same Koha Common installation?

My apologies if I’m asking in the wrong place, or if I‘ve simply missed some 
clear instructions on all this.

Tom Burke
___

Koha mailing listhttp://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade procedure

[Tom Burke]

Hello the list

I am a new volunteer IT help for a small number of community libraries in 
Sheffield, UK. I have been tasked with researching what we need to do to 
upgrade our Koha installation, but so far have not been able to find any 
definitive guidance. (I may of course have been looking in the wrong place.) 
I’d welcome some advice from the list, please.

We have a server running Debian Buster on which we have installed Koha 19.11 
Common. Then we have 5 actual instances configured, one each for each of the 
community libraries. We would like to upgrade from 19.11 to a later release. 
I’ve gained some experience in installing and configuring Koha to a basic 
degree on local test sites and would now like to test the upgrade procedure; 
however, I have been unable to find any documentation about the procedure to 
follow.

Among the questions I’ve got are:
a) we assume that if we wanted to move from 19.11 to 20.11, we would 
have to do it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is 
this a correct assumption?; and
b) does the upgrade procedure amend the database schema, etc, for 
multiple instances that are using the same Koha Common installation?

My apologies if I’m asking in the wrong place, or if I‘ve simply missed some 
clear instructions on all this.

Tom Burke
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade procedure

[Katrin Fischer]

Hi Tom,

also, some information on the upgrade process can be found here:

https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade

Katrin

On 23.08.21 17:29, Katrin Fischer wrote:

Hi Tom,

others might add to this, but

a) you don't need to update from one version to another in steps/stages.
You can directly update from 19.11 to 20.11.

b) the update will take care of the database changes required for all
instances of a Koha installation.

That said, it's always recommended to do a backup before any major
update and if possible to test on a test server first.

Hope this helps,

Katrin

On 23.08.21 16:50, Tom Burke wrote:

Hello the list

I am a new volunteer IT help for a small number of community
libraries in Sheffield, UK. I have been tasked with researching what
we need to do to upgrade our Koha installation, but so far have not
been able to find any definitive guidance. (I may of course have been
looking in the wrong place.) I’d welcome some advice from the list,
please.

We have a server running Debian Buster on which we have installed
Koha 19.11 Common. Then we have 5 actual instances configured, one
each for each of the community libraries. We would like to upgrade
from 19.11 to a later release. I’ve gained some experience in
installing and configuring Koha to a basic degree on local test sites
and would now like to test the upgrade procedure; however, I have
been unable to find any documentation about the procedure to follow.

Among the questions I’ve got are:
a) we assume that if we wanted to move from 19.11 to 20.11, we
would have to do it in two stages, i.e. first to 20.05 and
subsequently to 20.11 - is this a correct assumption?; and
b) does the upgrade procedure amend the database schema, etc, for
multiple instances that are using the same Koha Common installation?

My apologies if I’m asking in the wrong place, or if I‘ve simply
missed some clear instructions on all this.

Tom Burke
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade procedure

[Katrin Fischer]

Hi Tom,

others might add to this, but

a) you don't need to update from one version to another in steps/stages.
You can directly update from 19.11 to 20.11.

b) the update will take care of the database changes required for all
instances of a Koha installation.

That said, it's always recommended to do a backup before any major
update and if possible to test on a test server first.

Hope this helps,

Katrin

On 23.08.21 16:50, Tom Burke wrote:

Hello the list

I am a new volunteer IT help for a small number of community libraries in 
Sheffield, UK. I have been tasked with researching what we need to do to 
upgrade our Koha installation, but so far have not been able to find any 
definitive guidance. (I may of course have been looking in the wrong place.) 
I’d welcome some advice from the list, please.

We have a server running Debian Buster on which we have installed Koha 19.11 
Common. Then we have 5 actual instances configured, one each for each of the 
community libraries. We would like to upgrade from 19.11 to a later release. 
I’ve gained some experience in installing and configuring Koha to a basic 
degree on local test sites and would now like to test the upgrade procedure; 
however, I have been unable to find any documentation about the procedure to 
follow.

Among the questions I’ve got are:
a) we assume that if we wanted to move from 19.11 to 20.11, we would 
have to do it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is 
this a correct assumption?; and
b) does the upgrade procedure amend the database schema, etc, for 
multiple instances that are using the same Koha Common installation?

My apologies if I’m asking in the wrong place, or if I‘ve simply missed some 
clear instructions on all this.

Tom Burke
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade procedure

[Javi Legido]

Hi there.

I strongly advise you to:

1. Find and dump the koha database (I assume MySQL engine)
2. Move from installing software on baremetal to docker containers

Cheers.

Javier


On Mon, 23 Aug 2021 at 16:50, Tom Burke  wrote:

> Hello the list
>
> I am a new volunteer IT help for a small number of community libraries in
> Sheffield, UK. I have been tasked with researching what we need to do to
> upgrade our Koha installation, but so far have not been able to find any
> definitive guidance. (I may of course have been looking in the wrong
> place.) I’d welcome some advice from the list, please.
>
> We have a server running Debian Buster on which we have installed Koha
> 19.11 Common. Then we have 5 actual instances configured, one each for each
> of the community libraries. We would like to upgrade from 19.11 to a later
> release. I’ve gained some experience in installing and configuring Koha to
> a basic degree on local test sites and would now like to test the upgrade
> procedure; however, I have been unable to find any documentation about the
> procedure to follow.
>
> Among the questions I’ve got are:
> a) we assume that if we wanted to move from 19.11 to 20.11, we
> would have to do it in two stages, i.e. first to 20.05 and subsequently to
> 20.11 - is this a correct assumption?; and
> b) does the upgrade procedure amend the database schema, etc, for
> multiple instances that are using the same Koha Common installation?
>
> My apologies if I’m asking in the wrong place, or if I‘ve simply missed
> some clear instructions on all this.
>
> Tom Burke
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04

[Isabel Pineda]

Hi Mark.

It sounds good that everything worked for you without problems. At least this 
means that I don't have to expect major difficulties during the upgrade. 
Anyway, I will have to wait until next year to do the OS upgrade, so there is 
plenty of time for planification.

Thank you 
Isabel Pineda

-Mensaje original-
De: Koha [mailto:koha-boun...@lists.katipo.co.nz] En nombre de Mark Alexander
Enviado el: viernes, 25 de junio de 2021 06:24 p.m.
Para: koha 
Asunto: Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04

Excerpts from Alvaro Cornejo's message of 2021-06-25 18:25:51 -0500:
> We also use a VPS provider (Linode) for the koha hosting.
> 
> What we do when migrating to a major version is to create a new VPS, 
> install everything from scratch, move the DB from the old system to 
> the new one, do the DB conversion and test that everything goes as expected.

I also use Linode, but I have done a similar upgrade without creating a second 
VPS and migrating the database.  Perhaps that's living a bit dangerously, but 
it worked for me.  I used Linode's backup feature to give me an escape route if 
something went wrong.  Briefly, here's what I did:

I shutdown the machine completely, and created a manual backup of the entire 
machine.  After rebooting, I did the upgrade from Debian 8 to Debian 9.  This 
was done using various apt commands.  I recall that I had to use Linode's 
out-of-band ssh service instead of normal ssh at one point, because the upgrade 
brought down Debian's network service briefly.

After the OS upgrade, I made another manual backup of the entire machine.
I also made a backup of the Koha database and configuration, and copied those 
files to my own laptop.  Finally, I did the Koha upgrade using the usual 'apt 
install koha-common'.

--
Let's organize this thing and take all
the fun out of it. --Ashleigh Brilliant
___

Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04

[Isabel Pineda]

Hi Alvaro.

Yes, this sounds like a safe way for the OS update. I think that I am going to 
do it the same way, renting a second VPS for a couple of months and doing the 
update without pressure.

Thank you
Isabel Pineda

De: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
Enviado el: viernes, 25 de junio de 2021 05:26 p.m.
Para: Isabel Pineda 
CC: koha@lists.katipo.co.nz
Asunto: Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04

Hi Isabel,

We also use a VPS provider (Linode) for the koha hosting.

What we do when migrating to a major version is to create a new VPS, install 
everything from scratch, move the DB from the old system to the new one, do the 
DB conversion and test that everything goes as expected.

As is a second VPS, we can take all the time needed to testng all the features 
we use. Once we are happy with results, we do a new DB migration since the 
installation/test process can take a couple of weeks; by then, the DB has 
certainly changed since.

Linode allows us to swap public IP addresses from one VPS to another. So 
putting the new VPS in service is quite easy (basically adjust some addresses) 
and does not require changes in DNS.

Once the migration is done we keep the old system for a couple of weeks just in 
case and then remove the old VPS.

This way allows us to work with low pressure, during normal working hours, and 
to have almost zero downtime.

Hope this helps,

Regards,

Alvaro




||
[https://drive.google.com/uc?id=1lpgSKUunPpKrvmS1rja7umnEgiqBa_vD=download]
 Stay safe / Cuídate/  Reste sécurisé
7 Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à mesure.
 q Recycle always / Recicla siempre / Recyclez toujours
 P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez 
seulement si nécessaire


Le ven. 25 juin 2021 à 15:52, Isabel Pineda 
mailto:isabel.pin...@ds.edu.sv>> a écrit :
Hi.

One of these days I will have to upgrade the OS. Currently I am running Koha on 
a VPS with Ubuntu 18.04.
I would like to ask the community for your experience: Is it advisable to 
upgrade the OS on the existing server (following the instructions here: 
https://ubuntu.com/blog/how-to-upgrade-from-ubuntu-18-04-lts-to-20-04-lts-today)?
 Or will there be problems with the Koha installation? Maybe it is better to 
install Koha on a new server with a new OS version and then migrate the 
database from the old server to the new one? Apart from Koha (and the software 
required by Koha) there are only a few more programs installed on the server 
(Certbot, Postfix, vsftpd and the firewall).

Can you tell me how you did it and if you were facing any difficulties?

Thank you very much
Isabel Pineda
___

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

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] upgrade from Koha 20.05.06.000 to latest version failing with Row size too large

[Mesfin Teshome]

 Greetings everyone,    I have been trying to upgrade Koha 20.05.06.000 to the 
latest version for some time now and every time I try I get a DBI exception 
"Row size too large" message. The full error message below:


Upgrade to 20.0t.00.030 done [18:40:59] Bug 20047 - Add new system preference 
'AutoApprovePatronProfileSettings'Upgrade to 20.06.00.031 done [18:40:59] Bug 
22789 - Add non_priority column on reserves and old_reserves tables{UNKNOWN}: 
DBI Exception: DBD::mysql::db do failed: Row size too large. The maximum row 
size for the used table type, not counting BLOBs, is 8126.This incldues 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`


Anyone who has any idea how I can address this and go on with the upgrade.I am 
running Koha on Debian 10 Buster, Perl 5.028001, Server version: Apache/2.4.38 
(Debian), mysql Ver 15.1 Distrib 10.3.29-MariaDB, for debian-linux-gnu (x86_64) 
using readline 5.2
Kind regards,




On Monday, June 28, 2021, 03:01:04 AM GMT+3, 
 wrote:  
 
 Send Koha mailing list submissions to
    koha@lists.katipo.co.nz

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.katipo.co.nz/mailman/listinfo/koha
or, via email, send a message with subject or body 'help' to
    koha-requ...@lists.katipo.co.nz

You can reach the person managing the list at
    koha-ow...@lists.katipo.co.nz

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha digest..."


Today's Topics:

  1. Re: Title search works, but Library catalog search fails in
      OPAC (Katrin Fischer)


--

Message: 1
Date: Sun, 27 Jun 2021 10:38:15 +0200
From: Katrin Fischer 
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Title search works, but Library catalog search
    fails in OPAC
Message-ID: <67a02970-fa2e-c90e-1b63-92b671b5c...@web.de>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi Tasha,

there is currently a bug about some punctuation leading to no results in
Elasticsearch that might relate to your problem:

*Bug 28316*
 - Fix
ES crashes related to various punctuation characters

Hope this helps,

Katrin

On 24.06.21 23:55, Bales (US), Tasha R wrote:
> Follow-up to my problem searching the OPAC for phrases containing punctuation 
> (i.e., Electroactive polymer (EAP) actuators).  This Bywater 
> Solutions article 
> suggests that the problem is a feature of Elasticsearch.
>
>
>
> FYI, we are using Elasticsearch 6.1.1 on its own dedicated server, and I 
> don’t believe we’ve installed the ICU Analysis plug-in (looks like it’s 
> required for Zebra, but I can’t tell if it’s required for Elasticsearch), 
> which could be a factor.  I couldn’t replicate all aspects of my experience 
> in a sandbox, although searches for phrases containing punctuation still 
> failed in an OPAC “Library Catalog” sandbox search.  I concluded that I 
> needed to review our configuration.
>
>
>
> I’ve been reviewing the Koha Wiki and elastic.co documentation, and comparing 
> to our index_config.yaml.
>
> By chance does anyone know how to interpret the syntax below?  The 
> documentation describes the parameters below, but I don’t see any usage of 
> “-“ before options.  Does the option “- punctuation“ mean “yes, remove 
> punctuation”, or “no, don’t remove punctuation”, or does the phrase refer to 
> some additional configuration file, or perhaps it’s commented out?
>
>
>
>        analyzer_phrase:
>
>          tokenizer: keyword
>
>          filter:
>
>            - icu_folding
>
>          char_filter:
>
>            - punctuation
>
>
>
> Thanks for your time and consideration,
>
>
>
>
>
> Tasha Bales
>
> Business Support Team | Information Services
>
> Enterprise Services | Enterprise Operations, Finance and Sustainability
>
>
>
>
>
> -Original Message-
>
> From: Bales (US), Tasha R
>
> Sent: Tuesday, June 22, 2021 7:54 AM
>
> To: 'Jonathan Druart' 
>
> Cc: Discussion Group Koha 
>
> Subject: RE: [EXTERNAL] Re: [Koha] Title search works, but Library catalog 
> search fails in OPAC
>
>
>
> Jonathan, thank you!
>
>
>
> It does work without the parentheses.
>
>
>
> I would suspect an encoding problem, but for that the problem only manifests 
> in the OPAC, and not the intranet.
>
>
>
> I came across this issue while testing after migrating from MariaDB to 
> Percona MySQL.  Your reply prompted me to check the encoding of the new 
> database, and it's unfortunately Latin-1.  Since these are parentheses and 
> not diacritics, I’m not sure what my expectations should be, but changing to 
> UTF-8 is a place to start.  Httpd.conf does have UTF-8 set as the default.
>
>
>
> FWIW, my source 

Re: [Koha] upgrade from Koha 20.05.06.000 to latest version failing with Row size too large

[Mason James]

hi Mesfin
this page looks helpful... 
https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb



On 28/06/21 8:17 pm, Mesfin Teshome wrote:

  Greetings everyone,    I have been trying to upgrade Koha 20.05.06.000 to the latest 
version for some time now and every time I try I get a DBI exception "Row size too 
large" message. The full error message below:


Upgrade to 20.0t.00.030 done [18:40:59] Bug 20047 - Add new system preference 
'AutoApprovePatronProfileSettings'Upgrade to 20.06.00.031 done [18:40:59] Bug 22789 
- Add non_priority column on reserves and old_reserves tables{UNKNOWN}: DBI 
Exception: DBD::mysql::db do failed: Row size too large. The maximum row size for 
the used table type, not counting BLOBs, is 8126.This incldues 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`


Anyone who has any idea how I can address this and go on with the upgrade.I am 
running Koha on Debian 10 Buster, Perl 5.028001, Server version: Apache/2.4.38 
(Debian), mysql Ver 15.1 Distrib 10.3.29-MariaDB, for debian-linux-gnu (x86_64) 
using readline 5.2
Kind regards,




 On Monday, June 28, 2021, 03:01:04 AM GMT+3, 
 wrote:
  
  Send Koha mailing list submissions to

     koha@lists.katipo.co.nz

To subscribe or unsubscribe via the World Wide Web, visit
     https://lists.katipo.co.nz/mailman/listinfo/koha
or, via email, send a message with subject or body 'help' to
     koha-requ...@lists.katipo.co.nz

You can reach the person managing the list at
     koha-ow...@lists.katipo.co.nz

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha digest..."


Today's Topics:

   1. Re: Title search works, but Library catalog search fails in
       OPAC (Katrin Fischer)


--

Message: 1
Date: Sun, 27 Jun 2021 10:38:15 +0200
From: Katrin Fischer 
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Title search works, but Library catalog search
     fails in OPAC
Message-ID: <67a02970-fa2e-c90e-1b63-92b671b5c...@web.de>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi Tasha,

there is currently a bug about some punctuation leading to no results in
Elasticsearch that might relate to your problem:

*Bug 28316*
 - Fix
ES crashes related to various punctuation characters

Hope this helps,

Katrin

On 24.06.21 23:55, Bales (US), Tasha R wrote:

Follow-up to my problem searching the OPAC for phrases containing punctuation (i.e., 
Electroactive polymer (EAP) actuators).  This Bywater 
Solutions article 
suggests that the problem is a feature of Elasticsearch.



FYI, we are using Elasticsearch 6.1.1 on its own dedicated server, and I don’t 
believe we’ve installed the ICU Analysis plug-in (looks like it’s required for 
Zebra, but I can’t tell if it’s required for Elasticsearch), which could be a 
factor.  I couldn’t replicate all aspects of my experience in a sandbox, 
although searches for phrases containing punctuation still failed in an OPAC 
“Library Catalog” sandbox search.  I concluded that I needed to review our 
configuration.



I’ve been reviewing the Koha Wiki and elastic.co documentation, and comparing 
to our index_config.yaml.

By chance does anyone know how to interpret the syntax below?  The 
documentation describes the parameters below, but I don’t see any usage of “-“ 
before options.  Does the option “- punctuation“ mean “yes, remove 
punctuation”, or “no, don’t remove punctuation”, or does the phrase refer to 
some additional configuration file, or perhaps it’s commented out?



         analyzer_phrase:

           tokenizer: keyword

           filter:

             - icu_folding

           char_filter:

             - punctuation



Thanks for your time and consideration,





Tasha Bales

Business Support Team | Information Services

Enterprise Services | Enterprise Operations, Finance and Sustainability





-Original Message-

From: Bales (US), Tasha R

Sent: Tuesday, June 22, 2021 7:54 AM

To: 'Jonathan Druart' 

Cc: Discussion Group Koha 

Subject: RE: [EXTERNAL] Re: [Koha] Title search works, but Library catalog 
search fails in OPAC



Jonathan, thank you!



It does work without the parentheses.



I would suspect an encoding problem, but for that the problem only manifests in 
the OPAC, and not the intranet.



I came across this issue while testing after migrating from MariaDB to Percona 
MySQL.  Your reply prompted me to check the encoding of the new database, and 
it's unfortunately Latin-1.  Since these are parentheses and not diacritics, 
I’m not sure what my expectations should be, but changing to UTF-8 is a place 
to start.  Httpd.conf does have 

[Koha] Upgrade Instruction

[Charles Kelley]

Hi, all!

My library would like to upgrade from Koha v. 20.05 to v. 21.05 and
Debian 9 "Stretch" to Debian 10 "Buster" or later. Are there instructions
on how to do upgrades and updates, e.g., YouTube videos?

We will probably upgrade in August or September, so there is time
aplenty to experiment, test, etc.

Many thanks!

-- 

気を付けて。 /ki wo tukete/ = Take care.

-- Charles.

Charles Kelley, MLS
PSC 704 Box 1029
APO AP 96338

Charles Kelley
Tsukimino 1-Chome 5-2
Tsukimino Gaadenia #210
Yamato-shi, Kanagawa-ken
〒242-0002 JAPAN

+1-301-741-7122 [US cell]
+81-80-4356-2178 [JPN cell]

mnogoja...@aol.com [h]
cmkelley...@gmail.com [p]

linkedin.com/in/cmkelleymls 
Meeting Your Information Needs. Virtually.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04

[Mark Alexander]

Excerpts from Alvaro Cornejo's message of 2021-06-25 18:25:51 -0500:
> We also use a VPS provider (Linode) for the koha hosting.
> 
> What we do when migrating to a major version is to create a new VPS,
> install everything from scratch, move the DB from the old system to the new
> one, do the DB conversion and test that everything goes as expected.

I also use Linode, but I have done a similar upgrade without creating a
second VPS and migrating the database.  Perhaps that's living a bit
dangerously, but it worked for me.  I used Linode's backup feature to
give me an escape route if something went wrong.  Briefly, here's what
I did:

I shutdown the machine completely, and created a manual backup of the
entire machine.  After rebooting, I did the upgrade from Debian 8 to
Debian 9.  This was done using various apt commands.  I recall that I
had to use Linode's out-of-band ssh service instead of normal ssh at
one point, because the upgrade brought down Debian's network service
briefly.

After the OS upgrade, I made another manual backup of the entire machine.
I also made a backup of the Koha database and configuration, and copied those
files to my own laptop.  Finally, I did the Koha upgrade using the usual
'apt install koha-common'.

-- 
Let's organize this thing and take all
the fun out of it. --Ashleigh Brilliant
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04

[Alvaro Cornejo]

Hi Isabel,

We also use a VPS provider (Linode) for the koha hosting.

What we do when migrating to a major version is to create a new VPS,
install everything from scratch, move the DB from the old system to the new
one, do the DB conversion and test that everything goes as expected.

As is a second VPS, we can take all the time needed to testng all the
features we use. Once we are happy with results, we do a new DB migration
since the installation/test process can take a couple of weeks; by then,
the DB has certainly changed since.

Linode allows us to swap public IP addresses from one VPS to another. So
putting the new VPS in service is quite easy (basically adjust some
addresses) and does not require changes in DNS.

Once the migration is done we keep the old system for a couple of weeks
just in case and then remove the old VPS.

This way allows us to work with low pressure, during normal working hours,
and to have almost zero downtime.

Hope this helps,

Regards,

Alvaro




||
 Stay safe / Cuídate/  Reste sécurisé
*7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
mesure.
 *q *Recycle always / Recicla siempre / Recyclez toujours
 P Print only if absolutely necessary / Imprime solo si es necesario /
Imprimez seulement si nécessaire


Le ven. 25 juin 2021 à 15:52, Isabel Pineda  a
écrit :

> Hi.
>
> One of these days I will have to upgrade the OS. Currently I am running
> Koha on a VPS with Ubuntu 18.04.
> I would like to ask the community for your experience: Is it advisable to
> upgrade the OS on the existing server (following the instructions here:
> https://ubuntu.com/blog/how-to-upgrade-from-ubuntu-18-04-lts-to-20-04-lts-today)?
> Or will there be problems with the Koha installation? Maybe it is better to
> install Koha on a new server with a new OS version and then migrate the
> database from the old server to the new one? Apart from Koha (and the
> software required by Koha) there are only a few more programs installed on
> the server (Certbot, Postfix, vsftpd and the firewall).
>
> Can you tell me how you did it and if you were facing any difficulties?
>
> Thank you very much
> Isabel Pineda
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade OS - Ubuntu 18.04 to 20.04

[Isabel Pineda]

Hi.

One of these days I will have to upgrade the OS. Currently I am running Koha on 
a VPS with Ubuntu 18.04.
I would like to ask the community for your experience: Is it advisable to 
upgrade the OS on the existing server (following the instructions here: 
https://ubuntu.com/blog/how-to-upgrade-from-ubuntu-18-04-lts-to-20-04-lts-today)?
 Or will there be problems with the Koha installation? Maybe it is better to 
install Koha on a new server with a new OS version and then migrate the 
database from the old server to the new one? Apart from Koha (and the software 
required by Koha) there are only a few more programs installed on the server 
(Certbot, Postfix, vsftpd and the firewall).

Can you tell me how you did it and if you were facing any difficulties?

Thank you very much
Isabel Pineda
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade / migration questions

[Scott Owen]

...and searching my old email...I found:

from :
Tomas Cohen Arazi 
"I suggest you create an empty instance named the same as the 'old one', so
all configuration files are fresh.
Then adjust apache and friends, rsync the /var/lib/koha/ dir,
load a DB dump and run koha-upgrade-schema "

This is from a few months ago but I'm assuming the information is still
valid  so I think I have answered my own questions.
Thanks for reading.

-S








On Fri, Jun 25, 2021 at 8:35 AM Scott Owen  wrote:

> Hi all,
>
> I am in the process of upgrading my Koha instances to a newer version.
>
> Due to the age of the current version, I am going to have to do a
> database dump / restore
>
> I am following the basic Debian install (at the wiki
> https://wiki.koha-community.org/wiki/Koha_on_Debian  )
> and have just installed the mariadb-server. (I tried the MySQL but the
> install said the MySql-server package wasn't available ?? I'm assuming this
> is by design)
>
> Before I continue with the "defaults", setup Apache, and create a Koha
> instance, I was wondering if there are any steps I should take at this
> time, if I intend to restore a database on the instance?
> Should I make sure the names are the same ?? or should I make sure to NOT
> name the db instances (library name) the same ? Does it matter ?
>
> Should I continue and do a complete Koha instance install ?? or is this
> not required if I am going to dump a db onto this server?
>
>  Thank you for any insight / advice.
>
> -S
>
>
>
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade / migration questions

[Scott Owen]

Hi all,

I am in the process of upgrading my Koha instances to a newer version.

Due to the age of the current version, I am going to have to do a
database dump / restore

I am following the basic Debian install (at the wiki
https://wiki.koha-community.org/wiki/Koha_on_Debian  )
and have just installed the mariadb-server. (I tried the MySQL but the
install said the MySql-server package wasn't available ?? I'm assuming this
is by design)

Before I continue with the "defaults", setup Apache, and create a Koha
instance, I was wondering if there are any steps I should take at this
time, if I intend to restore a database on the instance?
Should I make sure the names are the same ?? or should I make sure to NOT
name the db instances (library name) the same ? Does it matter ?

Should I continue and do a complete Koha instance install ?? or is this not
required if I am going to dump a db onto this server?

 Thank you for any insight / advice.

-S
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade planning tools and processes.

[Joonas Kylmälä]

Hi,

we had access to the Koha source code so we looked up there what changes
were done to kohastructure.sql and in our case we were lucky that we
could discard all the changes there. So basically what we did then was a
set of SQL queries that reverted the DB schema back to kohastructure.sql
from community's 17.05 koha version. So we first took the db dump from
the modified 17.05 installation, imported it to the new Koha master
version server, ran the SQL script to revert to 17.05 DB schema, ran
updatedatabase and finally configured settings now to work with the new
Koha version.

The code is available here under GPLv3:
. It is for
migrating from https://github.com/KohaSuomi/Koha/ fork of Koha.

Another thing we heavily relied upon to have similar features in KC
master version was adding our own scripts to IntranetUserJS instead of
implementing the features in Perl code. Also before the migration we
submitted maybe a dozen or so patches to community that we had in the
fork before and helped with reviewing some of the features we also
needed. Also we are using couple plugins:
https://github.com/NatLibFi/koha-plugin-rest-di and
https://github.com/NatLibFi/koha-plugin-rest-biblios

Joonas

On 30/11/2020 15:48, Raymund Delahunty wrote:
> We are looking to upgrade our relatively heavily customised version of 18.11 
> to 20.11 in maybe June 2021. Our server is hosted externally and we do not 
> have command-line access to it. The Koha system is supported and will be 
> upgraded by a software support company which specialises in supporting Koha 
> and other open source products. I'd be interested to know what upgrade 
> management tools and procedures support companies and other Koha users in a 
> position similar to us have used in the past, and how successful the upgrade 
> experience was, and if you think it was helped be less painful than it could 
> have otherwise been, given the tools and procedures you used. We have used a 
> google document managed by the support company in the past and at times I 
> found it difficult to see a timeline and to know where we were, issue by 
> issue, with the multiple issues being reported and needing advice / fixes. 
> Rather than clutter up this List I'd be happy to receive suggestions and 
> comments directly at lib-syst...@arts.ac.uk. 
> Thanks. Ray Delahunty, University of the Arts London.
> 
> 
> 
> 
> 
> This email and any attachments are intended solely for the addressee and may 
> contain confidential information. If you are not the intended recipient of 
> this email and/or its attachments you must not take any action based upon 
> them and you must not copy or show them to anyone. Please send the email back 
> to us and immediately and permanently delete it and its attachments. Where 
> this email is unrelated to the business of University of the Arts London or 
> of any of its group companies the opinions expressed in it are the opinions 
> of the sender and do not necessarily constitute those of University of the 
> Arts London (or the relevant group company). Where the sender's signature 
> indicates that the email is sent on behalf of UAL Short Courses Limited the 
> following also applies: UAL Short Courses Limited is a company registered in 
> England and Wales under company number 02361261. Registered Office: 
> University of the Arts London, 272 High Holborn, London WC1V 7EY
> ___
> 
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> 

-- 
Joonas Kylmälä
Tietojärjestelmäasiantuntija

Kansalliskirjasto
Kirjastoverkkopalvelut
PL 15 (Unioninkatu 36)
00014 Helsingin yliopisto
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Upgrade planning tools and processes.

[Raymund Delahunty]

We are looking to upgrade our relatively heavily customised version of 18.11 to 
20.11 in maybe June 2021. Our server is hosted externally and we do not have 
command-line access to it. The Koha system is supported and will be upgraded by 
a software support company which specialises in supporting Koha and other open 
source products. I'd be interested to know what upgrade management tools and 
procedures support companies and other Koha users in a position similar to us 
have used in the past, and how successful the upgrade experience was, and if 
you think it was helped be less painful than it could have otherwise been, 
given the tools and procedures you used. We have used a google document managed 
by the support company in the past and at times I found it difficult to see a 
timeline and to know where we were, issue by issue, with the multiple issues 
being reported and needing advice / fixes. Rather than clutter up this List I'd 
be happy to receive suggestions and comments directly at 
lib-syst...@arts.ac.uk. Thanks. Ray Delahunty, 
University of the Arts London.





This email and any attachments are intended solely for the addressee and may 
contain confidential information. If you are not the intended recipient of this 
email and/or its attachments you must not take any action based upon them and 
you must not copy or show them to anyone. Please send the email back to us and 
immediately and permanently delete it and its attachments. Where this email is 
unrelated to the business of University of the Arts London or of any of its 
group companies the opinions expressed in it are the opinions of the sender and 
do not necessarily constitute those of University of the Arts London (or the 
relevant group company). Where the sender's signature indicates that the email 
is sent on behalf of UAL Short Courses Limited the following also applies: UAL 
Short Courses Limited is a company registered in England and Wales under 
company number 02361261. Registered Office: University of the Arts London, 272 
High Holborn, London WC1V 7EY
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] upgrade stuck (Tē tōia, tē haumatia)

[Jonathan Druart]

It's not stuck at 17.12.00.000 (Tē tōia, tē haumatia), but the next
one: 17.12.00.001 (Bug 19724 - Add [deleted]biblio_metadata.timestamp)
It can be a bit long depending on the size of your DB. Try again and
be patient :)

Le ven. 11 sept. 2020 à 09:57, vinod mishra  a écrit :
>
> Hello
>
> Why upgrade of schema stuck at "(Tē tōia, tē haumatia)" ? however, once I
> escape and again upgrade it goes well. Is there any problem in escaping and
> executing the upgrade command again?
>
> MariaDB 10.4 and Ubuntu 18.4 koha 20.05
>
> With Regards,
>
> Vinod Kumar Mishra,
> Assistant Librarian,
> Biju Patnaik Central Library (BPCL),
> NIT Rourkela,
> Sundergadh-769008,
> Odisha,
> India.
> Mob:91+9439420860
> URL: http://vinod.itshelp.co.in/
> ORCID ID: http://orcid.org/-0003-4666-7874
>
> *"Spiritual relationship is far more precious than physical. Physical
> relationship divorced from spiritual is body without soul" -- Mahatma
> Gandhi*
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] upgrade stuck (Tē tōia, tē haumatia)

[vinod mishra]

Hello

Why upgrade of schema stuck at "(Tē tōia, tē haumatia)" ? however, once I
escape and again upgrade it goes well. Is there any problem in escaping and
executing the upgrade command again?

MariaDB 10.4 and Ubuntu 18.4 koha 20.05

With Regards,

Vinod Kumar Mishra,
Assistant Librarian,
Biju Patnaik Central Library (BPCL),
NIT Rourkela,
Sundergadh-769008,
Odisha,
India.
Mob:91+9439420860
URL: http://vinod.itshelp.co.in/
ORCID ID: http://orcid.org/-0003-4666-7874

*"Spiritual relationship is far more precious than physical. Physical
relationship divorced from spiritual is body without soul" -- Mahatma
Gandhi*
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from Koha 3.08.07

[Nigel Titley]

On 10/09/2020 08:24, Jonathan Druart wrote:
> Late hi!

No problem, better late than never!

> Yes Nigel, your upgrade steps are exactly what need to be done.
> However step "10" must be "restart all the things", which is:
> memcached, apache2 and plack.

OK... useful to know. I had done a machine reboot which probably took
care of that.

> And, optionally, 11. check the about page if everything is ok ("server
> information" and "system information" tabs)

Yes... I did a test check in and check out and got the known error
related to Maria/Mysql so followed the excellent wiki article to
(fingers crossed) fix the autonumbering problem with INNODB

> Enjoy the new features :)

I am!

Nigel
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from Koha 3.08.07

[Jonathan Druart]

Late hi!

Yes Nigel, your upgrade steps are exactly what need to be done.
However step "10" must be "restart all the things", which is:
memcached, apache2 and plack.
And, optionally, 11. check the about page if everything is ok ("server
information" and "system information" tabs)

Enjoy the new features :)
Regards,
Jonathan

Le mer. 9 sept. 2020 à 19:13, Nigel Titley  a écrit :
>
>
>
> On 09/09/2020 17:24, Nigel Titley wrote:
> >
> >> And answering my own question, it looks like it might be possible to
> >> export the book inventory in MARC format and the Patrons as a CSV file.
> >> And possibly the transactions in an offline format? If the worst comes
> >> to the worst I can lose the transactions.
> >>
> >> Does that sound like a plan?
> >
> > And answering my own question again it looks like that all I have to do
> > is dump the database on the old machine, copy it across and install it
> > on the new machine. The schema upgrade *should* be able to cope as I'm
> > running a koha instance later than 3.4
>
> And this indeed worked... so everyone please ignore my witterings. The
> procedure I followed was
>
> 1. Install latest koha on the new machine
> 2. Use mysqldump to dump the whole koha database on the old machine
> 3. Copy across to new machine
> 4. Use "koha-create --create-db " to create a koha instance on
> the new machine
> 5. Drop the new empty database  created by step 4
> 6. Create a new empty database 
> 7. Use mysql to import the dump you made in step 2 into 
> 8. Run koha-upgrade-schema 
> 9. Run koha-rebuild-zebra -v -f 
> 10. Restart apache (possibly not necessary but doesn't do any harm)
>
> I now seem to have a fully functional new koha on a new machine
>
> Thanks everyone (I know no one said anything but you were all there in
> spirit)
>
> Nigel
>
>
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha