[Koha-bugs] [Bug 20820] New: koha fails to connect to memcached until restart after debian package upgrade 17.11.06-1 -> 18.05.00-1 on Ubuntu Xenial 16.04

[bugzilla-daemon at bugs.koha-community.org]

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

            Bug ID: 20820
           Summary: koha fails to connect to memcached until restart after
                    debian package upgrade 17.11.06-1 -> 18.05.00-1 on
                    Ubuntu Xenial 16.04
 Change sponsored?: ---
           Product: Koha
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Packaging
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: helix84 at centrum.sk
        QA Contact: testopia at bugs.koha-community.org
                CC: mirko at abunchofthings.net

On Ubuntu Xenial 16.04, after upgrading koha from 17.11.06-1 to 18.05.00-1 from
official koha debian package, the following error is shown in the dpkg log and
accessing koha opac and koha intranet shows an unstyled interface.


...
Upgrade to 17.12.00.044 done (Bug 20624 - Disable OAuth2 client credentials
grant by default)
Upgrade to 18.05.00.000 done (Koha 18.05)

Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the
unix socket permissions set properly? Is the host reachable?
If you ignore this warning, you will face performance issues

Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the
unix socket permissions set properly? Is the host reachable?
If you ignore this warning, you will face performance issues
Updated the cs-CZ translations.
Setting up libhijk-perl (0.26-1) ...
Setting up libtype-tiny-xs-perl (0.012-1build1) ...
Use of uninitialized value $fn in exists at
/usr/share/perl5/NeedRestart/Utils.pm line
100.=========================================================================================================================
                      ]
Use of uninitialized value $fn in stat at /usr/share/perl5/NeedRestart/Utils.pm
line 102.
Use of uninitialized value in list assignment at
/usr/share/perl5/NeedRestart/Interp/Perl.pm line 132.
Use of uninitialized value $fn in exists at
/usr/share/perl5/NeedRestart/Utils.pm line
100.==================================================================================================================================
             ]
Use of uninitialized value $fn in stat at /usr/share/perl5/NeedRestart/Utils.pm
line 102.
Use of uninitialized value in list assignment at
/usr/share/perl5/NeedRestart/Interp/Perl.pm line 132.
Scanning processes...                                                           
Scanning candidates...                                                          
Scanning linux images...                                                        
Restarting services using systemd...
No containers need to be restarted.



$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.4 LTS
Release:        16.04
Codename:       xenial

$ grep MEMCACHED_SERVERS /etc/koha/koha-sites.conf
# MEMCACHED_SERVERS: comma separated list of memcached servers (ip:port)
MEMCACHED_SERVERS="127.0.0.1:11211"

$ sudo systemctl status memcached.service 
● memcached.service - memcached daemon
   Loaded: loaded (/lib/systemd/system/memcached.service; enabled; vendor
preset: enabled)
   Active: active (running) since Fri 2018-05-25 13:01:18 CEST; 32min ago
 Main PID: 1016 (memcached)
    Tasks: 6
   Memory: 12.1M
      CPU: 110ms
   CGroup: /system.slice/memcached.service
           └─1016 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127.0.0.1

May 25 13:01:18 koha systemd[1]: Started memcached daemon.

$ sudo netstat -tulpn | grep 11211
tcp        0      0 127.0.0.1:11211         0.0.0.0:*               LISTEN     
1016/memcached  


The problem is not alleviated even after restarting the koha-common service and
the memcached service. It is resolved by restarting the host.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.