Summary: | error "Connection to the memcached servers '__MEMCACHED_SERVERS__' failed" during install | ||
---|---|---|---|
Product: | Koha | Reporter: | Giuseppe Ciaccio <giuseppe.ciaccio> |
Component: | Installation and upgrade (command-line installer) | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P3 | CC: | costalc, dcook, giuseppe.ciaccio, jonathan.druart, katrin.fischer, mehmet.akgul, tomascohen, ulrich.kleiber |
Version: | Main | ||
Hardware: | PC | ||
OS: | Linux | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Giuseppe Ciaccio
2019-01-28 16:42:10 UTC
These are more so warnings than errors. I think you can safely ignore them, although Koha really should be updated to prevent the warnings from showing in the first place. This weird warning should be removed. (In reply to Tomás Cohen Arazi from comment #2) > This weird warning should be removed. +1 What's happening? debian/scripts/koha-translate set KOHA_CONF (for non-dev installs) to /etc/koha/koha-conf-site.xml.in, ecause our LangInstaller module needs some paths from there (like intrahtdoc). The problem is that this koha-conf does not have a valid memcached config, and so we reach Koha::Cache without correct values and get the warning. We definitively can ignore this warning, but it would be better to remove it of course. However I have no idea how to clean that. (In reply to Jonathan Druart from comment #4) > What's happening? > debian/scripts/koha-translate set KOHA_CONF (for non-dev installs) to > /etc/koha/koha-conf-site.xml.in, ecause our LangInstaller module needs some > paths from there (like intrahtdoc). > The problem is that this koha-conf does not have a valid memcached config, > and so we reach Koha::Cache without correct values and get the warning. > > We definitively can ignore this warning, but it would be better to remove it > of course. However I have no idea how to clean that. I've thought of a few strategies. The easiest is probably to add an environmental variable to koha-translate that can prevent L2 caching from being initialized in Koha::Cache. Alternatively: 1. Remove the dependency on C4::Context in LangInstaller, and instead pass intranetdir, opacdir, intrahtdocs, and opachtdocs as arguments to the LangInstaller constructor. 2. Customize C4::Context and Koha::Caches to pass an argument to the Koha::Cache constructor to prevent L2 (ie memcached) caching from initialising, and use this argument in koha-translate |