← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
12:32 | martinmorris | another question for people, i'm finding it hard to get a clear answer to why I'd be getting ERROR 114 in my zebra log when i search for authorities |
13:40 | still trying to debug this - can anybody say if this looks reasonable for a command to access the authorities database using the yaz-client? | |
13:40 | Z> authentication kohauser/zebrastripes | |
13:40 | Authentication set to Open (kohauser/zebrastripes) | |
13:40 | Z> open tcp:localhost:9999/authorities | |
13:40 | Connecting...error = System (lower-layer) error: Connection refused | |
13:40 | can't see why i can't connect like that | |
13:41 | gmcharlt | try Z> |
13:41 | try Z> open localhost:9999/authorities | |
13:41 | martinmorris | ok |
13:41 | nope | |
13:42 | can't connect to biblios either, yet i know that's working fine | |
13:42 | gmcharlt | could you pastebin your koha-conf.xml ? |
13:43 | martinmorris | certainly, how do I do that? |
13:43 | gmcharlt | first 20 lines or so should enough - go to pastebin.com , copy in the text, then post the link |
13:43 | martinmorris | ok |
13:44 | http://pastebin.com/d5bbcd684 | |
13:45 | gmcharlt | ok, bib and authority servers are being accessed through Unix-domain sockets, not TCP ports |
13:45 | so to connect in yaz-client: | |
13:45 | martinmorris | ah, of cours |
13:45 | gmcharlt | Z> authentication ... |
13:45 | martinmorris | bibliosocket etc... |
13:46 | gmcharlt | Z> open unix:/var/run/koha/zebradb/bibliosocket |
13:46 | Z> base authorities | |
13:46 | martinmorris | thank you |
13:47 | can you tell me what ERROR 114 is all about? | |
13:47 | gmcharlt | can happen in several ways |
13:48 | but one likely candidate is that authority records haven't been indexed yet | |
13:48 | the zebrasrv log may help | |
13:49 | martinmorris | i've definitely indexed them |
13:49 | rebuild_zebra -a -r | |
13:49 | rebuild_zebra.pl -a - r rather | |
13:50 | gmcharlt | running an authority search and pasting in the correspoinding zebrasrv log would help - gives the exact Z39.50 query used |
13:51 | martinmorris | give me a few secs |
13:52 | 14:52:17-18/07 zebrasrv(1) [session] Session - OK 1 unix:/var/run/koha/zebradb/authoritysocket 15937 | |
13:52 | 14:52:17-18/07 zebrasrv(1) [request] Auth idPass kohauser - | |
13:52 | 14:52:17-18/07 zebrasrv(1) [request] Init OK - ID:81/81 Name:ZOOM-C/YAZ Version:1.154/3.0.34 | |
13:52 | 14:52:17-18/07 zebrasrv(1) [log] dict_lookup_grep: (\x01\x16)(PERSO) | |
13:52 | 14:52:17-18/07 zebrasrv(1) [log] dict_lookup_grep: (\x01\x16)(NAME) | |
13:52 | 14:52:17-18/07 zebrasrv(1) [request] Search authorities ERROR 114 1 1+0 RPN @attrset Bib-1 @or @attr "1=Heading" @attr 7=1 0 @and @attr 5=100 @attr "1=authtype" PERSO_NAME @attr 4=6 @attr 5=1 @attr "1=Heading-Main" Zamenhof | |
13:52 | 14:52:17-18/07 zebrasrv(1) [session] Connection closed by client | |
13:53 | gmcharlt | do you use MARC21 or UNIMARC? if you use MARC21, when you installed Koha, did you choose the 'dom' mode for authority indexing? |
13:54 | martinmorris | i use marc21 |
13:54 | and yes, i believe i did choose dom mode | |
13:54 | how would i check though? | |
13:54 | installation log? | |
13:54 | gmcharlt | yes |
13:55 | martinmorris | let me track that down |
13:57 | AUTH_INDEX_MODE=dom | |
13:58 | gmcharlt | ok |
13:59 | could you pastebin in the MARC view of the Zamenhof authority record? | |
13:59 | ori | |
13:59 | as stored in Koha, not the original one you loaded | |
13:59 | martinmorris | so from the koha mysql database? |
13:59 | gmcharlt | e.g., select * from auth_header where authid = foo |
13:59 | martinmorris | good, yes |
13:59 | hold on | |
14:01 | Snow_Fox | Question: Anyone ever play with HP Storage Works Data Protection Express? |
14:01 | martinmorris | http://pastebin.com/d70ece681 |
14:01 | i imported it from the library of congress | |
14:03 | gmcharlt | martinmorris: what version of Koha are you runnign 3.0.3 or HEAD? |
14:03 | it's the @attr "1=Heading" @attr 7=1 0 part of the query that I'm finding suspicious | |
14:04 | martinmorris | 3.00.01.005 according to the about koha pages |
14:04 | ok | |
14:04 | what's wrong with that do you think? | |
14:04 | gmcharlt | there's been a fair amount of authority search changes |
14:04 | I'd recommend upgrading to 3.0.3 | |
14:04 | since you're on only 3.0.1 | |
14:05 | martinmorris | ok, happy to try that |
14:05 | trust it isn't too difficult - never upgraded koha before (and this isn't a production installation) | |
14:05 | gmcharlt | no, that all that different |
14:07 | martinmorris | wish me luck |
14:07 | gmcharlt | good luck! |
16:46 | greenmang0 | indradg: hello |
16:47 | indradg | greenmang0, hi |
16:47 | greenmang0 | indradg: had dinner? :) |
16:48 | indradg | greenmang0, not yet... the cook didn't turn up... planning on putting together a batch of khichdi in a bit |
16:49 | greenmang0 | indradg: oh... so where is your family?? |
16:50 | indradg: live alone... away from home? | |
16:55 | indradg | greenmang0, nope, very much at home, but my wife isn't too handy with indian food |
16:55 | greenmang0 | indradg: ok :) |
17:51 | martinmorris | hello, don't know if gmcharlt is still there? |
17:51 | anyway, my ERROR 114 problem is still there, and I've upgraded | |
17:51 | pianohacker | @seen gmcharlt |
17:51 | munin | pianohacker: gmcharlt was last seen in #koha 3 hours, 44 minutes, and 9 seconds ago: <gmcharlt> good luck! |
17:51 | gmcharlt | martinmorris: drat |
17:51 | martinmorris | hello there |
17:51 | yeah, it is a bit of a shame | |
17:51 | good to have upgraded though | |
17:52 | koha version is 3.00.02.012 - just to check | |
17:52 | and i've rebuild my indexes | |
17:52 | gmcharlt | martinmorris: I'll poke around with the authority record, to see if there's a data-dependent issue, but won't get around to it until later this evening |
17:52 | martinmorris | that's great, thank you |
17:53 | one other minor thing | |
17:54 | previously there was a bar at the bottom of the screen (in the staff client) where i could change the language. that's now disappeared and the browser window seems to flash slightly as if it's trying to draw that bar but fails (if you get what I mean) | |
17:54 | gmcharlt | check to see what your stafflanguages syspref is set tup - make sure more than one is selected |
17:55 | martinmorris | ah ok, thanks |
17:59 | pianohacker | Hmm. According to http://www.loc.gov/z3950/agenc[…]fns/bib1diag.html , 114 is Unsupported Use attribute. That's surprisingly unhelpful |
17:59 | </sarcasm> | |
18:00 | martinmorris | that's precisely my problem piano |
18:00 | :) | |
18:00 | no real idea how to go beyond that and debug | |
18:02 | although i see the copac.ac.uk site has some further info | |
18:05 | apparently i'm searching on a field that isn't supported | |
20:08 | separate small question - if i were to run koha over two machines, one slower than the other, i'd put the webserver on the slower machine and the db on the faster. Is that right? | |
20:59 | Snow_Fox | Martimorris i would think that would be the correct answer |
20:59 | since the db will be hitting harder then a web service | |
21:00 | generally speaking | |
21:03 | martinmorris | thanks snow_fox, that's what i went for :) |
21:07 | Snow_Fox | np |
00:37 | martinmorris | can somebody tell me about pazpar2? is it used only to search other z39.50 servers? |
00:38 | pianohacker1 | That's one of its uses |
00:38 | pianohacker | Koha uses it for grouping together results based on their title/isbn/etc. |
00:38 | martinmorris | i'm just setting up a two-server system, so i want to configure zebra on one machine to use tcp ports rather than sockets |
00:39 | i've done that, using the publicserver running on port 9999 | |
00:39 | can i then tell the other machine to just connect for authoirty and biblio searching on 9999 on the other machine? | |
00:39 | or do i need separate servers on 9998 and 9999? | |
00:39 | pianohacker | Hmm |
00:40 | martinmorris | :) |
00:40 | pianohacker | You could probably get it all on one port |
00:40 | martinmorris | i could just try it all out on one port i suppose |
00:40 | pianohacker | But it would most likely be easiest to do two |
00:40 | martinmorris | koha-conf.xml implies i can do it all via a publicserver instance |
00:40 | but i wasn't sure | |
00:40 | pianohacker | Would involve less mucking around with the config files |
00:40 | martinmorris | ah, really? |
00:40 | pianohacker | I believe so |
00:41 | martinmorris | having two ports? |
00:42 | i'd have <listen id="biblioserver" >tcp:@:9998</listen> and <listen id="authorityserver" >tcp:@:9999</listen> | |
00:42 | ? | |
00:43 | pianohacker | Yup |
00:43 | martinmorris | the only other difficulty i'm seeing is how to configure koha-conf.xml on the other machine to point to those ports |
00:44 | any advice? | |
00:45 | pianohacker | You might try simply copying the listen and serverinfo elements to the other server |
00:47 | martinmorris | oh, really? how would that work? on the receiving server (with 9998 and 9999 open) the config file just says to open up the ports, the remainder of the file is localhost |
00:48 | ah, it's ok, there's a brief explanation at the top which says where to put the host in | |
09:31 | Hello, not sure if anybody's awake but I'm having ERROR 114 problems with my authorities, can anybody advise? |
← Previous day | Today | Next day → | Search | Index