Paul A schreef op wo 21-01-2015 om 20:36 [-0500]:
k318-ko+ 1285 0.0 0.0 114000 5532 ? S 19:47 0:00 \_ zebrasrv -v none,fatal,warn -f /etc/koha/sites/k318/koha-conf.xml
OK, so it is running.
I have no clue as to user k318-ko+
That's just a truncation of the username.
nor where --name=k318-koha-zebra came from.
It's just a name, to prevent the same thing being started twice.
koha-conf.xml has (for both bibs and auths, created by the install process): <user>k318-koha</user> <password>2YTE********Gxbk</password>
HOWEVER -- I have just (since reboot) found in zebra-output.log "Failed to bind to unix:/var/run/koha/zebradb/bibliosocket [No such file or directory]" and the same for authority socket.
That's suspect. Have you messed with the configuration? It should be creating the sockets in /var/run/koha/<instancename>/bibliosocket, etc. This is defined in the <listen> sections near the top of koha-conf.xml.
There is no file at all by that name on this box, but a quick look at our production box finds symbolic links at /run/koha/zebradb/ (but no file by that name.)
/run is not necessarily equal to /var/run. On the server I just checked, /run doesn't exist at all. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF