Did you reboot the server in between? The OS sometimes decides to clean up /var/run
You can run koha-create-dirs instancename and it will sort it out Chris On 9 May 2018 3:22:43 AM NZST, "Bortel, Gary" <gary.bor...@sos.wa.gov> wrote: >This morning we tried updating from 17.05.10 to 17.05.11. All seemed to >go well, but afterwards not results were returned from a search in >either the public or staff interfaces. Assuming Zebra had failed to >start, I ran "koha-start-zebra instance-name", but received the error >"Invalid --pidfiles argument: '/var/run/koha/instance-name/' (Directory >does not exist)". Checked /var/run and...the koha directory in fact no >longer existed. Reverting back to the old snapshot of this server shows >that directory in place. > >Is this expected behavior? Resolution? > >Multi-tenant installation >Koha 17.05.10 --> 17.05.11 >Ubuntu 16.04 >Running memcached, but not yet upgraded to Plack > >Thanks >gcb > > > >-----Original Message----- >From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of guille >Sent: Monday, April 30, 2018 6:14 AM >To: koha@lists.katipo.co.nz >Subject: Re: [Koha] Koha 17.05 and memcached > >sorry for my english is google translator > >yes, jonathan, i am testing plack in my installation, and it works >fine, but when I restart the server it disables the intranet and opac >page, and deletes at least that i know the file / var / run / koha. >what am I doing wrong. my version of koha is 17.05.11 > > >_______________________________________________ >Koha mailing list http://koha-community.org >Koha@lists.katipo.co.nz >https://lists.katipo.co.nz/mailman/listinfo/koha -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha