Re: [Koha] Upgrade failure

[Daniel Owens]

Hang on, I just reran the upgrade, and it succeeded. Please ignore this 
message.


Daniel

On 7/16/24 10:09 AM, Daniel Owens wrote:


I was upgrading my packages on Ubuntu this morning and the upgrade 
failed. The step that failed was:


Upgrade to 23.12.00.044  [14:48:14]: Bug 36120 - Add pickup
location to bookings
    Added column 'bookings.pickup_library_id'
    Set existing bookings pickup location to item homebranch
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot
change column 'pickup_library_id': used in a foreign key
constraint 'bookings_ibfk_4' at
/usr/share/koha/lib/C4/Installer.pm line 741

The first step in the upgrade was to 23.12.00.000, if that's helpful. 
I am not sure exactly which version I started from but will probably 
be downgrading to oldstable until I can resolve this.


Any suggestions for resolving this?

Daniel


___

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?

[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

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

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

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] 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

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] 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

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 
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 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

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

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

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

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

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

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

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 

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

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

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

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

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

Re: [Koha] Upgrade from Koha 3.08.07

[Alex Shepherd]

Thanks Nigel for reporting your success. I have an upgrade from Ubuntu 16.04 / 
Koha 17.11 and wonder about such things. In need to clone my VM and try and 
upgrade but I’ve been putting t off...

Your success of a much harder upgrade is very encouraging.

Regards
Alex Shepherd

Sent from my iPad

> On 10/09/2020, at 5:14 AM, Nigel Titley  wrote:
> 
> 
> 
>> 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

Re: [Koha] Upgrade from Koha 3.08.07

[Nigel Titley]

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

Re: [Koha] Upgrade from Koha 3.08.07

[Nigel Titley]

> 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

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

[Nigel Titley]

On 09/09/2020 15:34, Nigel Titley wrote:
> I'm running an extremely antique version of Koha 3.08.07 on Debian Squeeze.
> 
> For various reasons (mainly the fact that the system is enormously
> stable) nothing has been upgraded for a long while but it's getting to
> the point where I need to upgrade it. I'm planning at the same time to
> move Koha off onto a new system running the latest Ubuntu LTS. I'm happy
> with installing a brand-new Koha but how do I go about transferring the
> data. I've found instructions for shifting the database but will the
> database schema upgrade work with that huge a jump? It's not a huge
> library, just a couple of thousand books.
> 
> Thanks for any help that anyone can offer.

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?

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 16.11, Ubuntu 16.04 to koha 17.05, 17.11 --not usable for check out

[Alvaro Cornejo]

Hi Heinrich,

You should replace your database/instance name where needed.

The backup I was referring to is a mysqldump of your original DB 16.11.

See below other comments,

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 lun. 6 juil. 2020 à 16:14, Heinrich Hartl  a écrit :

> Hallo Alvaro,
>
> I run my server as a vmware virtual machine - so it is very easy for me to
> return to a snapshot.
>
> Following your advice (but starting with the current state virtual machine
> running koha 17.11 ) I did
> #sudo koha-upgrade-schema YourInstance
> #sudo koha-rebuild-zebra -v -f YourInstance
>
> Unfortunately my problem persisted.
>
Have you seen any specific error in the process?


> ===
>
> I resume an earlier (koha17.05, Ubuntu 16.04=Xenial) snapshot
> root@koha-VM-dev:/home/hhl #
>  mysql -uroot -p
> Enter password:
> Welcome to the MySQL monitor.  Commands end with ; or \g.
> Your MySQL connection id is 26
> Server version: 5.7.30-0ubuntu0.16.04.1 (Ubuntu)
>
> Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights
> reserved.
>
> Oracle is a registered trademark of Oracle Corporation and/or its
> affiliates. Other names may be trademarks of their respective
> owners.
>
> Type 'help;' or '\h' for help. Type '\c' to clear the current input
> statement.
>
> mysql> drop database koha_library;
> Query OK, 193 rows affected (1,10 sec)
>
If this is ok then it means your instance db was called koha_library. Else
it should have given an error. So we are ok with koha_library as your DB
name


> mysql> create database koha_library;
> Query OK, 1 row affected (0,00 sec)
>
> mysql> quit
> Bye
>
>  I did not substitute koha_library assuming this is a database not
> specific to library-instances.
> My only library-instance happens to be named library.
>
There is only one DB per instance. There is no a "generic" DB for koha


>
> Loadding my database however failed.
> I tried koha-restore # that failed
>
You can not use koha-restore since you have different versions for db &
koha code


> I repeated
> #mysql -uroot -p
> >drop database koha_library;
> >create database koha_library;
> >quit;
>
the create database just create an empty DB, no tables, no data.

And then
> #mysql -uroot -p
> #mysql -uroot -p koha_library < library-2020-06-24.sql
>

You might try to get a new 16.11 backup with
#sudo su
#mysqldump -uroot -p koha_library | gzip  > koha_library.sql.gz (you might
skip the compression if your DB is not too big)

Before loading the backup uncompress it
Once successful upload, you need to upgrade the schema and rebuild your
index

Also, if have memcached and/or plack enabled, you need to restart them

Hope this helps



>  the input file I used comes from koha-dump (16.11) as
> library-2020-06-24.sql.gz ans was expanded using gunzip.
> -- endless errors filled my terminalbuffer.
> Are you referring to some other DB backupformat?
>
> Best regards
> Heinrich
> ==
>
>
> Am 06.07.20 um 20:25 schrieb Alvaro Cornejo:
>
> Hi Heinrich
>
> It seems the db upgrade schema had an error in the upgrade process.
>
> I'll suggest you try to run the db upgrade schema to see if that works.
> Always do a DB backup before tweaking it.
>
> #sudo koha-upgrade-schema YourInstance
> Then recreate your index
> #sudo koha-rebuild-zebra -v -f YourInstance
>
> Do you have a 16.11 BD backup? If so you can restart the db process from
> scratch.
>
> Enter mysql and delete current koha DB
> #sudo su
> #mysql -uroot -p
>
> >drop database koha_library;
> >create database koha_library;
> >quit;
>
> Load your backup
> #sudo su
> #mysql -uroot -p koha_library < koha_library.sql
> #exit
> (koha_library is your DB name created above)
> (koha_library.sql is your db backup)
>
> Upgrade your DB
> #sudo koha-upgrade-schema YourInstance
>
> Recreate your index
> #sudo koha-rebuild-zebra -v -f YourInstance
>
> Else check the upgrade log to find the table(s) that were not
> upgraded/created and do it manually.
>
> 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 lun. 6 juil. 2020 à 03:55, Heinrich Hartl  a écrit :
>
>>
>>   Software error:
>>
>> Template process failed: undef error -
>> DBIx::Class::Storage::DBI::_dbh_execute(): 

Re: [Koha] upgrade from koha 16.11, Ubuntu 16.04 to koha 17.05, 17.11 --not usable for check out

[Heinrich Hartl]

Hallo Alvaro,

I run my server as a vmware virtual machine - so it is very easy for me
to return to a snapshot.

Following your advice (but starting with the current state virtual
machine running koha 17.11 ) I did

#sudo koha-upgrade-schema YourInstance
#sudo koha-rebuild-zebra -v -f YourInstance

Unfortunately my problem persisted.

===

I resume an earlier (koha17.05, Ubuntu 16.04=Xenial) snapshot
root@koha-VM-dev:/home/hhl #
 mysql -uroot -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 26
Server version: 5.7.30-0ubuntu0.16.04.1 (Ubuntu)

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.

mysql> drop database koha_library;
Query OK, 193 rows affected (1,10 sec)

mysql> create database koha_library;
Query OK, 1 row affected (0,00 sec)

mysql> quit
Bye

 I did not substitute koha_library assuming this is a database not
specific to library-instances.
My only library-instance happens to be named library.


Loadding my database however failed.
I tried koha-restore # that failed
    I repeated
    #mysql -uroot -p
    >drop database koha_library;
    >create database koha_library;
    >quit;
And then
#mysql -uroot -p
#mysql -uroot -p koha_library < library-2020-06-24.sql

 the input file I used comes from koha-dump (16.11) as
library-2020-06-24.sql.gz ans was expanded using gunzip.
-- endless errors filled my terminalbuffer.
Are you referring to some other DB backupformat?

Best regards
Heinrich
==


Am 06.07.20 um 20:25 schrieb Alvaro Cornejo:

Hi Heinrich

It seems the db upgrade schema had an error in the upgrade process.

I'll suggest you try to run the db upgrade schema to see if that works.
Always do a DB backup before tweaking it.

#sudo koha-upgrade-schema YourInstance
Then recreate your index
#sudo koha-rebuild-zebra -v -f YourInstance

Do you have a 16.11 BD backup? If so you can restart the db process
from scratch.

Enter mysql and delete current koha DB
#sudo su
#mysql -uroot -p

>drop database koha_library;
>create database koha_library;
>quit;

Load your backup
#sudo su
#mysql -uroot -p koha_library < koha_library.sql
#exit
(koha_library is your DB name created above)
(koha_library.sql is your db backup)

Upgrade your DB
#sudo koha-upgrade-schema YourInstance

Recreate your index
#sudo koha-rebuild-zebra -v -f YourInstance

Else check the upgrade log to find the table(s) that were not
upgraded/created and do it manually.

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
PPrint only if absolutely necessary / Imprime solo si es necesario /
Imprimez seulement si nécessaire


Le lun. 6 juil. 2020 à 03:55, Heinrich Hartl mailto:h-ha...@gmx.de>> a écrit :


  Software error:

Template process failed: undef error -
DBIx::Class::Storage::DBI::_dbh_execute(): Table
'koha_library.club_enrollments' doesn't exist at
/usr/share/koha/lib/Koha/Objects.pm line 269

For help, please send mail to the webmaster ([no address given]
), giving this error message and the
time and
date of the error.

==

koha 16.11 is working fine.

This error comes after upgrading koha 16.11 to koha 17.05. The error
persists when I upgrade to 17.11

(I tried 17.11 - hoping the problem in 17.05 would be corrected
with 17.11)

I can log in into koha, can search the catalog and apparently I can do
everything apart from checking out books to patrons!

I enter a partial name in the patron field, I search, I get a list of
matching patrons, I select one and *here comes the bug* as above.


Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-184-generic x86_64)

And from koha /about:

Server information Koha version:        17.11.18.000
OS version ('uname -a'):        Linux koha-VM-dev 4.4.0-184-generic
#214-Ubuntu SMP Thu Jun 4 10:14:11 UTC 2020 x86_64
Perl interpreter:       /usr/bin/perl
Perl version:   5.022001
Perl @INC:      /usr/share/koha/lib
/etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1
/usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22
/usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.22
/usr/share/perl/5.22
/usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base
.
MySQL version:  mysql Ver 14.14 Distrib 5.7.30, for Linux (x86_64)
using
EditLine wrapper
Apache version:     

