Oops, accidentally hit send too soon.Also, to keep the regular koha-z3950-responder script from interfering you have to rename the config dir as Zeno did. I picked z3950-srv, but anything will work so long as you rename all of them the same way.Jason
koha-z3950-responder@.service
Description: Bina
I was glad that I remembered this exchange, I was setting up ES and the z3950
responder today and having some trouble. I poked at the script a bit to see
what might be the problem but didn’t have time to figure out the issue. I am
fairly comfortable with systemd units though, so I put together t
Hi,
I use the suggestion of Fridolin and now I'm a working z39.50 with
ElasticSearch on Koha 20.11
My SystemD unit (etc/systemd/system/koha-z39-el.service):
[Unit]
Description=Koha Z39.50 Service
[Service]
Type=simple
User=lib-koha
Environment="KOHA_CONF=/etc/koha/sites/lib/koha-conf.xml"
"
Hi,
We at Biblibre use one Koha per machine so whe created a SystemD unit :
[Unit]
Description=Koha Z39.50 Service
[Service]
Type=simple
User=koha
Environment="KOHA_CONF=/home/koha/etc/koha-conf.xml"
"PERL5LIB=/home/koha/src"
ExecStart=/home/koha/src/misc/z3950_responder.pl --debug
[Install]
Hi to,
I'm trying to use ElasticSearch everywhere with Koha 20.11
I'm working on Debian 10, EleasticSearch 6.8.13, Java openjdk 11 (Debian
package)
The search on Opac and Intranet is OK.
Problems are on z39.50 server.
With bug 13937 a z39.50/SRU server is ready also with ES as search back-end.
