Matthew Metzger wrote:
Matthew Metzger wrote:
Chris Cormack wrote:
I had another problem that I thought was related, but probably isn't. I get an error when I try to do a z39.50 search. I thought that 2.2.7 and later used a different way to do z39.50. I was hoping that upgrading would simplify the process. Anyway, here's the error: ---- Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [my email] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log. ----
I have started the z39.50 daemon by invoking: /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-launch.sh
Hi Matthew
Ive gotta do some work at the moment, but if no one has taken a crack at answering you by the time I take a lunch break, ill take a look.
To help, if you could find the error_log and paste the relevant bit in from there, that might help.
Chris -- Chris Cormack chris.cormack@liblime.com VP Research and Development www.liblime.com LibLime +64 21 542 131
Hello again,
I've updated the yaz toolkit to yaz-3.0.6 and installed Net::Z3950::ZOOM, but still have no results when doing a z39.80 search. Here's the error message I get:
---- Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [my email address] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log. ----
I've posted lines from my koha-error_log elsewhere in this thread.
thanks in advance for any help.
-Matthew
I took a look at lines 135 and 145 of /usr/local/koha/intranet/cgi-bin/z3950/search.pl and it looks like I'm getting an error because of not being able to connect to the remote z39.50 server. I'm not sure why this is the case because it worked fine before the upgrade from 2.2.6 to 2.2.9. Any help would be greatly appreciated. thanks for your time, Matthew Metzger