Re: [Koha] upgrade from koha 16.11, Ubuntu 16.04 to koha 17.05, 17.11 --not usable for check out

[Alvaro Cornejo]

Hi Heinrich

It seems the db upgrade schema had an error in the upgrade process.

I'll suggest you try to run the db upgrade schema to see if that works.
Always do a DB backup before tweaking it.

#sudo koha-upgrade-schema YourInstance
Then recreate your index
#sudo koha-rebuild-zebra -v -f YourInstance

Do you have a 16.11 BD backup? If so you can restart the db process from
scratch.

Enter mysql and delete current koha DB
#sudo su
#mysql -uroot -p

>drop database koha_library;
>create database koha_library;
>quit;

Load your backup
#sudo su
#mysql -uroot -p koha_library < koha_library.sql
#exit
(koha_library is your DB name created above)
(koha_library.sql is your db backup)

Upgrade your DB
#sudo koha-upgrade-schema YourInstance

Recreate your index
#sudo koha-rebuild-zebra -v -f YourInstance

Else check the upgrade log to find the table(s) that were not
upgraded/created and do it manually.

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 lun. 6 juil. 2020 à 03:55, Heinrich Hartl  a écrit :

>
>   Software error:
>
> Template process failed: undef error -
> DBIx::Class::Storage::DBI::_dbh_execute(): Table
> 'koha_library.club_enrollments' doesn't exist at
> /usr/share/koha/lib/Koha/Objects.pm line 269
>
> For help, please send mail to the webmaster ([no address given]
> ), giving this error message and the time and
> date of the error.
>
> ==
>
> koha 16.11 is working fine.
>
> This error comes after upgrading koha 16.11 to koha 17.05.  The error
> persists when I upgrade to 17.11
>
> (I tried 17.11 - hoping the problem in 17.05 would be corrected with 17.11)
>
> I can log in into koha, can search the catalog and apparently I can do
> everything apart from checking out books to patrons!
>
> I enter a partial name in the patron field, I search, I get a list of
> matching patrons, I select one and *here comes the bug* as above.
>
>
> Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-184-generic x86_64)
>
> And from koha /about:
>
> Server information Koha version:17.11.18.000
> OS version ('uname -a'):Linux koha-VM-dev 4.4.0-184-generic
> #214-Ubuntu SMP Thu Jun 4 10:14:11 UTC 2020 x86_64
> Perl interpreter:   /usr/bin/perl
> Perl version:   5.022001
> Perl @INC:  /usr/share/koha/lib
> /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.22.1
> /usr/local/share/perl/5.22.1
> /usr/lib/x86_64-linux-gnu/perl5/5.22
> /usr/share/perl5
> /usr/lib/x86_64-linux-gnu/perl/5.22
> /usr/share/perl/5.22
> /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base
> .
> MySQL version:  mysql Ver 14.14 Distrib 5.7.30, for Linux (x86_64) using
> EditLine wrapper
> Apache version: Server version: Apache/2.4.18 (Ubuntu)
> Memcached:  Servers: undefined | Namespace: undefined | Status: unknown
> | Config read from: Nowhere Note that the right place to define the
> memcached config is in your $KOHA_CONF file. Currently you do not have a
> valid memcached configuration defined. | Effective caching method:
> Zebra version:  Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
> software, covered by the GNU General Public License, and you are welcome
> to change it and/or distribute copies of it under certain conditions.
> SHA1 ID: c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU
>
>
>
>
>
> Best regards
> Heinrich Hartl
> Spessartstr. 50
> 63457 Hanau-Großauheim
> Telefon 06181 9564 40
> Mobile 0163 640 3268
>
> ___
>
> 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: Ubuntu 16.04.6 LTS / Koha 17.11.18.000

[Alvaro Cornejo]

Hi Alex,

We just move from Ubuntu 16.04 to 18.04,  koha from 17.05 to 19.11 and went
from a 1core 2GB Ram box to a 2 core 4 GB Ram box.

What we did was to install everything from scratch in a new Linode  and
then move the DB from old machine to the new one. Do all tests needed and
when satisfied, swap IP between the old linode to the new one. This is a
feature from Linode the avoid moving DNS entries when replacing servers.
This way give us all the peace of mind required and production site was not
touched until the IP swap.

About upgrading OS, you might want to check your Yaz & Zebra versions for
compatibility and dependencies.

About your DB scripts, you might not needed anymore since issue was fixed
by mysql/mariadb. You can check versions in koha wiki.

We use this guide for moving the DB (
http://kohageek.blogspot.com/2015/08/move-old-koha-database-to-new.html )
In your case, you will need to repeat the mysqldump part for each instance.

We will keep old linode for about a month and then delete it. We will pay
for two linodes for about 2 months.

Regards

Alvaro



|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
  Visitenos en www.perusms.com


Le mar. 28 janv. 2020 à 16:15, Alex Shepherd  a écrit :

> Hi Guys,
>
> I’m needing to update my Koha server that hosts 8 separate instances of
> Koha and just looking for any advice or guidance to reduce disappointment…
>
> Its on a Digital Ocean Droplet, which I’ve taken a SnapShot of and will
> test the upgrade on a cloned test instance from the snapshot before doing
> it on production, so its low risk but I want to avoid unforeseen issues
> that may not show-up for a while.
>
> I’m aware of the notes here:
> https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Upgrade_Instructions
> but they are quite brief and I kinda expect more issues than “it just
> works”… Maybe it does - I don’t know yet.
>
> It is currently running:
>
> Ubuntu 16.04.6 LTS
> Koha 17.11.18.000
> MariaDB 10.0.38-MariaDB-0ubuntu0.16.04.1
>
> The only “special” things I’ve done to this server are:
>
> A) install the IndexData repos:
>
>   http://ftp.indexdata.dk/ubuntu xenial InRelease
>   http://ftp.indexdata.dk/ubuntu xenial Release
>
>   to upgrade Yaz and Zebra as there were issue with my Koha instances
> handling some Asian languages (Thai I believe) that were improved with the
> later versions.
>
> B) Add the Startup scripts to each MySQL DB to reset the sequence numbers
> etc on boot.
>
>
> Questions in my mind:
>
> 1) Do I just alter the APT Koha repo to say 19.11 and run update/upgrade
> in one step or is there a need to step through each major version to get
> there?
>
> 1) Should I also upgrade Ubuntu to 18.04 LTS or just leave it on 16.04
> LTS? This might affect the Yaz and Zebra versions as well.
>
> Any comments or advice?
>
> Regards
>
> Alex Shepherd
>
> p: +64-7-829 4441
> m: +64-21-64
> e: kiwi64...@gmail.com
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade Koha from 18.05.x to 18.11.x

[koha_learner]

Dear Michael,

Thanks a lot, it works.

Regards,

Zahid Hossain Shoeb




--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade Koha from 18.05.x to 18.11.x

[Michael Kuhn]

Hi Zahid Hossain

> How to upgrade Koha 18.05.x to Koha 18.11.x on Debian 9?
> I have tried but the changes happened from 18.05.05.000 to
> 18.05.11.000 only.
> The commands were -
>
> apt-get update
> apt-get upgrade
> apt-get install koha-common
> koha-rebuild-zebra -v -f 
>
> I have not provided any command to upgrade the schema, though tables
> of the database changed from 198 to 205 in the current version.
> Cooperation in this regard will be highly appreciated.

You will probably need to adapt your file 
"/etc/apt/sources.list.d/koha.list" to either


deb http://debian.koha-community.org/koha 18.11 main

or

deb http://debian.koha-community.org/koha stable main

depending on what you're intending to do in the future. The following 
wiki page gives information about this an more:A good source on


* https://wiki.koha-community.org/wiki/Koha_on_Debian

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
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to Koha 18.11 on Ubuntu 16.04

[Tomas Cohen Arazi]

Did you run:

 $ sudo apt update

before trying to upgrade?


El mié., 23 ene. 2019 a las 8:00, user233162 ()
escribió:

> Hi,
>
> I have instance of Koha 17.11.05 installed on an Ubuntu
> 16.04 LTS. I would like to upgrade Koha to the current
> version 18.11., but I get the error:
>
> sudo apt-get install koha-common
>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> koha-common is already the newest version (17.11.05-1).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> Any idea how resolve this problem please?
>
> Many thanks,
>
> Karel Matějka
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> 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
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to Koha 18.11 on Ubuntu 16.04

[Renvoize, Martin]

Hmm, how did you setup your debian repositories; to follow suit or codename
(https://wiki.koha-community.org/wiki/Debian#Set_up_package_sources) ?.

Either way I'm surprised by your results.. If your tracking by codename and
it's set to 17.11 I would have expected a significantly more recent 17.11
to have been installed.

I'll raise this with the packaging manager for you and see if he can help
shed some light on this for you.

*Martin Renvoize*



Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

*Email:* martin.renvo...@ptfs-europe.com

*Fax:* +44 (0) 800 756 6384


www.ptfs-europe.com







Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30

The information contained in this email message may be privileged,
confidential and protected from disclosure. If you are not the intended
recipient, any dissemination, distribution or copying is strictly
prohibited. If you think that you have received this email message in
error, please email the sender at i...@ptfs-europe.com



On Wed, 23 Jan 2019 at 11:00, user233162  wrote:

> Hi,
>
> I have instance of Koha 17.11.05 installed on an Ubuntu
> 16.04 LTS. I would like to upgrade Koha to the current
> version 18.11., but I get the error:
>
> sudo apt-get install koha-common
>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> koha-common is already the newest version (17.11.05-1).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> Any idea how resolve this problem please?
>
> Many thanks,
>
> Karel Matějka
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] upgrade to Koha 18.11 on Ubuntu 18.04

[Giuseppe Angilella]

Many thanks, Salvo!

The update to Koha 18.11 worked after I issued the command

sudo apt install libhttp-oai-3.27-perl

as you kindly suggested.

I chose to maintain my old /etc/koha/koha-sites.conf , although a later 
comparison with koha-sites.conf.dpkg-dist as provided by the new package 
did not evidence any major difference. (The new configuration does not 
include the options BIBLIOS_INDEXING_MODE="dom" and 
AUTHORITIES_INDEXING_MODE="dom", and by default sets USE_MEMCACHED="yes", 
while I had "no".)


A first run immediately after the update seemed to exhibit some 
inconsistencies in the appearance of the -intra page, but these 
disappeared after a reboot and a page refresh on my browser.


There is some change perhaps in the opac page (e.g. background colour) 
which I may have to reset manually, but one should always be ready to some 
minor change after an upgrade.


While googling for a solution, I've also stumbled in the following bug, 
which I quote for later reference:


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

