Re: [Koha] Koha Digest, Vol 45, Issue 92
Dear Members; I have a problem. Recently we upgraded our Koha catalogue to version 3. During the course of editing, we have met a challenge at one point and we can nolonger proceed. Some records indicating no call number can not be searched and be found except when one generates the Report through "Items with no checkouts" that we can see the records. For example, the following record can not be edited after generating it through reports: # 7082 No Call Number Barcode 7149 Title/ Auhor: Challenges and prospects for a new Nile water agreement : Ngʼwandu, Pius Yasebasi. The information one gets is as follows: An Error has Occurred! Error 404 * This error means that the link was broken and that the page doesn't exist * To report this error, you can email the Koha Administrator. * Use top menu bar to navigate to another part of Koha. What do I do? Simon J Engitu PArliament of Uganda Quoting koha-request@lists.katipo.co.nz:
Send Koha mailing list submissions to koha@lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request@lists.katipo.co.nz
You can reach the person managing the list at koha-owner@lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..."
Today's Topics:
1. internal error message (Carol McGeehon) 2. Re: internal error message (Joe Atzberger) 3. FIRSTSEARCH WORLDCAT Z39.50 issue? (Cab Vinton)
----------------------------------------------------------------------
Message: 1 Date: Tue, 28 Jul 2009 11:44:37 -0700 From: "Carol McGeehon" <clmcgeeh@co.douglas.or.us> Subject: [Koha] internal error message To: <koha@lists.katipo.co.nz> Message-ID: <BB68BAA78A982E4D86913D189AB3B78F436777@mercury.co.douglas.or.us> Content-Type: text/plain; charset="us-ascii"
I'm having a problem keeping the web interface up. I'm receiving the following error message:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@web4 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.
Additionally, a 500 Internal Server Error was encountered while trying to use an ErrorDocument to handle the request.
________________________________
Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.5 with Suhosin-Patch Server at 199.195.23.104 Port 8080
I've had someone with Linux experience look at it and tell me the permissions on the cgi-bin folder are being changed. We don't know why.
Can someone tell me what might be happening so I can fix it?
Carol McGeehon
Technical Support Manager
Douglas County Library System
1409 NE Diamond Lake Blvd
Roseburg, OR 97470
541-440-6005
To travel hopefully is a better thing than to arrive
Robert Louis Stevenson
On Wed, Jul 29, 2009 at 1:37 AM, <sengitu@parliament.go.ug> wrote:
Dear Members; I have a problem. Recently we upgraded our Koha catalogue to version 3. During the course of editing, we have met a challenge at one point and we can nolonger proceed. Some records indicating no call number can not be searched and be found except when one generates the Report through "Items with no checkouts" that we can see the records. For example, the following record can not be edited after generating it through reports:
# 7082 No Call Number Barcode 7149
Title/ Auhor: Challenges and prospects for a new Nile water agreement : Ngʼwandu, Pius Yasebasi.
The information one gets is as follows:
An Error has Occurred! Error 404
* This error means that the link was broken and that the page doesn't exist * To report this error, you can email the Koha Administrator. * Use top menu bar to navigate to another part of Koha.
What do I do?
Simon J Engitu PArliament of Uganda
Examine your error logs for more information. You can try to rebuild your indexes from scratch. For example, using zebra: rebuild_zebra.pl -b -a -r Given your description, we would expect this to fail. So then check your zebra error logs. It sounds like you have encoding that is causing errors some record(s) to be impossible to parse. You may be able to determine more by viewing the biblioitems.marcxml field on the mysql command line. -- Joe Atzberger LibLime - Open Source Library Solutions
participants (2)
-
Joe Atzberger -
sengitu@parliament.go.ug