Try to modify 666 with 644 and change the owner of the file instead.
It's often a bad idea to let others with +w
2016-02-13 3:03 GMT+00:00 wildness :
> HI Katrin,
> Thank you so much for your help! I did a chmod 666 on the file I
> mentioned and reindexed and like
HI Katrin,
Thank you so much for your help! I did a chmod 666 on the file I
mentioned and reindexed and like magic the zebra server runs properly!
--
View this message in context:
http://koha.1045719.n5.nabble.com/Fixing-Zebra-After-Upgrade-tp5871038p5874440.html
Sent from the
Hi,
I think the permission problem is probably from running the reindexing
process with the wrong user - but I am not sure how to fix this for an
installation with packages.
Also, be careful about the remapping/changing of Koha-to-MARC-Mappings,
because it won't change your records, only the
Hi,
Wait progress:
20:01:18-05/02 zebraidx(12154) [warn] Cannot open
`/etc/koha/sites/library/zebra-biblios-dom.cfg' [Permission denied]
20:01:18-05/02 zebraidx(12154) [fatal] Cannot read config
/etc/koha/sites/library/zebra-biblios-dom.cfg
20:01:18-05/02 zebraidx(12155) [warn] Cannot open
Hi Katrin
Thank you so much for replying! I checked the mark mapping and it seems
to be in order, but how exactly do I assign do I get my set to match yours (
BIBLIONUMBER in : 999$c , BIBLIOITEMNUMBER in : 999$d). Sorry I'm a
software developer and i'm working with our librarian, but
Progress I played around with the mappings, but now I have a
persmission's error:
Wait progress:
20:01:18-05/02 zebraidx(12154) [warn] Cannot open
`/etc/koha/sites/library/zebra-biblios-dom.cfg' [Permission denied]
20:01:18-05/02 zebraidx(12154) [fatal] Cannot read config
Hi,
I think the about page might give a first important clue here - have you
checked that your Zebra server is indeed running? If it's not running in
the background, all searches will not return any results.
Can you run this on command line?
ps axf | grep "zebrasrv"
Something else that looks a
Hi All,
I've been trying to solve this issue for a about a month now and was
wondering if you all could provide any advice. This issue occurred after I
upgraded to version 3.18 and the previous version was at least two years
old, but I didn't note it down.
Our server is running Ubuntu
8 matches
Mail list logo