Many thanks and best regards,

Giuseppe.

On Sat, 29 Dec 2018, Salvatore Toscano wrote:


Hi
using the Synaptic package controller (sudo apt-get update /sudo apt-get
install synaptic), look for the package libhttp-oai-3.27-perl (version
3.27-1~Koha+1) and check if it is installed.
If not found try to install it.
I have a debian buster/sid distribution and I verified that the koha-common
package is updated to version 18.11.01-1 with the libhttp-oai-3.27-perl
package installed.
The libhttp-oai-perl package (version 3.08-1) is also downloaded from the
repositories, but it has not been installed.
I hope I have given the correct information.

Best regards from Catania (Italy)

Salvo.
Il giorno ven 28 dic 2018 alle ore 17:55 Giuseppe Angilella
 ha scritto:
  Hi,

  I have a (working) instance of Koha 17.11.05-1 installed on an
  Ubuntu
  18.01.1 LTS (bionic) machine. I would like to upgrade Koha to
  the current
  version 18.11.01-1, but I get the error:

  sudo apt upgrade koha-common

  Some packages could not be installed. This may mean that you
  have
  requested an impossible situation or if you are using the
  unstable
  distribution that some required packages have not yet been
  created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
    koha-common : Depends: libhttp-oai-perl (< 4.0) but 4.06-1 is
  to be installed or
                           libhttp-oai-3.27-perl but it is not
  going to be installed
  E: Broken packages

  Any hint on how to resolve my problem?

  Many thanks in advance and best regards,

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




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

Re: [Koha] Upgrade issues

[Scott Owen]

Koha version: 17.11.06.000

-- Thank you Sir 

Info added to Bugzilla as per Mr. Druarts' request.




On Fri, Jun 15, 2018 at 10:18 AM, Tomas Cohen Arazi 
wrote:

> So it is trying to upgrade you to 18.05. Are you sure you want that? I
> suggest that you replace 'stable' with '17.11' for now.
>
> Kind regards.
>
> El vie., 15 jun. 2018 a las 11:03, Scott Owen ()
> escribió:
>
>>
>>
>>
>> deb http://debian.koha-community.org/koha stable main
>>
>> On Fri, Jun 15, 2018 at 9:55 AM, Tomas Cohen Arazi 
>> wrote:
>>
>>> Can you share your /etc/apt/sources.list.d/koha.list config?
>>>
>>> El vie., 15 jun. 2018 a las 10:39, Scott Owen ()
>>> escribió:
>>>
 Hi all,

 I'm trying to upgrade my Koha version...but got stopped at the
 following:


 root@Pine:~# sudo apt-get install koha-common
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  koha-common : Depends: libnet-oauth2-authorizationserver-perl but it
 is
 not going to be installed
 E: Unable to correct problems, you have held broken packages.
 root@Pine:~#


 current server:

 Server information
 Koha version: 17.05.05.000
 OS version ('uname -a'): Linux Pine 3.16.0-4-686-pae #1 SMP Debian
 3.16.43-2+deb8u5 (2017-09-19) i686
 Perl interpreter: /usr/bin/perl
 Perl version: 5.020002
 Perl @INC: /usr/share/koha/lib
 /etc/perl
 /usr/local/lib/i386-linux-gnu/perl/5.20.2
 /usr/local/share/perl/5.20.2
 /usr/lib/i386-linux-gnu/perl5/5.20
 /usr/share/perl5
 /usr/lib/i386-linux-gnu/perl/5.20
 /usr/share/perl/5.20
 /usr/local/lib/site_perl
 .
 MySQL version: mysql Ver 14.14 Distrib 5.5.60, for debian-linux-gnu
 (i686)
 using readline 6.3
 Apache version: Server version: Apache/2.4.10 (Debian)
 Memcached: Servers: undefined | Namespace: koha | Status: unknown |
 Config
 read from: Nowhere Note that the right place to define the memcached
 config
 is in your $KOHA_CONF file. Currently you do not have a valid memcached
 configuration defined. | Effective caching method: Cache::Memory
 Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
 software, covered by the GNU General Public License, and you are
 welcome to
 change it and/or distribute copies of it under certain conditions. SHA1
 ID:
 c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU



 My Googling skills have failed me and I couldn't find the "dummies"
 version
 of how to fix this ?
 Am I missing a repository ? If so ...what is the correct command to add
 it
 ?/

 Thank you

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

>>> --
>>> Tomás Cohen Arazi
>>> Theke Solutions (https://theke.io )
>>> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
>>> GPG: B2F3C15F
>>>
>>
>> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io )
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade issues

[Jonathan Druart]

Please comment with your info on
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20826

On Fri, 15 Jun 2018 at 11:03 Scott Owen  wrote:

> deb http://debian.koha-community.org/koha stable main
>
> On Fri, Jun 15, 2018 at 9:55 AM, Tomas Cohen Arazi 
> wrote:
>
> > Can you share your /etc/apt/sources.list.d/koha.list config?
> >
> > El vie., 15 jun. 2018 a las 10:39, Scott Owen ()
> > escribió:
> >
> >> Hi all,
> >>
> >> I'm trying to upgrade my Koha version...but got stopped at the
> following:
> >>
> >>
> >> root@Pine:~# sudo apt-get install koha-common
> >> Reading package lists... Done
> >> Building dependency tree
> >> Reading state information... Done
> >> Some packages could not be installed. This may mean that you have
> >> requested an impossible situation or if you are using the unstable
> >> distribution that some required packages have not yet been created
> >> or been moved out of Incoming.
> >> The following information may help to resolve the situation:
> >>
> >> The following packages have unmet dependencies:
> >>  koha-common : Depends: libnet-oauth2-authorizationserver-perl but it is
> >> not going to be installed
> >> E: Unable to correct problems, you have held broken packages.
> >> root@Pine:~#
> >>
> >>
> >> current server:
> >>
> >> Server information
> >> Koha version: 17.05.05.000
> >> OS version ('uname -a'): Linux Pine 3.16.0-4-686-pae #1 SMP Debian
> >> 3.16.43-2+deb8u5 (2017-09-19) i686
> >> Perl interpreter: /usr/bin/perl
> >> Perl version: 5.020002
> >> Perl @INC: /usr/share/koha/lib
> >> /etc/perl
> >> /usr/local/lib/i386-linux-gnu/perl/5.20.2
> >> /usr/local/share/perl/5.20.2
> >> /usr/lib/i386-linux-gnu/perl5/5.20
> >> /usr/share/perl5
> >> /usr/lib/i386-linux-gnu/perl/5.20
> >> /usr/share/perl/5.20
> >> /usr/local/lib/site_perl
> >> .
> >> MySQL version: mysql Ver 14.14 Distrib 5.5.60, for debian-linux-gnu
> (i686)
> >> using readline 6.3
> >> Apache version: Server version: Apache/2.4.10 (Debian)
> >> Memcached: Servers: undefined | Namespace: koha | Status: unknown |
> Config
> >> read from: Nowhere Note that the right place to define the memcached
> >> config
> >> is in your $KOHA_CONF file. Currently you do not have a valid memcached
> >> configuration defined. | Effective caching method: Cache::Memory
> >> Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
> >> software, covered by the GNU General Public License, and you are welcome
> >> to
> >> change it and/or distribute copies of it under certain conditions. SHA1
> >> ID:
> >> c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU
> >>
> >>
> >>
> >> My Googling skills have failed me and I couldn't find the "dummies"
> >> version
> >> of how to fix this ?
> >> Am I missing a repository ? If so ...what is the correct command to add
> it
> >> ?/
> >>
> >> Thank you
> >>
> >> -S
> >> ___
> >> Koha mailing list  http://koha-community.org
> >> Koha@lists.katipo.co.nz
> >> https://lists.katipo.co.nz/mailman/listinfo/koha
> >>
> > --
> > Tomás Cohen Arazi
> > Theke Solutions (https://theke.io )
> > ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
> > GPG: B2F3C15F
> >
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade issues

[Tomas Cohen Arazi]

So it is trying to upgrade you to 18.05. Are you sure you want that? I
suggest that you replace 'stable' with '17.11' for now.

Kind regards.

El vie., 15 jun. 2018 a las 11:03, Scott Owen () escribió:

>
>
>
> deb http://debian.koha-community.org/koha stable main
>
> On Fri, Jun 15, 2018 at 9:55 AM, Tomas Cohen Arazi 
> wrote:
>
>> Can you share your /etc/apt/sources.list.d/koha.list config?
>>
>> El vie., 15 jun. 2018 a las 10:39, Scott Owen ()
>> escribió:
>>
>>> Hi all,
>>>
>>> I'm trying to upgrade my Koha version...but got stopped at the following:
>>>
>>>
>>> root@Pine:~# sudo apt-get install koha-common
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Some packages could not be installed. This may mean that you have
>>> requested an impossible situation or if you are using the unstable
>>> distribution that some required packages have not yet been created
>>> or been moved out of Incoming.
>>> The following information may help to resolve the situation:
>>>
>>> The following packages have unmet dependencies:
>>>  koha-common : Depends: libnet-oauth2-authorizationserver-perl but it is
>>> not going to be installed
>>> E: Unable to correct problems, you have held broken packages.
>>> root@Pine:~#
>>>
>>>
>>> current server:
>>>
>>> Server information
>>> Koha version: 17.05.05.000
>>> OS version ('uname -a'): Linux Pine 3.16.0-4-686-pae #1 SMP Debian
>>> 3.16.43-2+deb8u5 (2017-09-19) i686
>>> Perl interpreter: /usr/bin/perl
>>> Perl version: 5.020002
>>> Perl @INC: /usr/share/koha/lib
>>> /etc/perl
>>> /usr/local/lib/i386-linux-gnu/perl/5.20.2
>>> /usr/local/share/perl/5.20.2
>>> /usr/lib/i386-linux-gnu/perl5/5.20
>>> /usr/share/perl5
>>> /usr/lib/i386-linux-gnu/perl/5.20
>>> /usr/share/perl/5.20
>>> /usr/local/lib/site_perl
>>> .
>>> MySQL version: mysql Ver 14.14 Distrib 5.5.60, for debian-linux-gnu
>>> (i686)
>>> using readline 6.3
>>> Apache version: Server version: Apache/2.4.10 (Debian)
>>> Memcached: Servers: undefined | Namespace: koha | Status: unknown |
>>> Config
>>> read from: Nowhere Note that the right place to define the memcached
>>> config
>>> is in your $KOHA_CONF file. Currently you do not have a valid memcached
>>> configuration defined. | Effective caching method: Cache::Memory
>>> Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
>>> software, covered by the GNU General Public License, and you are welcome
>>> to
>>> change it and/or distribute copies of it under certain conditions. SHA1
>>> ID:
>>> c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU
>>>
>>>
>>>
>>> My Googling skills have failed me and I couldn't find the "dummies"
>>> version
>>> of how to fix this ?
>>> Am I missing a repository ? If so ...what is the correct command to add
>>> it
>>> ?/
>>>
>>> Thank you
>>>
>>> -S
>>> ___
>>> Koha mailing list  http://koha-community.org
>>> Koha@lists.katipo.co.nz
>>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>>
>> --
>> Tomás Cohen Arazi
>> Theke Solutions (https://theke.io )
>> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
>> GPG: B2F3C15F
>>
>
> --
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade issues

[Scott Owen]

deb http://debian.koha-community.org/koha stable main

On Fri, Jun 15, 2018 at 9:55 AM, Tomas Cohen Arazi 
wrote:

> Can you share your /etc/apt/sources.list.d/koha.list config?
>
> El vie., 15 jun. 2018 a las 10:39, Scott Owen ()
> escribió:
>
>> Hi all,
>>
>> I'm trying to upgrade my Koha version...but got stopped at the following:
>>
>>
>> root@Pine:~# sudo apt-get install koha-common
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> The following packages have unmet dependencies:
>>  koha-common : Depends: libnet-oauth2-authorizationserver-perl but it is
>> not going to be installed
>> E: Unable to correct problems, you have held broken packages.
>> root@Pine:~#
>>
>>
>> current server:
>>
>> Server information
>> Koha version: 17.05.05.000
>> OS version ('uname -a'): Linux Pine 3.16.0-4-686-pae #1 SMP Debian
>> 3.16.43-2+deb8u5 (2017-09-19) i686
>> Perl interpreter: /usr/bin/perl
>> Perl version: 5.020002
>> Perl @INC: /usr/share/koha/lib
>> /etc/perl
>> /usr/local/lib/i386-linux-gnu/perl/5.20.2
>> /usr/local/share/perl/5.20.2
>> /usr/lib/i386-linux-gnu/perl5/5.20
>> /usr/share/perl5
>> /usr/lib/i386-linux-gnu/perl/5.20
>> /usr/share/perl/5.20
>> /usr/local/lib/site_perl
>> .
>> MySQL version: mysql Ver 14.14 Distrib 5.5.60, for debian-linux-gnu (i686)
>> using readline 6.3
>> Apache version: Server version: Apache/2.4.10 (Debian)
>> Memcached: Servers: undefined | Namespace: koha | Status: unknown | Config
>> read from: Nowhere Note that the right place to define the memcached
>> config
>> is in your $KOHA_CONF file. Currently you do not have a valid memcached
>> configuration defined. | Effective caching method: Cache::Memory
>> Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
>> software, covered by the GNU General Public License, and you are welcome
>> to
>> change it and/or distribute copies of it under certain conditions. SHA1
>> ID:
>> c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU
>>
>>
>>
>> My Googling skills have failed me and I couldn't find the "dummies"
>> version
>> of how to fix this ?
>> Am I missing a repository ? If so ...what is the correct command to add it
>> ?/
>>
>> Thank you
>>
>> -S
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io )
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade issues

[Tomas Cohen Arazi]

Can you share your /etc/apt/sources.list.d/koha.list config?

El vie., 15 jun. 2018 a las 10:39, Scott Owen () escribió:

> Hi all,
>
> I'm trying to upgrade my Koha version...but got stopped at the following:
>
>
> root@Pine:~# sudo apt-get install koha-common
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  koha-common : Depends: libnet-oauth2-authorizationserver-perl but it is
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> root@Pine:~#
>
>
> current server:
>
> Server information
> Koha version: 17.05.05.000
> OS version ('uname -a'): Linux Pine 3.16.0-4-686-pae #1 SMP Debian
> 3.16.43-2+deb8u5 (2017-09-19) i686
> Perl interpreter: /usr/bin/perl
> Perl version: 5.020002
> Perl @INC: /usr/share/koha/lib
> /etc/perl
> /usr/local/lib/i386-linux-gnu/perl/5.20.2
> /usr/local/share/perl/5.20.2
> /usr/lib/i386-linux-gnu/perl5/5.20
> /usr/share/perl5
> /usr/lib/i386-linux-gnu/perl/5.20
> /usr/share/perl/5.20
> /usr/local/lib/site_perl
> .
> MySQL version: mysql Ver 14.14 Distrib 5.5.60, for debian-linux-gnu (i686)
> using readline 6.3
> Apache version: Server version: Apache/2.4.10 (Debian)
> Memcached: Servers: undefined | Namespace: koha | Status: unknown | Config
> read from: Nowhere Note that the right place to define the memcached config
> is in your $KOHA_CONF file. Currently you do not have a valid memcached
> configuration defined. | Effective caching method: Cache::Memory
> Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
> software, covered by the GNU General Public License, and you are welcome to
> change it and/or distribute copies of it under certain conditions. SHA1 ID:
> c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU
>
>
>
> My Googling skills have failed me and I couldn't find the "dummies" version
> of how to fix this ?
> Am I missing a repository ? If so ...what is the correct command to add it
> ?/
>
> Thank you
>
> -S
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade problem Debian Packages

[clint.deckard]

OK, a restart of memcached did the trick.
Should have thought of that earlier

Clint.

clint.deckard wrote:

Thanks for the reply Liz,
Yes the instance did exist with koha-create --create-db, I used 
koha-remove then koha-restore. The instances are the same name and it is 
not 'instance' :)


