So I had a chance to go back and hit this problem again this morning... 1. I ran the latest security updates on the OS itself (Unbuntu 16.04). Checked on Koha (17.05.10) and everything was running fine...returning search results as expected. 2. Restarted the server several times and after each restart, Koha was still working with the /var/run/koha directories present as expected. 3. Updated Koha (--> 17.05.11), restarted Koha and everything was still okay. 4. Restarted the server and the /var/run/koha directories had gone missing with Zebra no longer able to start. 5. If I run "sudo koha-create-dirs instance-name1" and "koha-start-zebra instance-name1"...I am able to search the catalog with results returned. 6. Restarting the OS takes down Koha yet again.
My understanding is that in Ubuntu, the directories/files in /var/run are considered volatile and need to be recreated by individual services on each restart of the OS. That seems to be taking place with 17.05.10. With no change to the OS, this no longer seems to be occurring in 17.05.11. Digging through code, it looks as though this should occur when koha-zebra-ctl.sh is called. At the very least, it appears those directories should be created if "sudo /etc/init.d/koha-common start" is run...they're not. Running "sudo service --status-all" shows the koha-common service as not running, though memcached does seem to be. If I run koha-create-dirs and koha-start-zebra for all instances, then run "sudo service koha-common start"...Koha still shows as not running. Other ideas? For now, I'll leave this server running on 17.05.10 and try updating to 17.11 when 18.05 is released later this month... gcb >Yep that's write, create the dirs again and start zebra with the command from >Michael. >It's the Ubuntu restart that's deleting the dirs, not the upgrade. >Chris _______________________________________________ Koha mailing list http://koha-community.org [email protected] https://lists.katipo.co.nz/mailman/listinfo/koha
