[Koha] rebuild_zebra daemon locks memcached?

[Alvaro Cornejo]

Hi

Since our update to 19.11.09 we start having problems with kona. We
initially thought it was apache since without any notice, koha stop
responding.

When doing ps-ef |grep apache we got hundreds of entries even though we
have very low load. Max 3 users at a time. Restarting apache solved the
issue for a while

On the server we only have koha and mod_pagespeed. Boith using the same
instance of memcached. We disabled mod_pagespped and for a while, it looked
like it was the problem, but after a couple of days, the issue returned.

using netstat we found that there were lots of CLOSE_WAIT connections to
port 11211. So  we decided to configure two instances of memcached in two
different ports. One for koha and one for mod_pagespeed.

The issue of CLOSE_WAIT connections is less often now. However they are
almost always related to perl
.
# sudo netstat -tulpan |grep 11211
gives us
tcp1  0 127.0.0.1:54368 127.0.0.1:11211
CLOSE_WAIT  1411/perl

And checking the perl process:
#ps -ef |grep 1411
bibliot+  1411  1407  0 Sep18 ?00:01:44 /usr/bin/perl
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 5

Also, we noticed that, at anytime, memcached port has at least 10-15
connections split between memcached process and starman workers

Is that normal?

mod_pagespeed didn´t have any problem since it is configured to use an
independant memcached instance

Koha 19.11.09
Ubuntu bionic
memcached  1.5.6

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
___

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

Re: [Koha] ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]

[Charles Kelley]

Hello again, all!

In our latest exchange, on 24 Sept 2020 at 09:01, the Koha Discussion
Group circulated:

It looks like my exuberance was premature. I spent much of yesterday
> updating records. Towards the end of the day, I exported the entire
> database -- both bibliographic and item records. Then I rebooted the
> server. While the Koha interface came up, none of the titles I searched was
> found. Instead, I got this error from the either Koha or the Linux box, to
> wit:
>
> **Software error:**
>>
>> Unable to perform your search. Please try again.
>>
>> For help, please send mail to the webmaster ([*no address given*]), giving
>> this message and the date and time of the error.
>
>
>
Mason James wrote:


> $ sudo systemctl enable elasticsearch


This worked! I've rebooted several times, checked my recent saves, and
everything is intact.

Thank you!

Luis Moises Rojas wrote:

Try to set ES as a service
>

Thanks for everything, all! Your advice and suggestions all worked
perfectly. Linux is new to us as system administrators, and we aren't used
to this level of detail.

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

-- Charles.

Charles Kelley, MLS
PSC 704 Box 1029
APO AP 96338

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

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

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

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

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

Re: [Koha] ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]

[Luis Moises Rojas]

It is good to reindex

El mié., 23 de septiembre de 2020 8:43 p. m., Mason James 
escribió:

>
> On 24/09/20 11:45 am, Luis Moises Rojas wrote:
> > Hello,
> > Not you did not lost your work.
> > You have to start ES everytime you reboot your server and reindex again.
> ..
> >>  However, by rebooting ElasticSearch manually, we could search
> again.
> >> Must I reboot ElasticSearch everytime we reboot the server? How does one
> >> get ElasticSearch to come up when the server is rebooted besides through
> >> manual intervention? Surely, there must be an automatic way.
>
> ...just to confirm, an ES reindex is not required after a server reboot
>
>
___

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

Re: [Koha] ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]

[Mason James]

On 24/09/20 11:45 am, Luis Moises Rojas wrote:

Hello,
Not you did not lost your work.
You have to start ES everytime you reboot your server and reindex again.

..

 However, by rebooting ElasticSearch manually, we could search again.
Must I reboot ElasticSearch everytime we reboot the server? How does one
get ElasticSearch to come up when the server is rebooted besides through
manual intervention? Surely, there must be an automatic way.


...just to confirm, an ES reindex is not required after a server reboot

___

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

Re: [Koha] ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]

[Luis Moises Rojas]