The odd thing is that I migrated a number of instances with the same 
process two weeks ago without issue, but the two I tried today have the 
same result.


Appreciatively,
Clint.

Liz Rea wrote:


On 15/01/18 11:55, clint.deckard wrote:

Following an upgrade form 16.05 to 17.11 using the packages (and
koha-restore) on Debian Jessie I get the following error when trying
to access the staff or opac interface;
"DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
Access denied for user 'koha_instance'@'localhost' (using password:
YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1490. at
/usr/share/koha/lib/Koha/Database.pm line 100"

I did notice the error during koha-restore 'DROP USER koha_instance
failed' (approx).

I'd appreciate some help.

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

Hi Clint,

Did the instance koha_instance exist before you tried to restore the
database? i.e. did you koha-create instance before or after you restored
the database?

Is the instance name the same between your dumped database and the new
instance? If not, they probably should be. If you can't do that for some
reason, you'll need to unzip and edit the database dump to include the
new db name, it'll look something like:

--
-- Current Database: `koha_instance`
--

CREATE DATABASE /*!32312 IF NOT EXISTS*/ `koha_instance` /*!40100
DEFAULT CHARACTER SET latin1 */;

USE `koha_instance`;

if "instance" there doesn't match the name of your new db/instance,
you'll need to edit the dump to change it to match up, if that makes 
sense.


I'm making a grand assumption that you know that most Koha instances
aren't named instance, they can be named whatever you want and that
there's nothing magic about "instance" as a name when you've done
koha-create, or koha_instance as the database name. All that needs to
happen is that the koha-create  and koha_ should
match up. Then everything should work. And that the  should
exist before you try to import the database.

If koha-restore doesn't work after you've unzipped and edited the dump
file, you can do (I'm assuming you'll have only one dump file in the
current directory - if you have more than one specify the full filename!)

cat instance-*.sql | sudo koha-mysql instance

and that will import the edited database into the instance's database.

Cheers,
Liz






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

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

Re: [Koha] Upgrade problem Debian Packages

[clint.deckard]

Thanks for the reply Liz,
Yes the instance did exist with koha-create --create-db, I used 
koha-remove then koha-restore. The instances are the same name and it is 
not 'instance' :)


The odd thing is that I migrated a number of instances with the same 
process two weeks ago without issue, but the two I tried today have the 
same result.


Appreciatively,
Clint.

Liz Rea wrote:


On 15/01/18 11:55, clint.deckard wrote:

