Thanks Lennon! I enabled and started Plack (with one extra command needed): - sudo koha-plack --enable library - sudo a2enmod headers proxy_http - sudo koha-plack --start library After doing so I was hoping the problem would be magically* fixed but alas batch check outs still aren't working reliably: - Choose a patron - Switch to batch check out - Paste in 88 barcodes - Click "check out" - Wait over 10 minutes for a "Gateway Timeout: The gateway did not receive a timely response from the upstream server or application." While it was running I ran htop to see if memory or processor was causing a bottleneck but neither processor was maxed out and the RAM was hovering around 1.44G of 3.84G. My plan for tomorrow is to try profiling circulation.pl using Devel::NYTProf ( https://wiki.koha-community.org/wiki/Profiling_with_DevelNYTProf) and see if that gives me any clues. Matt On Tue, 14 Sept 2021 at 14:10, Lennon Mazonde <lennon@kohasupport.com> wrote:

Hi Matthew,

1. To enable Plack you need to run

sudo koha-plack --enable instancename

then

sudo koha-plack --start instancename

2. To resolve the admin email warning, go to Home > Administration > System preferences > Interface options > KohaAdminEmailAddress and enter your admin email. You may have to do some additional configuration on your back-end server to setup an email server such as Postfix to enable your Koha instance to send out emails.

I hope this helps!

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

On 9/14/21 8:55 AM, Matthew Lindfield Seager wrote:

...

Hi Katrin,

Memcached is installed and running according to the About Koha page. Following the second lot of instructions at https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see that it has been handling requests. I also compared the old server (post upgrade to 21.05) with the new server and both have the same configuration in `/etc/memcached.conf`. According to the about page configuration is coming from koha-conf.xml but I'm not sure where to find that file (and it doesn't seem like Memcached is the culprit so I didn't bother installing mlocate to find it).

The only mentions of Plack I can see are on the Perl Modules info page:

- Plack::Middleware::ReverseProxy (0.14) - 0.16 - Plack::Middleware::LogWarn (0.001002) - 0.001002

I could not find any info in the Wiki about Plack other than the ~2017 Plack page <https://wiki.koha-community.org/wiki/Plack> and a brief mention on the Performance page <https://wiki.koha-community.org/wiki/Performance>. Is there anything I need to do to enable it?

Both old and new server have a single warning on the System information tab: "System preference 'KohaAdminEmailAddress' does not contain a valid email address. Emails will not be sent."

