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

[Mark Alexander]

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

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

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

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

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

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

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

[Alvaro Cornejo]

Hi Isabel,

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

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

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

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

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

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

Hope this helps,

Regards,

Alvaro




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


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

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

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

[Koha] Upgrade OS - Ubuntu 18.04 to 20.04

[Isabel Pineda]

Hi.

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

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

Thank you very much
Isabel Pineda
___

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

Re: [Koha] Update from version 20 to 21 - cannot edit patrons anymore

[Isabel Pineda]

Hi Michael.

I'm sorry. No, there is no warning in "System Information".

Thank you
Isabel

-Mensaje original-
De: Michael Kuhn [mailto:m...@adminkuhn.ch] 
Enviado el: viernes, 25 de junio de 2021 11:20 a.m.
Para: Isabel Pineda ; Koha 
Asunto: Re: [Koha] Update from version 20 to 21 - cannot edit patrons anymore

Hi Isabel

 > It is version 21.05.00.000.

That's from "Server information". I asked for "System information" are there no 
warnings?

 > Someone has just told me that this is a  > bug and will be resolved in 
 > version 21.05.01. This version is not yet  > available on Ubuntu but I hope 
 > that it will be in the next days.

Yes, that's why I asked. maybe it's the same bug that I experienced some days 
ago

* https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144
(Cannot delete any patrons)

In this case it turned out it was just one missing ";" in a file.

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] Update from version 20 to 21 - cannot edit patrons anymore

[Michael Kuhn]

Hi Isabel

> It is version 21.05.00.000.

That's from "Server information". I asked for "System information" are 
there no warnings?


> Someone has just told me that this is a
> bug and will be resolved in version 21.05.01. This version is not yet
> available on Ubuntu but I hope that it will be in the next days.

Yes, that's why I asked. maybe it's the same bug that I experienced some 
days ago


* https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144 
(Cannot delete any patrons)


In this case it turned out it was just one missing ";" in a file.

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] Update from version 20 to 21 - cannot edit patrons anymore

[Isabel Pineda]

Hi Michael. 

It is version 21.05.00.000. Someone has just told me that this is a bug and 
will be resolved in version 21.05.01. This version is not yet available on 
Ubuntu but I hope that it will be in the next days.

Thank you very much
Isabel

-Mensaje original-
De: Koha [mailto:koha-boun...@lists.katipo.co.nz] En nombre de Michael Kuhn
Enviado el: viernes, 25 de junio de 2021 11:10 a.m.
Para: koha@lists.katipo.co.nz
Asunto: Re: [Koha] Update from version 20 to 21 - cannot edit patrons anymore

Hi Isabel

 > I have just updated Koha to version 21.05 and now I am having a  > problem 
 > because I cannot edit patrons anymore. It seems that a  > javascript is 
 > missing?
 >
 > The log file intranet-error.log gives this output:
 > File not found : default/js/locale_data.js at 
 > /usr/share/koha/lib/Koha/Template/Plugin/Asset.pm line 84.: 
/usr/share/koha/intranet/cgi-bin/members/memberentry.pl
 >
 > Does anybody know how to fix this? I am running Koha on Ubuntu 18.04.

What does Koha menu "About Koha > System information" say?

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

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

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

Re: [Koha] Update from version 20 to 21 - cannot edit patrons anymore

[Michael Kuhn]

Hi Isabel

> I have just updated Koha to version 21.05 and now I am having a
> problem because I cannot edit patrons anymore. It seems that a
> javascript is missing?
>
> The log file intranet-error.log gives this output:
> File not found : default/js/locale_data.js at 
/usr/share/koha/lib/Koha/Template/Plugin/Asset.pm line 84.: 
/usr/share/koha/intranet/cgi-bin/members/memberentry.pl

>
> Does anybody know how to fix this? I am running Koha on Ubuntu 18.04.

What does Koha menu "About Koha > System information" say?

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

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

[Koha] Update from version 20 to 21 - cannot edit patrons anymore

[Isabel Pineda]

Hi.

I have just updated Koha to version 21.05 and now I am having a problem because 
I cannot edit patrons anymore. It seems that a javascript is missing?

The log file intranet-error.log gives this output:
File not found : default/js/locale_data.js at 
/usr/share/koha/lib/Koha/Template/Plugin/Asset.pm line 84.: 
/usr/share/koha/intranet/cgi-bin/members/memberentry.pl

Does anybody know how to fix this? I am running Koha on Ubuntu 18.04.