Following an upgrade form 16.05 to 17.11 using the packages (and
koha-restore) on Debian Jessie I get the following error when trying
to access the staff or opac interface;
"DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
Access denied for user 'koha_instance'@'localhost' (using password:
YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1490. at
/usr/share/koha/lib/Koha/Database.pm line 100"

I did notice the error during koha-restore 'DROP USER koha_instance
failed' (approx).

I'd appreciate some help.

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

Hi Clint,

Did the instance koha_instance exist before you tried to restore the
database? i.e. did you koha-create instance before or after you restored
the database?

Is the instance name the same between your dumped database and the new
instance? If not, they probably should be. If you can't do that for some
reason, you'll need to unzip and edit the database dump to include the
new db name, it'll look something like:

--
-- Current Database: `koha_instance`
--

CREATE DATABASE /*!32312 IF NOT EXISTS*/ `koha_instance` /*!40100
DEFAULT CHARACTER SET latin1 */;

USE `koha_instance`;

if "instance" there doesn't match the name of your new db/instance,
you'll need to edit the dump to change it to match up, if that makes sense.

I'm making a grand assumption that you know that most Koha instances
aren't named instance, they can be named whatever you want and that
there's nothing magic about "instance" as a name when you've done
koha-create, or koha_instance as the database name. All that needs to
happen is that the koha-create  and koha_ should
match up. Then everything should work. And that the  should
exist before you try to import the database.

If koha-restore doesn't work after you've unzipped and edited the dump
file, you can do (I'm assuming you'll have only one dump file in the
current directory - if you have more than one specify the full filename!)

cat instance-*.sql | sudo koha-mysql instance

and that will import the edited database into the instance's database.

Cheers,
Liz






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

Re: [Koha] Upgrade problem Debian Packages

[Liz Rea]

On 15/01/18 11:55, clint.deckard wrote:
> Following an upgrade form 16.05 to 17.11 using the packages (and
> koha-restore) on Debian Jessie I get the following error when trying
> to access the staff or opac interface;
> "DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
> Access denied for user 'koha_instance'@'localhost' (using password:
> YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1490. at
> /usr/share/koha/lib/Koha/Database.pm line 100"
>
> I did notice the error during koha-restore 'DROP USER koha_instance
> failed' (approx).
>
> I'd appreciate some help.
>
> Clint.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
Hi Clint,

Did the instance koha_instance exist before you tried to restore the
database? i.e. did you koha-create instance before or after you restored
the database?

Is the instance name the same between your dumped database and the new
instance? If not, they probably should be. If you can't do that for some
reason, you'll need to unzip and edit the database dump to include the
new db name, it'll look something like:

--
-- Current Database: `koha_instance`
--

CREATE DATABASE /*!32312 IF NOT EXISTS*/ `koha_instance` /*!40100
DEFAULT CHARACTER SET latin1 */;

USE `koha_instance`;

if "instance" there doesn't match the name of your new db/instance,
you'll need to edit the dump to change it to match up, if that makes sense.

I'm making a grand assumption that you know that most Koha instances
aren't named instance, they can be named whatever you want and that
there's nothing magic about "instance" as a name when you've done
koha-create, or koha_instance as the database name. All that needs to
happen is that the koha-create  and koha_ should
match up. Then everything should work. And that the  should
exist before you try to import the database.

If koha-restore doesn't work after you've unzipped and edited the dump
file, you can do (I'm assuming you'll have only one dump file in the
current directory - if you have more than one specify the full filename!)

cat instance-*.sql | sudo koha-mysql instance

and that will import the edited database into the instance's database.

Cheers,
Liz





-- 
--
Liz Rea
Catalyst.Net Limited
Level 6, Catalyst House, 
150 Willis Street, Wellington.
P.O Box 11053, Manners Street, 
Wellington 6142
04 803 2265

GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7


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

Re: [Koha] Upgrade Koha 3.12 to 17.05

[Bob Birchall]

On 12/07/17 21:17, Mesfin Teshome wrote:

Dear all,Can I upgraded Koha 3.12 directly to Koha 17.05? I am currently 
running Koha 3.12 on Ubuntu 14.04. I will really appreciate your help and 
feedback on this. Thank you.Regards,Mesfin


You'll need to be very careful.

First, current versions of Koha won't run on Ubuntu 14.04, so you need 
to upgrade Ubuntu first.  Next, its a big upgrade, through 7 or 8 major 
release versions of Koha, so there is inherent risk. Before you do 
anything, take a backup.


The recommended way to install Koha is from Debian packages. See the 
Koha wiki for info - there's a page for Ubuntu. That was not the case 
back at 3.12 iirc, so that's another change you are navigating.


You need to find a way of creating your new installation without 
destroying your old one.  Otherwise you could get stuck not being able 
to go forward and not being able to go back.  Can you use a different 
device?  If so, install Ubuntu, then install Koha 16.11 or 17.05 from 
Debian packages, then install your saved Koha 3.12 database. Log in to 
the staff client and you'll get the web installer, which will attempt to 
upgrade your database to the current version.


The alternative is to do a conversion.  Export the data you need from 
Koha 3.12 and import it into a new Koha 16.11 or 17.05.


Good luck.  Its much easier to keep your Koha version up to date.

Bob Birchall
Calyx




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

Re: [Koha] Upgrade to latest version not working

[Hugo Agud]

Hi

The Koha release was 2 days ago, but you should wait until the packages are
release, so.. .a litle more of patient ;)

2016-11-24 10:54 GMT+01:00 anjoze :

> Hi all,
> I'm trying to upgrade from version 16.05.05 to latest.
> 2 days ago was released version 16.11.
> I'm using Ubuntu 16.04LTS with Debian repositories:
> /deb http://debian.koha-community.org/koha stable main'/
>
> When try to upgrade koha I get this message:
> I koha-common is already the newest version (16.05.05.01).
>
> Thanks for any help
>
>
>
> -
> Koha version:   16.05.05
>- -
> José Anjos
> --
> View this message in context: http://koha.1045719.n5.nabble.
> com/Upgrade-to-latest-version-not-working-tp5911883.html
> Sent from the Koha-general mailing list archive at Nabble.com.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 

*Hugo Agud - Orex Digital *

*www.orex.es *


[image: www.orex.es/koha] 
   [image: www.orex.es/vufind] 



Director

Calle Sant Joaquin,117, 2º-3ª · 08922 Santa Coloma de Gramanet - Tel: 933
856 138   ha...@orex.es · http://www.orex.es/



No imprima este mensaje a no ser que sea necesario. Una tonelada de papel
implica la tala de 15 árboles y el consumo de 250.000 litros de agua.



Aviso de confidencialidad
Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO
RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni
está autorizado a recibirlo por el remitente), no está autorizado a copiar,
reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje
por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from 3.18 to 3.20.07.000 - Now getting Loading .. you may continue scanning in Circulation Checkout

[Tajoli Zeno]

Hi,


Il 14/01/2016 09:48, Admire Mutsikiwa ha scritto:


I have upgrade my Koha system running on Debian 8.2 from Koha 3.18 to
3.20.07 . Now which checking out a book it is  not displaying the table with
the checkout details such as the due date. Instead, it is displaying the
message

"Loading  .. you may continue scanning" . Any help?


this is a know bug, bug 15431:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15431

You have two option:
1)Wait until next 3.20.x release (next week as I know)

2)Try to fix it with those instructions [from Frédéric DEMIANS]:

- Access your Koha server with shell.

- Locate the file 'checkouts' in your local Koha installation. It is in 
'svc'

  subdirectory of the Koha home directory.

- Change your working directory to the directory containing 'checkouts'.

- Run this command:

  wget -O checkouts http://tinyurl.com/zg6ukte

  It retrieves a valid 'checkouts' program.


Bye
Zeno Tajoli

--
Zeno Tajoli
/Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche
Email: z.taj...@cineca.it Fax: 051/6132198
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from Koha version 2.5 to 3.x

[Indranil Das Gupta]

Hi Damien,

On Thu, Nov 19, 2015 at 6:47 AM, Indranil Das Gupta  wrote:
> Hi Damien,
>
> On Thu, Nov 19, 2015 at 6:30 AM, damienm  
> wrote:
>> Hi,
>>
>> I'm  new to Koha and have inherited a very old koha install. I'm wanting to
>> move the instance to a new VM and thought it may be a good opportunity to
>> upgrade too. Can anyone please assist in the recommend steps to do so?

Couple of points:

The starting point would this http://wiki.koha-community.org/wiki/Upgrading_2.2

Then to ensure that 952 is moved to items table

And a close watch at the updatedatabase.pl output. A few errors can be
ignored, but some would needed to addressed.

and of course a zebra reindex once all that is over.

basically that is pretty much the deal.

cheers,
-idg
>>
>> Thank you in advance..
>>
>> Damien
>>
>>
>>
>>
>> --
>> View this message in context: 
>> http://koha.1045719.n5.nabble.com/Upgrade-from-Koha-version-2-5-to-3-x-tp5862137.html
>> Sent from the Koha-general mailing list archive at Nabble.com.
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
>
> --
> Indranil Das Gupta
>
> Phone : +91-98300-20971
> Blog: http://indradg.randomink.org/blog
> IRC  : indradg on irc://irc.freenode.net
> Twitter : indradg
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
> Please exchange editable Office documents only in ODF Format. No other
> format is acceptable. Support Open Standards.
>
> For a free editor supporting ODF, please visit LibreOffice -
> http://www.documentfoundation.org



-- 
Indranil Das Gupta

Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC  : indradg on irc://irc.freenode.net
Twitter : indradg

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
Please exchange editable Office documents only in ODF Format. No other
format is acceptable. Support Open Standards.

For a free editor supporting ODF, please visit LibreOffice -
http://www.documentfoundation.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from Koha version 2.5 to 3.x

[Mark Tompsett]

Greetings,

Indranil's suggested process direction seems good.

Though, sometimes an upgrade is an opportunity to lose the junk.
However, perhaps you may wish to take this opportunity to do a fresh 
install, and import cleaned MARC records into the fresh install? I would 
also take note of any other settings which might be useful (custom reports, 
branches, system preference settings, etc.). There is, after all, multiple 
ways to accomplish the same thing. :)


GPML,
Mark Tompsett 


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

Re: [Koha] Upgrade from Koha version 2.5 to 3.x

[Indranil Das Gupta]

Hi Damien,

On Thu, Nov 19, 2015 at 6:30 AM, damienm  wrote:
> Hi,
>
> I'm  new to Koha and have inherited a very old koha install. I'm wanting to
> move the instance to a new VM and thought it may be a good opportunity to
> upgrade too. Can anyone please assist in the recommend steps to do so?
>
> Thank you in advance..
>
> Damien
>
>
>
>
> --
> View this message in context: 
> http://koha.1045719.n5.nabble.com/Upgrade-from-Koha-version-2-5-to-3-x-tp5862137.html
> Sent from the Koha-general mailing list archive at Nabble.com.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha



-- 
Indranil Das Gupta

Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC  : indradg on irc://irc.freenode.net
Twitter : indradg

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
Please exchange editable Office documents only in ODF Format. No other
format is acceptable. Support Open Standards.

For a free editor supporting ODF, please visit LibreOffice -
http://www.documentfoundation.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from Koha version 2.5 to 3.x

[Damien Mannix]

Thank you - clean install sounds like a very good option. Is there an  easy way 
to export the data I need or is it more the case copying the database tables 
from old instance to the new?

Best Regards 

Damien Mannix 
Senior Systems Administrator

Email Reference  |  M02...E 
AMOG Pty Ltd 
19 Business Park Drive, Notting Hill Vic 3168, Australia

T +61 3 9542 3700  |  F  +61 3 9542 3790  |  M  +61 423 717 566 
E mailto:damien.mannix@amog.consulting
W http://www.amog.consulting/

Australia  |  United States  |  Colombia  |  United Kingdom  |  Malaysia



This e-mail is intended only for the addressee or addressees named above and 
associated project team members, as dictated by project requirements, and may 
contain confidential information. If you are not the intended recipient, please 
let us know immediately by return e-mail and then delete this e-mail, without 
disclosing or copying the contents. The content of emails to and from AMOG 
Consulting is monitored for corporate governance purposes. Emails addressed to 
individuals within AMOG may be copied to other AMOG staff as dictated by 
project requirements. AMOG does not accept liability for any errors or 
omissions in the content of this message which may arise as a result of the 
email transmission. We recommend that you confirm correct transmission by 
reference to the original in hard copy form or other means before relying on 
information contained herein for design, construction or operational purposes



On 19 November 2015 at 12:46:55 pm, Mark Tompsett (mtomp...@hotmail.com) wrote:

Greetings,  

Indranil's suggested process direction seems good.  

Though, sometimes an upgrade is an opportunity to lose the junk.  
However, perhaps you may wish to take this opportunity to do a fresh  
install, and import cleaned MARC records into the fresh install? I would  
also take note of any other settings which might be useful (custom reports,  
branches, system preference settings, etc.). There is, after all, multiple  
ways to accomplish the same thing. :)  

GPML,  
Mark Tompsett  

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

Re: [Koha] Upgrade from Koha version 2.5 to 3.x

[Indranil Das Gupta]

On Thu, Nov 19, 2015 at 7:16 AM, Mark Tompsett  wrote:
> Greetings,
>
> Indranil's suggested process direction seems good.
>
> Though, sometimes an upgrade is an opportunity to lose the junk.
> However, perhaps you may wish to take this opportunity to do a fresh
> install, and import cleaned MARC records into the fresh install?

I agree. But you may need to hand-code a bit of the exporter code.
After all in 2.2.x days, the MARC record exporter IIRC didn't export
items.

