Bug 22504

Summary: Memcached not active but well configured to
Product: Koha Reporter: ducry.remy
Component: Web servicesAssignee: Bugs List <koha-bugs>
Status: CLOSED FIXED QA Contact: Testopia <testopia>
Severity: major    
Priority: P5 - low CC: josef.moravec
Version: 18.11   
Hardware: PC   
OS: Linux   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description ducry.remy 2019-03-13 10:43:21 UTC
Good morning, everyone, 
We are facing a problem related to Memcached.
Here are the details of the installation:
Koha Version 18.11.02.02.02.02.02.000
Ubuntu Server version 18.04
Installed under Linux
server information and memcached status: http://51.75.27.51/pref-sys.png

We have looked in the conf files and Memcached seems well configured but does not work as you can see in the screenshot.

Feel free to ask me for more details if necessary, have a great day.

Translated with www.DeepL.com/Translator
Comment 1 Josef Moravec 2019-03-14 09:35:25 UTC
what does this command return?

service memcached status
Comment 2 ducry.remy 2019-03-14 11:40:10 UTC
Hi Josef !

the command return : 
Connection to the memcached servers '127.0.0.1:11211' failed. Are the unix socket permissions set properly? Is the host reachable?
If you ignore this warning, you will face performance issues
Comment 3 Josef Moravec 2019-03-14 11:46:43 UTC
(In reply to ducry.remy from comment #2)
> Hi Josef !
> 
> the command return : 
> Connection to the memcached servers '127.0.0.1:11211' failed. Are the unix
> socket permissions set properly? Is the host reachable?
> If you ignore this warning, you will face performance issues

I don't think it is return of service status command - it should say if service is running, and what was the run command, and so on....
Comment 4 ducry.remy 2019-03-14 12:47:36 UTC
A colleague computer scientist came to our rescue, we disabled in the memcached configuration the -P option, it solved our problem.
We have a legal problem with the socket but it's not blocking for Koha.