Thank you very much
Isabel Pineda
___

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

Re: [Koha] Upgrade / migration questions

[Scott Owen]

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

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

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

-S








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

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

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

[Koha] Upgrade / migration questions

[Scott Owen]

Hi all,

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

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

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

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

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

 Thank you for any insight / advice.

-S
___

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

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

[Jason Boyer]

Hi Tasha, in yaml using a - like that makes the entry part of a list / array of 
values.

This is easier to see with a yaml -> json example

 analyzer_phrase:

   tokenizer: keyword

   filter:

 - icu_folding

   char_filter:

 - punctuation

Becomes something like this in json:

{ “analyzer_phrases":  { “tokenizer": “keyword” }, “filter”: [“icu_folding”], 
“char_filter”: [“punctuation”] }

So adding additional ‘-‘-prefixed entries below filter or char_filter would add 
additional entries to those arrays. Just having the bare word punctuation below 
char_filter would be a syntax error.

This means that there should be a definition for the punctuation char_filter 
*somewhere*, but possibly not in that file.

Jason

-- 
Jason Boyer
Senior System Administrator
Equinox Open Library Initiative
jbo...@equinoxoli.org
+1 (877) Open-ILS (673-6457)
https://equinoxOLI.org/

> On Jun 24, 2021, at 5:55 PM, Bales (US), Tasha R  
> wrote:
> 
> Follow-up to my problem searching the OPAC for phrases containing punctuation 
> (i.e., Electroactive polymer (EAP) actuators).  This Bywater 
> Solutions article 
> suggests that the problem is a feature of Elasticsearch.
> 
> 
> 
> FYI, we are using Elasticsearch 6.1.1 on its own dedicated server, and I 
> don’t believe we’ve installed the ICU Analysis plug-in (looks like it’s 
> required for Zebra, but I can’t tell if it’s required for Elasticsearch), 
> which could be a factor.  I couldn’t replicate all aspects of my experience 
> in a sandbox, although searches for phrases containing punctuation still 
> failed in an OPAC “Library Catalog” sandbox search.  I concluded that I 
> needed to review our configuration.
> 
> 
> 
> I’ve been reviewing the Koha Wiki and elastic.co documentation, and comparing 
> to our index_config.yaml.
> 
> By chance does anyone know how to interpret the syntax below?  The 
> documentation describes the parameters below, but I don’t see any usage of 
> “-“ before options.  Does the option “- punctuation“ mean “yes, remove 
> punctuation”, or “no, don’t remove punctuation”, or does the phrase refer to 
> some additional configuration file, or perhaps it’s commented out?
> 
> 
> 
>  analyzer_phrase:
> 
>tokenizer: keyword
> 
>filter:
> 
>  - icu_folding
> 
>char_filter:
> 
>  - punctuation
> 
> 
> 
> Thanks for your time and consideration,
> 
> 
> 
> 
> 
> Tasha Bales
> 
> Business Support Team | Information Services
> 
> Enterprise Services | Enterprise Operations, Finance and Sustainability
> 
> 
> 
> 
> 
> -Original Message-
> 
> From: Bales (US), Tasha R
> 
> Sent: Tuesday, June 22, 2021 7:54 AM
> 
> To: 'Jonathan Druart' 
> 
> Cc: Discussion Group Koha 
> 
> Subject: RE: [EXTERNAL] Re: [Koha] Title search works, but Library catalog 
> search fails in OPAC
> 
> 
> 
> Jonathan, thank you!
> 
> 
> 
> It does work without the parentheses.
> 
> 
> 
> I would suspect an encoding problem, but for that the problem only manifests 
> in the OPAC, and not the intranet.
> 
> 
> 
> I came across this issue while testing after migrating from MariaDB to 
> Percona MySQL.  Your reply prompted me to check the encoding of the new 
> database, and it's unfortunately Latin-1.  Since these are parentheses and 
> not diacritics, I’m not sure what my expectations should be, but changing to 
> UTF-8 is a place to start.  Httpd.conf does have UTF-8 set as the default.
> 
> 
> 
> FWIW, my source records were encoded in MARC-8.  I used MarcEdit to convert 
> them to UTF-8, and it appears that Koha automatically converts anyway on 
> import.  When I loaded these records into Koha, I used bulkmarcimport.pl on 
> the command line.
> 
> 
> 
> I'll ask that the default character set of the database be changed, and see 
> if that helps.  Thanks again.  I'm embarrassed that I didn't think to omit 
> the parentheses, or rather was belligerently insisting to myself that they 
> should not have been a problem,
> 
> 
> 
> 
> 
> Tasha Bales
> 
> Business Support Team | Information Services Enterprise Services | Enterprise 
> Operations, Finance and Sustainability
> 
> (480) 509-5415
> 
> https://is.web.boeing.com
> 
> 
> 
> 
> 
> -Original Message-
> 
> From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org]
> 
> Sent: Tuesday, June 22, 2021 12:01 AM
> 
> To: Bales (US), Tasha R 
> 
> Cc: Discussion Group Koha 
> 
> Subject: [EXTERNAL] Re: [Koha] Title search works, but Library catalog search 
> fails in OPAC
> 
> Importance: High
> 
> 
> 
> EXT email: be mindful of links/attachments.
> 
> 
> 
> 
> 
> 
> 
> Hello Tasha,
> 
> 
> 
> I've created 2 records with
> 
>  245$a Electroactive polymer (EAP) actuators as artificial muscles and the 
> following query returns the 2 results.
> 
> /opac-search.pl?idx==Electroactive%20polymer%20%28EAP%29%20actuators_search=1
> 
> 
> 
> Tried on master and 20.11.06.
> 
> 
> 
> Maybe a 