cheers,

-- 
Indranil Das Gupta

Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC  : indradg on irc://irc.freenode.net
Twitter : indradg

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
Please exchange editable Office documents only in ODF Format. No other
format is acceptable. Support Open Standards.

For a free editor supporting ODF, please visit LibreOffice -
http://www.documentfoundation.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade problem from 3.8.9 to 3.20.2

[vinod mishra]

Thanks Dear Jonathan,

So may i know what exactly to do step by step to overcome the situation as
i am trying nut due to my technical limitations i could not able to do.

Thanking You.

On Tue, Sep 1, 2015 at 2:12 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi Vinod,
>
> As it said in the error, you already had a primary key defined on the
> table.
> old_reserves shouldn't have a primary key on old_reserves before
> 3.09.00.025.
>
> Note that there was a bug in this update database entry, have a look
> at bug 10185. But it exists in 3.20.*
>
> Regards,
> Jonathan
>
> 2015-08-29 14:26 GMT+01:00 vinod mishra :
> > Dear All,
> >
> > When i am trying to restore the database of Koha 3.8.9 to on 3.20.2 it
> > gives following error after running* koha-upgrade-schema library*
> command.
> >
> >
> > Upgrade to 3.09.00.023 done (Add system preference SearchEngine )
> > Upgrade to 3.09.00.024 done (Add system preference
> IntranetSlipPrinterJS))
> > DBD::mysql::db do failed: Multiple primary key defined at
> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> > line 5549.
> > DBD::mysql::db do failed: Column count doesn't match value count at row 1
> > at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/
> updatedatabase.pl
> > line 5550.
> > DBD::mysql::db do failed: Incorrect table definition; there can be only
> one
> > auto column and it must be defined as a key at
> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> > line 5569.
> > DBD::mysql::db do failed: Column count doesn't match value count at row 1
> > at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/
> updatedatabase.pl
> > line 5570.
> > Failed to add reserve_id to reserves tables, please refresh the page to
> try
> > again. at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/
> > updatedatabase.pl line 5586.
> >
> > Any solution please? if its a bug than i will file on bugzilla?
> >
> > --
> >
> >
> >
> >
> > *With Regards,Vinod Kumar Mishra,Assistant Librarian,Biju Patnaik Central
> > Library (BPCL),*
> >
> > *NIT Rourkela,*
> >
> > *Sundergadh-769008,*
> >
> > *Odisha,*
> >
> > *India.*
> >
> > *Mob:91+9439420860*
> > *Website: http://mishravk.com/ *
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 




*With Regards,Vinod Kumar Mishra,Assistant Librarian,Biju Patnaik Central
Library (BPCL),*

*NIT Rourkela,*

*Sundergadh-769008,*

*Odisha,*

*India.*

*Mob:91+9439420860*
*Website: http://mishravk.com/ *
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade problem from 3.8.9 to 3.20.2

[Jonathan Druart]

Hi Vinod,

As it said in the error, you already had a primary key defined on the table.
old_reserves shouldn't have a primary key on old_reserves before 3.09.00.025.

Note that there was a bug in this update database entry, have a look
at bug 10185. But it exists in 3.20.*

Regards,
Jonathan

2015-08-29 14:26 GMT+01:00 vinod mishra :
> Dear All,
>
> When i am trying to restore the database of Koha 3.8.9 to on 3.20.2 it
> gives following error after running* koha-upgrade-schema library* command.
>
>
> Upgrade to 3.09.00.023 done (Add system preference SearchEngine )
> Upgrade to 3.09.00.024 done (Add system preference IntranetSlipPrinterJS))
> DBD::mysql::db do failed: Multiple primary key defined at
> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> line 5549.
> DBD::mysql::db do failed: Column count doesn't match value count at row 1
> at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> line 5550.
> DBD::mysql::db do failed: Incorrect table definition; there can be only one
> auto column and it must be defined as a key at
> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> line 5569.
> DBD::mysql::db do failed: Column count doesn't match value count at row 1
> at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> line 5570.
> Failed to add reserve_id to reserves tables, please refresh the page to try
> again. at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/
> updatedatabase.pl line 5586.
>
> Any solution please? if its a bug than i will file on bugzilla?
>
> --
>
>
>
>
> *With Regards,Vinod Kumar Mishra,Assistant Librarian,Biju Patnaik Central
> Library (BPCL),*
>
> *NIT Rourkela,*
>
> *Sundergadh-769008,*
>
> *Odisha,*
>
> *India.*
>
> *Mob:91+9439420860*
> *Website: http://mishravk.com/ *
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade problem from 3.8.9 to 3.20.2

[Jonathan Druart]

Could you have a look at the DB backup you did before the update and
confirm there is a primary key on the reserve table?

2015-09-01 11:42 GMT+01:00 vinod mishra :
> Thanks Dear Jonathan,
>
> So may i know what exactly to do step by step to overcome the situation as i
> am trying nut due to my technical limitations i could not able to do.
>
> Thanking You.
>
> On Tue, Sep 1, 2015 at 2:12 PM, Jonathan Druart
>  wrote:
>>
>> Hi Vinod,
>>
>> As it said in the error, you already had a primary key defined on the
>> table.
>> old_reserves shouldn't have a primary key on old_reserves before
>> 3.09.00.025.
>>
>> Note that there was a bug in this update database entry, have a look
>> at bug 10185. But it exists in 3.20.*
>>
>> Regards,
>> Jonathan
>>
>> 2015-08-29 14:26 GMT+01:00 vinod mishra :
>> > Dear All,
>> >
>> > When i am trying to restore the database of Koha 3.8.9 to on 3.20.2 it
>> > gives following error after running* koha-upgrade-schema library*
>> > command.
>> >
>> >
>> > Upgrade to 3.09.00.023 done (Add system preference SearchEngine )
>> > Upgrade to 3.09.00.024 done (Add system preference
>> > IntranetSlipPrinterJS))
>> > DBD::mysql::db do failed: Multiple primary key defined at
>> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
>> > line 5549.
>> > DBD::mysql::db do failed: Column count doesn't match value count at row
>> > 1
>> > at
>> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
>> > line 5550.
>> > DBD::mysql::db do failed: Incorrect table definition; there can be only
>> > one
>> > auto column and it must be defined as a key at
>> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
>> > line 5569.
>> > DBD::mysql::db do failed: Column count doesn't match value count at row
>> > 1
>> > at
>> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
>> > line 5570.
>> > Failed to add reserve_id to reserves tables, please refresh the page to
>> > try
>> > again. at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/
>> > updatedatabase.pl line 5586.
>> >
>> > Any solution please? if its a bug than i will file on bugzilla?
>> >
>> > --
>> >
>> >
>> >
>> >
>> > *With Regards,Vinod Kumar Mishra,Assistant Librarian,Biju Patnaik
>> > Central
>> > Library (BPCL),*
>> >
>> > *NIT Rourkela,*
>> >
>> > *Sundergadh-769008,*
>> >
>> > *Odisha,*
>> >
>> > *India.*
>> >
>> > *Mob:91+9439420860*
>> > *Website: http://mishravk.com/ *
>> > ___
>> > Koha mailing list  http://koha-community.org
>> > Koha@lists.katipo.co.nz
>> > https://lists.katipo.co.nz/mailman/listinfo/koha
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
>
>
> --
> With Regards,
> Vinod Kumar Mishra,
> Assistant Librarian,
> Biju Patnaik Central Library (BPCL),
> NIT Rourkela,
> Sundergadh-769008,
> Odisha,
> India.
> Mob:91+9439420860
> Website: http://mishravk.com/
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 3.18

[Chris Cormack]

* Lenora Oftedahl (o...@critfc.org) wrote:
 We're upgrading to 3.18, but we are not having any luck with getting the 
 Search to work.  Found the bit about 941$n=1, but we're not sure what that 
 means and where that goes.
  
Hi Lenora

We are going to need some more information, how was your Koha
installed? Packages or tarball, how did you do the upgrade? How are
you reindexing? What version did you come from?

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 3.14 or 3.16?

[Elaine Bradtke]

The latest release of 3.16 (3.16.4)  fixed some  bugs - I would recommend
you install that.

  We are usually fairly early adopters of the new versions, but one of the
bugs in 3.16 was a blocker for us (and has now been fixed). We will be
changing our system over from 3.14.06 to 3.16.4 shortly.  After I test it.

On Tue, Oct 7, 2014 at 7:26 AM, Indranil Das Gupta indr...@gmail.com
wrote:

 Hi Jack,

 On Tue, Oct 7, 2014 at 5:55 AM, vinod kumar vinod.kumar@gmail.com
 wrote:
   upgrade to 3.14

 When 3.18 is released sometime next month, 3.16 will become Koha's
 'old stable' release. If you is going to upgrade now, it makes little
 sense to go for a version that is slated to go out of active
 development / bugfix support. There is quite a bit of change under the
 hood, so closer you are to the latest stables sources better it is.

  On Tue, Oct 7, 2014 at 7:32 AM, jmorash jmor...@pacbell.net wrote:
 
  We are currently running version 3.12. Would it be recommended or
  advisable to upgrade to 3.14 or 3.16?

 3.16

  What are the differences?

 Refer to the release notes of 3.14 and 3.16 referenced in the links below:

 (1) http://koha-community.org/koha-3-14-0-released/

 (2) http://koha-community.org/koha-3-16-0-released/

 cheers
 -indranil

 Phone : +91-98300-20971
 Blog: http://indradg.randomink.org/blog
 IRC  : indradg on irc://irc.freenode.net
 Twitter : indradg

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
 Please exchange editable Office documents only in ODF Format. No other
 format is acceptable. Support Open Standards.

 For a free editor supporting ODF, please visit LibreOffice -
 http://www.documentfoundation.org
 ___
 Koha mailing list  http://koha-community.org
 Koha@lists.katipo.co.nz
 http://lists.katipo.co.nz/mailman/listinfo/koha




-- 
Elaine Bradtke
Data Wrangler
VWML
English Folk Dance and Song Society | http://www.efdss.org
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
---
Writing about music is like dancing about architecture
--Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 3.14 or 3.16?

[Indranil Das Gupta]

Hi Jack,

On Tue, Oct 7, 2014 at 5:55 AM, vinod kumar vinod.kumar@gmail.com wrote:
  upgrade to 3.14

When 3.18 is released sometime next month, 3.16 will become Koha's
'old stable' release. If you is going to upgrade now, it makes little
sense to go for a version that is slated to go out of active
development / bugfix support. There is quite a bit of change under the
hood, so closer you are to the latest stables sources better it is.

 On Tue, Oct 7, 2014 at 7:32 AM, jmorash jmor...@pacbell.net wrote:

 We are currently running version 3.12. Would it be recommended or
 advisable to upgrade to 3.14 or 3.16?