Hello,
Not you did not lost your work.
You have to start ES everytime you reboot your server and reindex again.

Try to set ES as a service

Bless

El mié., 23 de septiembre de 2020 6:23 p. m., Charles Kelley <
cmkelley...@gmail.com> escribió:

> Hello, all!
>
> In our latest exchange, on 23 Sept. 2020 at 08:47, I wrote:
>
> Success! After several dozen tests, I'm glad and relieved that
> ElasticSearch
> > is successfully installed and it works smoothly.
> >
>
> It looks like my exuberance was premature. I spent much of yesterday
> updating records. Towards the end of the day, I exported the entire
> database -- both bibliographic and item records. Then I rebooted the
> server. While the Koha interface came up, none of the titles I searched was
> found. Instead, I got this error from the either Koha or the Linux box, to
> wit:
>
> *Software error:*
> >
> > Unable to perform your search. Please try again.
> >
> > For help, please send mail to the webmaster ([*no address given*]),
> > giving this message and the date and time of the error.
> >
>
> I didn't lose my work from yesterday because I had a backup copy of the
> authority and bibliographic files, and I had a backup copy of the previous
> day's installation of Koha. I was prepared to upload the files into the
> previous day's installation if I had to.
>
> However, by rebooting ElasticSearch manually, we could search again.
> Must I reboot ElasticSearch everytime we reboot the server? How does one
> get ElasticSearch to come up when the server is rebooted besides through
> manual intervention? Surely, there must be an automatic way.
>
> Many thanks for everyone's help in this.
>
> --
>
> 気を付けて。 /ki wo tukete/ = Take care.
>
> -- Charles.
>
> Charles Kelley, MLS
> PSC 704 Box 1029
> APO AP 96338
>
> Charles Kelley
> Tsukimino 1-Chome 5-2
> Tsukimino Gaadenia #210
> Yamato-shi, Kanagawa-ken
> 〒242-0002 JAPAN
>
> +1-301-741-7122 [US cell]
> +81-80-4356-2178 [JPN cell]
>
> mnogoja...@aol.com [h]
> cmkelley...@gmail.com [p]
>
> linkedin.com/in/cmkelleymls 
> Meeting Your Information Needs. Virtually.
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

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

Re: [Koha] ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]

[Mason James]

hi Charles

try...

$ sudo systemctl enable elasticsearch



On 24/09/20 10:22 am, Charles Kelley wrote:

Hello, all!

 In our latest exchange, on 23 Sept. 2020 at 08:47, I wrote:

 Success! After several dozen tests, I'm glad and relieved that
ElasticSearch

...

Must I reboot ElasticSearch everytime we reboot the server? How does one
get ElasticSearch to come up when the server is rebooted besides through
manual intervention? Surely, there must be an automatic way.

 Many thanks for everyone's help in this.



___

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

[Koha] ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]

[Charles Kelley]

Hello, all!

In our latest exchange, on 23 Sept. 2020 at 08:47, I wrote:

Success! After several dozen tests, I'm glad and relieved that
ElasticSearch
> is successfully installed and it works smoothly.
>

It looks like my exuberance was premature. I spent much of yesterday
updating records. Towards the end of the day, I exported the entire
database -- both bibliographic and item records. Then I rebooted the
server. While the Koha interface came up, none of the titles I searched was
found. Instead, I got this error from the either Koha or the Linux box, to
wit:

*Software error:*
>
> Unable to perform your search. Please try again.
>
> For help, please send mail to the webmaster ([*no address given*]),
> giving this message and the date and time of the error.
>

I didn't lose my work from yesterday because I had a backup copy of the
authority and bibliographic files, and I had a backup copy of the previous
day's installation of Koha. I was prepared to upload the files into the
previous day's installation if I had to.

However, by rebooting ElasticSearch manually, we could search again.
Must I reboot ElasticSearch everytime we reboot the server? How does one
get ElasticSearch to come up when the server is rebooted besides through
manual intervention? Surely, there must be an automatic way.