Re: [Koha] 590 local note public and non public notes not displaying properly

[Jonathan Druart]

Hello Elaine,

Yes it's a bug, I've let a comment on bug 27268
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27268#c8

Regards,
Jonathan

Le jeu. 24 juin 2021 à 19:49, Elaine Bradtke  a écrit :
>
> We use a 590 local note for some material.
> There is a subfield x Non Public Note which contains information for the
> staff regarding the content of the work, and a subfield z Public note that
> contains a generic statement governed by an authorized value.
>
> What we see in the normal view in both the staff interface and the OPAC is
> the Non Public note and the code for the authorized value for the public
> note.
> In the OPAC, it displays correctly in labeled MARC. In plain MARC it only
> displays the authorized value code.  See
> https://catalogue.efdss.org/cgi-bin/koha/opac-detail.pl?biblionumber=65305
> for an example.
>
> Non public notes seem to work as expected in the item records.
> This worked before we upgraded to 21.05
>
> Should I file a bug?
> Elaine Bradtke
> VWML 
> English Folk Dance and Song Society 
> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
> Song Society in London, England. If you wish to phone me personally, send
> an e-mail first. I work off site)
> --
> Registered Company No. 297142
> Charity Registered in England and Wales No. 305999
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

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

[Koha] Keyword search in Koha

[Michael Kuhn]

Hi

Lately I stumbled upon some strange behaviour of the keyword search in 
Koha. In our library we are using an unchanged Zebra configuration as 
coming with Koha 20.11.00.


The Koha manual describes the keyword search in the following chapter: 
https://koha-community.org/manual/20.11/en/html/searching.html#basic-searching


1. The manual says: "When a single word is entered, a keyword search is 
performed. You can check this out by typing one word into the form and 
note the number of results located. Then, repeat the search with a minor 
change. In front of the search word, type ‘kw=’ followed by the same 
search term. The results will be identical." I did check this out and 
the result was NOT identical. Why is that so?


The following searches produce a difference of four results:

Search for: biology
* URL: .../search.pl?q=biology
* 5939 results

Search for: kw=biology
* URL: .../search.pl?q=kw%3Dbiology
* 5935 results

The following searches produce a difference of 49 results:

Search for: life
* URL: .../search.pl?q=life
* 837 results

Search for: kw=life
* URL: .../search.pl?q=kw%3Dbiology
* 788 results

2. The manual also says: "When you have more than one word in the search 
box, Koha will still do a keyword search, but a bit differently. Each 
word will be searched on its own, then the Boolean connector ‘and’ will 
narrow your search to those items with all words contained in matching 
records." I did check this out and it does not seem to be true - if I 
just enter two words (biology life) I get 37 more results than when I'm 
using the boolean operator AND. What is the explanation for this?


Search for: biology life
* URL: .../search.pl?q=biology+life
* 521 results

Search for: biology AND life
* URL: .../search.pl?q=biology+AND+life
* 484 results

Search for: kw=biology AND kw=life
* URL: .../search.pl?q=kw%3Dbiology+AND+kw%3Dlife
* 484 results

Especially I'm stunned because the first search does not seem to be 
using the OR operator but still produces considerably more results than 
the searches using the AND operator.


3. Is there maybe some undocumented use of using wildcards going on if 
one is not using a search prefix?


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