3.16

 What are the differences?

Refer to the release notes of 3.14 and 3.16 referenced in the links below:

(1) http://koha-community.org/koha-3-14-0-released/

(2) http://koha-community.org/koha-3-16-0-released/

cheers
-indranil

Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC  : indradg on irc://irc.freenode.net
Twitter : indradg

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
Please exchange editable Office documents only in ODF Format. No other
format is acceptable. Support Open Standards.

For a free editor supporting ODF, please visit LibreOffice -
http://www.documentfoundation.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade to 3.14 or 3.16?

[vinod kumar]

 upgrade to 3.14

On Tue, Oct 7, 2014 at 7:32 AM, jmorash jmor...@pacbell.net wrote:

 We are currently running version 3.12. Would it be recommended or
 advisable to upgrade to 3.14 or 3.16?
 What are the differences?

 Thanks  Jack

 Sent via the Samsung GALAXY S® 5, an ATT 4G LTE smartphone
 ___
 Koha mailing list  http://koha-community.org
 Koha@lists.katipo.co.nz
 http://lists.katipo.co.nz/mailman/listinfo/koha

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

Re: [Koha] Upgrade from source installation using repository

[Magnus Enger]

Hi!

The following page on the wiki tries to explain how to migrate from a
non-packages install to a packages install:
http://wiki.koha-community.org/wiki/Moving_an_installation_from_a_regular_install_to_the_Debian_packages

I am not sure how many people habe used that page yet, so there might be
things that need to be improved. Ask here or on IRC if toy run into
problems!

Best regards,
Magnus Enger

Den fredag 6. juni 2014 skrev Mesfin Teshome mesfina...@yahoo.com
følgende:

 Dear all,
How do I upgrade from source installation using Koha repository or is
 my option to upgrade using tar file only? My installation is Koha 3.12
 which was installed using the tar file.

 Regards,
 Mesfin
 ___
 Koha mailing list  http://koha-community.org
 Koha@lists.katipo.co.nz
 http://lists.katipo.co.nz/mailman/listinfo/koha

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

Re: [Koha] Upgrade from Koha 3.04

[Indranil Das Gupta]

Hi Greg,

On Mon, Jun 9, 2014 at 8:52 PM, Greg Ashe g...@glenstal.org wrote:

snipped
 Is it possible to transfer the Koha database from old machine to the new
 machine in a simple manner (eg dump entire database from old and restore to
 new)?

Yes, have a look here
http://lists.katipo.co.nz/public/koha/2012-June/033114.html.

cheers,

-- 
Indranil Das Gupta

Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC  : indradg on irc://irc.freenode.net
Twitter : indradg

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
Please exchange editable Office documents only in ODF Format. No other
format is acceptable. Support Open Standards.

For a free editor supporting ODF, please visit LibreOffice -
http://www.documentfoundation.orgHiY
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade from source installation using repository

[Mesfin Teshome]

Mark, 
Thank you. I want to use packages but my current installation is from tarball 
which was done since 3.0. I am now on 3.12. How do I switch to package without 
losing my current installation and configuration
Mesfin
Free
Sent from Yahoo Mail on Android

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

Re: [Koha] Upgrade from source installation using repository

[Mark Tompsett]

Greetings,

On Fri, Jun 6, 2014 at 3:56 PM, Mesfin Teshome mesfina...@yahoo.com wrote:

   How do I upgrade from source installation using Koha repository or is
my option to upgrade using tar file only? My installation is Koha 3.12
which was installed using the tar file.


I would recommend trying to move away from a tarball install, if you are 
using a Debian-based OS (Debian, Ubuntu, Mint, etc.)

http://wiki.koha-community.org/wiki/Moving_an_installation_from_a_regular_install_to_the_Debian_packages

Packages really simplify the upgrading process drastically.

GPML,
Mark Tompsett

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

Re: [Koha] Upgrade - 3.06 to 3.14

[Tom Hanstra]

To follow up on this a bit more, some of my problems were from strict 
checking in MySQL (see separate post) but a lot of others fall into 
these categories:


- Tables which already exist
- Columns which already exist
- Unable to write duplicate keys

Some of these might be OK to let ride.  Others I'm not so sure about.  
How can I best tell if the database after upgrade is missing anything?  
Are there integrity checks which can be run or do we just have to 
stumble on problems if/when we are missing functionality?


Thanks,
Tom

On 5/12/14, 12:25 PM, Tom Hanstra wrote:

When upgrading my database between the 3.06.04 version to the 3.14.05
version, I'm getting a lot of database update errors.  How do I best
track down whether these are causing integrity problems with the data?

I can provide a complete list of errors, but maybe I'm missing something
more fundamental.

Thanks,
Tom



--


-
 Tom Hanstra  Systems Administrator
 Hesburgh Libraries of Notre Dame Phone: (574)631-4686
 208 Hesburgh Library Email: hans...@nd.edu
 Notre Dame, IN  46556

 The nights are getting warmer, it won't be long.
 Won't be long 'til summer comes...  Thin Lizzy
-

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

Re: [Koha] Upgrade from 3.10 to 3.14x

[MJ Ray]

Karam Qubsi wrote:
 I take the backup files from (/var/spool/koha/library ) from server A .
 and restore them on server B .
 
 after that I get an error message :
 ERROR 1396 (HY000) at line 1: Operation DROP USER failed for 'koha_library'@
 '%'
 
 [...] and Koha is working, it seems that there is no problem . but I don't 
 know
 what is that error message means ?

That error message has happened to me since a while ago.  I suspect it's
being too cautious, trying to make really sure it removes the old
username and it should check it exists before running DROP USER, but
I've not taken the time to investigate further yet.

Hope that explains,
-- 
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op
http://koha-community.org supporter, web and library systems developer.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire (including development) at http://www.software.coop/
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade koha-3.10.05 to koha-3.12.00 but rebuild_zebra.pl not running

[satish]

The Documentation at
http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb=HEAD
says, (6.1.2 Zebra Indexer),
you run that as koha user.






On Wed, May 22, 2013 at 12:21 PM, Vikas Salunkhe salunkh...@gmail.comwrote:

 Dear all
 i am upgrade koha-3.10.05 to koha-3.12.00 upgrade successfully but when i
 try to  rebuild_zebra.pl and  use following command zebra is not running,
 the following message is comming,  please guide me

 lib@lib:~$ sudo KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/home/koha/lib
 /home/koha/bin/migration_tools/rebuild_zebra.pl -b -w -v

 [sudo] password for lib:
 Warning: You are running this script as the user 'root'.
 If this is intentional you must explicitly specify this using the
 -run-as-root switch
 Please do '/home/koha/bin/migration_tools/rebuild_zebra.pl --help' to see
 usage.

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




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

Re: [Koha] Upgrade koha 3.2 to koha 3.8.9

[Mohamed zalabany]

Dear Muhammed 
i think you need 
to make upgrade from 3.2 to the newest 3.8.9
this link may help you 
http://lists.katipo.co.nz/public/koha/2012-October/034430.html




Mohamed El Zalabany
Integrated library systems consultant
LibroTech
for library systems and information technology
http://www.librotech.net
mh_zalab...@hotmail.com
Mobile: 0111291444



 From: mr_mega...@hotmail.com
 To: koha@lists.katipo.co.nz
 Date: Thu, 7 Feb 2013 13:57:31 +0200
 Subject: [Koha] Upgrade koha 3.2 to koha 3.8.9
 
 
 Hi to all
 I installed koha 3.2 on ubuntu 10.10 from 2 years ago , now we will prepare a 
 new server ubuntu 12.04 server edition to install koha 3.8.9 , how come i 
 transfer my data from old server to new  server .
 any suggetion.
 
 
 MOHAMED MEGAHED 
 Librarian  Technical support  
 Misr International University Library
 Tel : +2 0100 22 97 96 2
 Tel : +2 011 23 502 505
 
 
  
 
 ___
 Koha mailing list  http://koha-community.org
 Koha@lists.katipo.co.nz
 http://lists.katipo.co.nz/mailman/listinfo/koha
  
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade koha 3.2 to koha 3.8.9

[Tomas Cohen Arazi]

Make a dump of your 3.2 database. Do a fresh install on your new
server. Put your dump in the DB you set for your new Koha. Go through
the update process, and youre done.

Regards
To+

On Thu, Feb 7, 2013 at 8:57 AM, Mohamed Megahed mr_mega...@hotmail.com wrote:

 Hi to all
 I installed koha 3.2 on ubuntu 10.10 from 2 years ago , now we will prepare a 
 new server ubuntu 12.04 server edition to install koha 3.8.9 , how come i 
 transfer my data from old server to new  server .
 any suggetion.


 MOHAMED MEGAHED
 Librarian  Technical support
 Misr International University Library
 Tel : +2 0100 22 97 96 2
 Tel : +2 011 23 502 505




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

Re: [Koha] Upgrade koha 3.2 to koha 3.8.9

[Chris Cormack]

On 8 February 2013 04:18, Tomas Cohen Arazi tomasco...@gmail.com wrote:
 Make a dump of your 3.2 database. Do a fresh install on your new
 server. Put your dump in the DB you set for your new Koha. Go through
 the update process, and youre done.

Don't forget to the remove items from marc bit too, from the INSTALL file

Koha 3.4.x or later  no longer stores items in biblio records.
If you are upgrading from an older version ou will need to do the
following two steps, they can take a long time (several hours) to
complete for large databases

 misc/maintenance/remove_items_from_biblioitems.pl --run
 misc/migration_tools/rebuild_zebra.pl -b -r

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

Re: [Koha] upgrade 3.6.1 to 3.8.5 DOM vs GRS1

[Ian Bays]

Hi.
This bug with patch will almost certainly fix the known problem with dom 
indexing:

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8665
My guess is that you have records with the 001 field that are not unique 
(which should work OK).

Cheers.


On 11/10/2012 08:24, Hugo Agud wrote:

Dear all

I write this mail because we wish to share this issue with you and ask you
If you have had similar experiences

We have upgraded a koha 3.6.1 to 3.8.5 with success no error messages, no
where however we have found some strange behaviour in the Zebra index..