Many thanks for everyone's help in this.

-- 

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

-- Charles.

Charles Kelley, MLS
PSC 704 Box 1029
APO AP 96338

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

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

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

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

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

[Koha] Import notes with line break

[Tiago Murakami]

Hi,

I need to import notes with line breaks. I try to use "space space", "" and "line break in marcedit and it did not work. Which character should
I use?

Thanks in advance

-- 
Tiago Murakami
___

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

Re: [Koha] Temporary workarounds for bug 23091 to charge overdue fines on formerly lost items

[Joelle Hannert]

I ended up creating a worksheet in Google sheets to help auto-calculate the
amount that should be charged. Happy to share if others are having this
same issue.

On Wed, Sep 23, 2020 at 2:20 PM Joelle Hannert  wrote:

> I recently discovered that our library is being impacted by bug 23091 -
> Add options to charge new or restore forgiven overdues when a lost item is
> returned.
>  I'm
> curious to hear if others have a good workaround process for re-charging
> overdues manually when items are returned, or are you just forgiving the
> fines until there is a fix? I'm worried about how to clearly communicate to
> circ staff how to properly re-calculate overdue fines once assumed lost
> items are returned...especially with our library having reduced open days
> (so less days when a fine should have accrued) during COVID.
>
> --
> Joelle Hannert
> Library Technical Services Coordinator
> Northwestern Michigan College
> (231) 995-1684
> Work days: M, T, Th, F
>


-- 
Joelle Hannert
Library Technical Services Coordinator
Northwestern Michigan College
(231) 995-1684
Work days: M, T, Th, F
___

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

[Koha] Temporary workarounds for bug 23091 to charge overdue fines on formerly lost items

[Joelle Hannert]

I recently discovered that our library is being impacted by bug 23091 - Add
options to charge new or restore forgiven overdues when a lost item is
returned.  I'm
curious to hear if others have a good workaround process for re-charging
overdues manually when items are returned, or are you just forgiving the
fines until there is a fix? I'm worried about how to clearly communicate to
circ staff how to properly re-calculate overdue fines once assumed lost
items are returned...especially with our library having reduced open days
(so less days when a fine should have accrued) during COVID.

-- 
Joelle Hannert
Library Technical Services Coordinator
Northwestern Michigan College
(231) 995-1684
Work days: M, T, Th, F
___

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

[Koha] How to add code to Marc record and display it in opac?

[Pavlo Bobesiuk]

Hi everyone.
Someone tried to add code of embed book to marc record and display it in
the opac html5 media player?
I have an idea to convert the first pages of books into flipbooks (
www.anyflip.com) and put code in marc record to be able to read them in
opac media player.
For example I would like to add this code:

http://online.anyflip.com/mepon/fath/";  seamless="seamless" scrolling="no"
frameborder="0" allowtransparency="true" allowfullscreen="true" >

to marc record of some book in 856u field, but in opac i see only code, I
don't see frame with flip book.
help me please realize this idea

Paolo
-- 
З повагою
Павло Бобесюк=))
___

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

Re: [Koha] Error in SQL during upgrade to 20.05.04

[Craig Butosi]

Hi all,

I can confirm the exact same error on my machine after sudo apt-get update
&& sudo apt-get upgrade to Koha 20.05.04. (Currently running: Koha 20.05.04
on Ubuntu 18.04.5, MariaDB 10.1.44).
No errors reported in var/log/mysql.
Koha seems to be working okay and that the new syspref is visible in Koha
--> Administration -->  Global System Preferences.
No warnings listed in About Koha --> System Information

C

Craig Butosi, MA, MLIS, B Mus (Hons)
Library: library.craigbutosi.ca



On Wed, Sep 23, 2020 at 9:04 AM Mike Lake  wrote:

> Hi
>
> Versions I'm using are:
>
> Debian_Stretch version 9.13 with sources being "deb
> http://debian.koha-community.org/koha stable main"
> Mariadb  Ver 15.1 Distrib 10.1.45-MariaDB, for debian-linux-gnu
>
>
> ---
> Mike Lake
>
> On 2020-09-23 20:42, Mike Lake wrote:
> > Hi
> >
> > Tonight I upgraded our Koha and the following errors occurred from an
> > aptitude update.
> > Update was koha-common 20.05.03-2 to 20.05.04-1
> > I have two instances "library" and "libtest2".
> > Both still appear to be working but the error is concerning.
> >
> >
> > $ sudo aptitude update
> > The following packages will be upgraded:
> >   koha-common
> > 
> > Get: 1 http://debian.koha-community.org/koha stable/main amd64
> > koha-common all 20.05.04-1 [37.3 MB]
> > Preparing to unpack .../koha-common_20.05.04-1_all.deb ...
> > Unpacking koha-common (20.05.04-1) over (20.05.03-2) ...
> > Processing triggers for systemd (232-25+deb9u12) ...
> > Setting up koha-common (20.05.04-1) ...
> >
> > Upgrading database schema for library
> > DBD::mysql::db do failed: You have an error in your SQL syntax; check
> > the manual that corresponds to your MariaDB server version for the
> > right syntax to use near '' at line 1 [for Statement "
> > INSERT IGNORE INTO systempreferences ( `variable`, `value`, `options`,
> > `explanation`, `type` ) VALUES
> >('DefaultLongOverdueSkipLostStatuses', '', NULL, 'Skip these lost
> > statuses by default in longoverdue.pl', 'Free'),
> > "] at
> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> > line 22388.
> > Upgrade to 20.05.03.001 done [19:42:16]: Bug 25958 - Allow LongOverdue
> > cron to exclude specified lost values
> > Upgrade to 20.05.04.000 done [19:42:16]: 20.05.04 release
> >
> > Upgrading database schema for libtest2
> > DBD::mysql::db do failed: You have an error in your SQL syntax; check
> > the manual that corresponds to your MariaDB server version for the
> > right syntax to use near '' at line 1 [for Statement "
> > INSERT IGNORE INTO systempreferences ( `variable`, `value`, `options`,
> > `explanation`, `type` ) VALUES
> >('DefaultLongOverdueSkipLostStatuses', '', NULL, 'Skip these lost
> > statuses by default in longoverdue.pl', 'Free'),
> >"] at
> > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
> > line 22388.
> > Upgrade to 20.05.03.001 done [19:42:16]: Bug 25958 - Allow LongOverdue
> > cron to exclude specified lost values
> > Upgrade to 20.05.04.000 done [19:42:16]: 20.05.04 release
> >
> > Processing triggers for man-db (2.7.6.1-2) ...
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Reading extended state information...
> >
> >
> > ---
> > Mike Lake
> >
> >
> > ___
> >
> > 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] Error in SQL during upgrade to 20.05.04

[Mike Lake]

Hi

Versions I'm using are:

Debian_Stretch version 9.13 with sources being "deb 
http://debian.koha-community.org/koha stable main"

Mariadb  Ver 15.1 Distrib 10.1.45-MariaDB, for debian-linux-gnu


---
Mike Lake

On 2020-09-23 20:42, Mike Lake wrote:

Hi

Tonight I upgraded our Koha and the following errors occurred from an
aptitude update.
Update was koha-common 20.05.03-2 to 20.05.04-1
I have two instances "library" and "libtest2".
Both still appear to be working but the error is concerning.


$ sudo aptitude update
The following packages will be upgraded:
  koha-common

Get: 1 http://debian.koha-community.org/koha stable/main amd64
koha-common all 20.05.04-1 [37.3 MB]
Preparing to unpack .../koha-common_20.05.04-1_all.deb ...
Unpacking koha-common (20.05.04-1) over (20.05.03-2) ...
Processing triggers for systemd (232-25+deb9u12) ...
Setting up koha-common (20.05.04-1) ...

Upgrading database schema for library
DBD::mysql::db do failed: You have an error in your SQL syntax; check
the manual that corresponds to your MariaDB server version for the
right syntax to use near '' at line 1 [for Statement "
INSERT IGNORE INTO systempreferences ( `variable`, `value`, `options`,
`explanation`, `type` ) VALUES
   ('DefaultLongOverdueSkipLostStatuses', '', NULL, 'Skip these lost
statuses by default in longoverdue.pl', 'Free'),
"] at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 22388.
Upgrade to 20.05.03.001 done [19:42:16]: Bug 25958 - Allow LongOverdue
cron to exclude specified lost values
Upgrade to 20.05.04.000 done [19:42:16]: 20.05.04 release

Upgrading database schema for libtest2
DBD::mysql::db do failed: You have an error in your SQL syntax; check
the manual that corresponds to your MariaDB server version for the
right syntax to use near '' at line 1 [for Statement "
INSERT IGNORE INTO systempreferences ( `variable`, `value`, `options`,
`explanation`, `type` ) VALUES
   ('DefaultLongOverdueSkipLostStatuses', '', NULL, 'Skip these lost
statuses by default in longoverdue.pl', 'Free'),
   "] at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
line 22388.
Upgrade to 20.05.03.001 done [19:42:16]: Bug 25958 - Allow LongOverdue
cron to exclude specified lost values
Upgrade to 20.05.04.000 done [19:42:16]: 20.05.04 release

Processing triggers for man-db (2.7.6.1-2) ...
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...


---
Mike Lake


___

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] Error in SQL during upgrade to 20.05.04

[Mike Lake]

Hi

Tonight I upgraded our Koha and the following errors occurred from an 
aptitude update.

Update was koha-common 20.05.03-2 to 20.05.04-1
I have two instances "library" and "libtest2".
Both still appear to be working but the error is concerning.


$ sudo aptitude update
The following packages will be upgraded:
  koha-common

Get: 1 http://debian.koha-community.org/koha stable/main amd64 
koha-common all 20.05.04-1 [37.3 MB]

Preparing to unpack .../koha-common_20.05.04-1_all.deb ...
Unpacking koha-common (20.05.04-1) over (20.05.03-2) ...
Processing triggers for systemd (232-25+deb9u12) ...
Setting up koha-common (20.05.04-1) ...

Upgrading database schema for library
DBD::mysql::db do failed: You have an error in your SQL syntax; check 
the manual that corresponds to your MariaDB server version for the right 
syntax to use near '' at line 1 [for Statement "
INSERT IGNORE INTO systempreferences ( `variable`, `value`, `options`, 
`explanation`, `type` ) VALUES
   ('DefaultLongOverdueSkipLostStatuses', '', NULL, 'Skip these lost 
statuses by default in longoverdue.pl', 'Free'),
"] at 
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl 
line 22388.
Upgrade to 20.05.03.001 done [19:42:16]: Bug 25958 - Allow LongOverdue 
cron to exclude specified lost values

Upgrade to 20.05.04.000 done [19:42:16]: 20.05.04 release

Upgrading database schema for libtest2
DBD::mysql::db do failed: You have an error in your SQL syntax; check 
the manual that corresponds to your MariaDB server version for the right 
syntax to use near '' at line 1 [for Statement "
INSERT IGNORE INTO systempreferences ( `variable`, `value`, `options`, 
`explanation`, `type` ) VALUES
   ('DefaultLongOverdueSkipLostStatuses', '', NULL, 'Skip these lost 
statuses by default in longoverdue.pl', 'Free'),
   "] at 
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl 
line 22388.
Upgrade to 20.05.03.001 done [19:42:16]: Bug 25958 - Allow LongOverdue 
cron to exclude specified lost values

Upgrade to 20.05.04.000 done [19:42:16]: 20.05.04 release

Processing triggers for man-db (2.7.6.1-2) ...
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...


---
Mike Lake


___

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