Comparing the Server Information page for the old server (which is super slow after the 21.05 upgrade but doesn't time out) with the new server (which is super slow AND times out), the only differences are:

- Minor Koha version (old server is 21.05.02.003, new server is 21.05.03.001) - Slightly different kernel release and version (old is 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) - Different MySQL versions (old is "mysql Ver 15.1 Distrib 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", new is "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))"

Thanks so much for some additional places to look for issues! If something in there gives a clue or if anyone has any other suggestions for things to check I'm all ears!

Matt

On Mon, 13 Sept 2021 at 07:01, <koha-request@lists.katipo.co.nz> wrote:

...

Date: Sun, 12 Sep 2021 12:46:57 +0200 From: Katrin Fischer <katrin.fischer.83@web.de> To: koha@lists.katipo.co.nz Subject: Re: [Koha] Batch check outs timing out after upgrade and migration Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80@web.de> Content-Type: text/plain; charset=utf-8; format=flowed

Hi Matthew,

is there anything on the "About Koha" page that might give a clue?

* Is Memcached running? * Is Plack configured and running? * Is there any error or warning displayed on the System information tab?

Hope this helps,

Katrin

_______________________________________________

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

Are you getting any additional errors in your log files - esp. MySQL, Apache and Koha logs?  I'm groping in the dark here but I wonder if you need change the limits in your apache2.conf (maybe increase your timeout value?) or increase the max input and execution time in php.ini? This sounds pretty basic but you could also try using a different browser after clearing your cache and cookies, and see if that makes a difference. 88 barcodes in batch checkout seems quite a lot to me, do you have the same issues when checking out fewer barcodes, e.g. 10? In your first email you said:

I fear our next best option might be to create a new (MariaDB) server from the original back ups and manually re-enter the past 4 days worth of borrowing and returns 😔

Have you considered setting up offline circulation <https://kohasupport.com/koha-hacks-how-to-install-the-koha-offline-circulation-plugin/>so you can at least continue serving your patrons (I assume you're in a production environment) until you can resolve the issue? Lennon Mazonde www.kohasupport.com lennon@kohasupport.com WhatsApp @ (+1) 717.489.0195 On 9/14/21 10:02 AM, Matthew Lindfield Seager wrote:

Thanks Lennon!

I enabled and started Plack (with one extra command needed):

- sudo koha-plack --enable library - sudo a2enmod headers proxy_http - sudo koha-plack --start library

After doing so I was hoping the problem would be magically* fixed but alas batch check outs still aren't working reliably:

- Choose a patron - Switch to batch check out - Paste in 88 barcodes - Click "check out" - Wait over 10 minutes for a "Gateway Timeout: The gateway did not receive a timely response from the upstream server or application."

While it was running I ran htop to see if memory or processor was causing a bottleneck but neither processor was maxed out and the RAM was hovering around 1.44G of 3.84G.

My plan for tomorrow is to try profiling circulation.pl using Devel::NYTProf ( https://wiki.koha-community.org/wiki/Profiling_with_DevelNYTProf) and see if that gives me any clues.

Matt

On Tue, 14 Sept 2021 at 14:10, Lennon Mazonde <lennon@kohasupport.com> wrote:

...

Hi Matthew,

1. To enable Plack you need to run

sudo koha-plack --enable instancename

then

sudo koha-plack --start instancename

2. To resolve the admin email warning, go to Home > Administration > System preferences > Interface options > KohaAdminEmailAddress and enter your admin email. You may have to do some additional configuration on your back-end server to setup an email server such as Postfix to enable your Koha instance to send out emails.

I hope this helps!

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

On 9/14/21 8:55 AM, Matthew Lindfield Seager wrote:

...

Hi Katrin,

Memcached is installed and running according to the About Koha page. Following the second lot of instructions at https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see that it has been handling requests. I also compared the old server (post upgrade to 21.05) with the new server and both have the same configuration in `/etc/memcached.conf`. According to the about page configuration is coming from koha-conf.xml but I'm not sure where to find that file (and it doesn't seem like Memcached is the culprit so I didn't bother installing mlocate to find it).

The only mentions of Plack I can see are on the Perl Modules info page:

- Plack::Middleware::ReverseProxy (0.14) - 0.16 - Plack::Middleware::LogWarn (0.001002) - 0.001002

I could not find any info in the Wiki about Plack other than the ~2017 Plack page <https://wiki.koha-community.org/wiki/Plack> and a brief mention on the Performance page <https://wiki.koha-community.org/wiki/Performance>. Is there anything I need to do to enable it?

Both old and new server have a single warning on the System information tab: "System preference 'KohaAdminEmailAddress' does not contain a valid email address. Emails will not be sent."

Comparing the Server Information page for the old server (which is super slow after the 21.05 upgrade but doesn't time out) with the new server (which is super slow AND times out), the only differences are:

- Minor Koha version (old server is 21.05.02.003, new server is 21.05.03.001) - Slightly different kernel release and version (old is 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) - Different MySQL versions (old is "mysql Ver 15.1 Distrib 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", new is "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))"

Thanks so much for some additional places to look for issues! If something in there gives a clue or if anyone has any other suggestions for things to check I'm all ears!

Matt

On Mon, 13 Sept 2021 at 07:01, <koha-request@lists.katipo.co.nz> wrote:

...

Date: Sun, 12 Sep 2021 12:46:57 +0200 From: Katrin Fischer <katrin.fischer.83@web.de> To: koha@lists.katipo.co.nz Subject: Re: [Koha] Batch check outs timing out after upgrade and migration Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80@web.de> Content-Type: text/plain; charset=utf-8; format=flowed

Hi Matthew,

is there anything on the "About Koha" page that might give a clue?

* Is Memcached running? * Is Plack configured and running? * Is there any error or warning displayed on the System information tab?

Hope this helps,

Katrin

_______________________________________________

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