If we upgrade koha and configure zebra for using DOM, some records are
missing, although they are in the mysql (we have seen the bugzilla and we
have applied it , and some records appears but we do not rely completly on
this index, we fear that some records are still missing... a search in
3.8.5 and 3.6.1 gives different number of results and we do not know if
this happens becasue of the change of indexing in DOM or because there are
still lmissing records however the subject search it matachs 100% both
servers.

If we upgrade koha and condigure grs1 we get the exact result list in 3.6.1
and 3.8.5 but all the records are empty, with no data...  (no error logs
nowhere), koha 3.8.5 gives 13 ersults... and is list them with no data...
  (we have reindexed them with -x and without -x) we suspect perhaps some
kind of character problem indexing..

Now we're going to maka a fresh install instead of a upgrade and check the
behaviour of zebra results...


Anybody has experienced a similar behaviour? we're going tin make a fresh
install of Koha 3.8.5 and transfer the database and check it in order to
compare both index (the upgraded and fresh install)


Data from the server (perhaps we should upgrade zebra?)
  Koha version: 3.08.05.000 OS version ('uname -a'): Linux ip-10-33-136-12
3.0.0-13-virtual #22-Ubuntu SMP Wed Nov 2 17:10:19 UTC 2011 i686 i686 i386
GNU/Linux Perl interpreter: /usr/bin/perl Perl version: 5.012004 Perl
@INC:/usr/share/koha/lib
/etc/perl
/usr/local/lib/perl/5.12.4
/usr/local/share/perl/5.12.4
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.12
/usr/share/perl/5.12
/usr/local/lib/site_perl
.
  MySQL version: mysql Ver 14.14 Distrib 5.1.63, for debian-linux-gnu (i686)
using readline 6.2 Apache version: Server version: Apache/2.2.20
(Ubuntu)Zebra version:Zebra 2.0.44 (C) 1994-2010, Index Data ApS Zebra
is free software, covered
by the GNU General Public License, and you are welcome to change it and/or
distribute copies of it under certain conditions. SHA1 ID:
419ad759807269fdfa379799a051ed3a551c6541 Using IC




--
Ian Bays
Director of Projects, PTFS Europe Limited
Content Management and Library Solutions
+44 (0) 800 756 6803 (phone)
+44 (0) 7774 995297 (mobile)
+44 (0) 800 756 6384 (fax)
skype: ian.bays
email: ian.b...@ptfs-europe.com

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

Re: [Koha] upgrade 3.6.1 to 3.8.5 DOM vs GRS1

[Hugo Agud]

yes, we have already implemented and missing records appear, the result
list are still not satisfactory, appears results that do not match the
search we are suspicious about dom ;)

We're going to do a fresh install and check again if the same situation
happens again

Thanks for the support!

2012/10/11 Ian Bays ian.b...@ptfs-europe.com

 Hi.
 This bug with patch will almost certainly fix the known problem with dom
 indexing:
 http://bugs.koha-community.**org/bugzilla3/show_bug.cgi?id=**8665http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8665
 My guess is that you have records with the 001 field that are not unique
 (which should work OK).
 Cheers.



 On 11/10/2012 08:24, Hugo Agud wrote:

 Dear all

 I write this mail because we wish to share this issue with you and ask you
 If you have had similar experiences

 We have upgraded a koha 3.6.1 to 3.8.5 with success no error messages, no
 where however we have found some strange behaviour in the Zebra index..

 If we upgrade koha and configure zebra for using DOM, some records are
 missing, although they are in the mysql (we have seen the bugzilla and we
 have applied it , and some records appears but we do not rely completly on
 this index, we fear that some records are still missing... a search in
 3.8.5 and 3.6.1 gives different number of results and we do not know if
 this happens becasue of the change of indexing in DOM or because there are
 still lmissing records however the subject search it matachs 100% both
 servers.

 If we upgrade koha and condigure grs1 we get the exact result list in
 3.6.1
 and 3.8.5 but all the records are empty, with no data...  (no error logs
 nowhere), koha 3.8.5 gives 13 ersults... and is list them with no data...
   (we have reindexed them with -x and without -x) we suspect perhaps some
 kind of character problem indexing..

 Now we're going to maka a fresh install instead of a upgrade and check the
 behaviour of zebra results...


 Anybody has experienced a similar behaviour? we're going tin make a fresh
 install of Koha 3.8.5 and transfer the database and check it in order to
 compare both index (the upgraded and fresh install)


 Data from the server (perhaps we should upgrade zebra?)
   Koha version: 3.08.05.000 OS version ('uname -a'): Linux ip-10-33-136-12
 3.0.0-13-virtual #22-Ubuntu SMP Wed Nov 2 17:10:19 UTC 2011 i686 i686 i386
 GNU/Linux Perl interpreter: /usr/bin/perl Perl version: 5.012004 Perl
 @INC:/usr/share/koha/lib
 /etc/perl
 /usr/local/lib/perl/5.12.4
 /usr/local/share/perl/5.12.4
 /usr/lib/perl5
 /usr/share/perl5
 /usr/lib/perl/5.12
 /usr/share/perl/5.12
 /usr/local/lib/site_perl
 .
   MySQL version: mysql Ver 14.14 Distrib 5.1.63, for debian-linux-gnu
 (i686)
 using readline 6.2 Apache version: Server version: Apache/2.2.20
 (Ubuntu)Zebra version:Zebra 2.0.44 (C) 1994-2010, Index Data ApS Zebra

 is free software, covered
 by the GNU General Public License, and you are welcome to change it and/or
 distribute copies of it under certain conditions. SHA1 ID:
 419ad759807269fdfa379799a051ed**3a551c6541 Using IC



 --
 Ian Bays
 Director of Projects, PTFS Europe Limited
 Content Management and Library Solutions
 +44 (0) 800 756 6803 (phone)
 +44 (0) 7774 995297 (mobile)
 +44 (0) 800 756 6384 (fax)
 skype: ian.bays
 email: ian.b...@ptfs-europe.com

 __**_
 Koha mailing list  http://koha-community.org
 Koha@lists.katipo.co.nz
 http://lists.katipo.co.nz/**mailman/listinfo/kohahttp://lists.katipo.co.nz/mailman/listinfo/koha




-- 

*Hugo Agud - Orex Digital *

*www.orex.es*

*
*

 Director

Avenida Sarriá 29 · 08029 Barcelona http://twitter.com/OrexDigital
:http://orexsl.blogspot.comhugoaguda - Tel: 93 539 40 70 Fax: 93 539
33 30
ha...@orex.es · http://www.orex.es/



No imprima este mensaje a no ser que sea necesario. Una tonelada de papel
implica la tala de 15 árboles y el consumo de 250.000 litros de agua.



Aviso de confidencialidad
Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO
RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni
está autorizado a recibirlo por el remitente), no está autorizado a copiar,
reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje
por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade koha 3.0 to 3.8 installation guide

[Robin Sheat]

Op 27-08-12 03:46, Vimal Kumar V. schreef:
 Please see the following link,
 
 http://kohageek.pbworks.com/w/page/31795398/upgrade

This is removing the remove items from biblios step, needed if you're
coming from 3.2 or earlier.

-- 
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade koha 3.0 to 3.8 installation guide

[Robin Sheat]

Op 27-08-12 11:14, Robin Sheat schreef:
 This is removing the remove items from biblios step, needed if you're
 coming from 3.2 or earlier.

This is _missing_ is what I was trying to say.

-- 
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Upgrade koha 3.0 to 3.8 installation guide

[Mark Tompsett]

Greetings,

As Robin Sheat pointed out, a step or two was missing. This is why we 
strongly recommend reading the INSTALL.{OS} (i.e. INSTALL.debian or 
INSTALL.ubuntu, etc.) files.


--- SNIPPET FROM INSTALL.ubuntu ---
UPGRADE
===
If you are running in another language other than english, please
switch to english before doing the upgrade, the templating system has
changed and the templates will need to be regenerated.
Once you have upgraded, please regenerate your templates in your
chosen languages.

If you are upgrading from a previous installation of Koha 3.x, you can
use the following:

./koha_perl_deps.pl -u -m # to identify new Perl dependencies

Install any missing modules
IMPORTANT: Koha 3.6.x uses Template::Toolkit, this must be installed
before the webinstaller can run

sudo apt-get install libtemplate-perl

perl Makefile.PL --prev-install-log /path/to/koha-install-log
make
make test
sudo make upgrade

Koha 3.4.x or later no longer stores items in biblio records so
if you are upgrading from an older version as part of the
upgrade you will need to do the following two steps, they can take a
long time (several hours) to complete for large databases

misc/maintenance/remove_items_from_biblioitems.pl --run
misc/migration_tools/rebuild_zebra.pl -b -r
--- END SNIPPET ---

I compared this section against the INSTALL.debian, and only find the debian 
had a typo in it.


If you are going to be doing a fresh install of Koha, consider packages in 
the first place:

http://wiki.koha-community.org/wiki/Koha_3.8_on_Debian_Squeeze
I can affirm that the Koha_3.8_on_Debian_Squeeze instructions work for 
Ubuntu 12.04 LTS.


GPML,
Mark Tompsett 


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

Re: [Koha] Upgrade to 3.8 causes phantom search results

[Elaine Bradtke]

Thanks Chris, that seems to have fixed it.  So glad it was a Bank Holiday
in the UK today, or the library director would have been having kittens by
now.
Elaine

On Mon, Aug 27, 2012 at 9:36 PM, Chris Cormack chr...@catalyst.net.nzwrote:

 * Elaine Bradtke (e...@efdss.org) wrote:
  Strange thing happened after we upgraded to 3.8 (from 3.4). We seem to
 have
  ghosts
  Hits that lead nowhere, in both the OPAC and staff interface.
  When a search is performed it lists x number of results.
  Scroll down the list and many of them look normal
  Some however have a result number, and nothing else - no title, no items,
  nothing.  If you mouseover the link it says biblioitemno= [blank]
  If you click on edit record, you get a blank form.
 
  It appears that somehow the number of hits is doubling, and half of these
  are non-existent.  This conclusion is from a very small sample set,
 working
  with a few titles that I know are unique. The ghost appears immediately
  following the real record in the hit list.
  Rebuilt the zebra, and it still does it.
  We didn't notice it at first, because in the staff interface, the ghosts
  come at the end of the hit list, and when I test upgrades I tend to go
 for
  searches that I know will hit a wide swath of the catalogue, so I didn't
  see the problem at the end of the list.
  Oddly, it's more noticeable in the OPAC.
 
  http://catalogue.efdss.org/ if you want to see.
  Try search terms queen and mogul for a small set of hits.
 
  Is there some setting that would cause this? I admit to meddling with
 some
  of the global preferences following the upgrade, but nothing radical.
   Changing them back didn't seem to fix the problem.

 Hi Elaine

 One thing you could try is

 http://koha-community.org/faq/double-ups-search-results-clear-index-start-again/

 Chris

 --
 Chris Cormack
 Catalyst IT Ltd.
 +64 4 803 2238
 PO Box 11-053, Manners St, Wellington 6142, New Zealand




-- 
Elaine Bradtke
Data Wrangler
VWML
English Folk Dance and Song Society | http://www.efdss.org
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
---
Writing about music is like dancing about architecture
--Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha