Summary: | Memcached not active but well configured to | ||
---|---|---|---|
Product: | Koha | Reporter: | ducry.remy |
Component: | Web services | Assignee: | 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: | ||
Circulation function: |
Description
ducry.remy
2019-03-13 10:43:21 UTC
what does this command return? service memcached status 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 (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.... 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. |