|Date||Wed Jan 19 15:39:03 2011|
|Subject||[greenstone-users] Issues in using "The Depositor"|
I checked the error log and found the error message like this:
[Wed Jan 19 15:16:31 2011] [error] [client 127.0.0.1] Premature end of script headers: library.cgi, referer: http://localhost/greenstone/cgi-bin/library.cgi?e=p-00000-00---off-0--00-----0-10-0---0---0direct-10---4-------0-1l--10-en-50---20-home---0--1-00-0-0-01-1-0utfZz-8-00&a=depositor&p=select
I found the answer in our archive folder and copy that into http.conf file, but still it does not work for me.
ScriptAlias /greenstone/cgi-bin "C:/Greenstone/cgi-bin"
Alias /greenstone "C:/Greenstone"
And also I download 2.83-windows-library.cgi<http://wiki.greenstone.org/wiki/gsdoc/patches/2.83-windows-library.cgi> and 2.83-windows-oaiserver.cgi<http://wiki.greenstone.org/wiki/gsdoc/patches/2.83-windows-oaiserver.cgi> and copy into cgi-bin folder. But still the same error message comes out. There is note about using Depositor saying
"You might need to set permissions for the GSDLHOME/tmp and GSDLHOME/collect or GSDLHOME/collect/your_accessable_collection directory." Does anyone know how to set up this permission? And also I use Window7, is it the main concern? Does anyone encounter this problem? Your suggestions are very appreciated.
From: Michael Silver [mailto:email@example.com] On Behalf Of Michael Silver
I'm sure there are others on the list that may have more specific recommendations, but here's what I would do.
1) Look at your Apache config in (usually) httpd.conf. It may "work", but it hasn't been truly set up correctly, IMHO. A server should provide a meaningful email address for contact. At bare minimum, the email address "firstname.lastname@example.org"<mailto:email@example.com> should be replaced with an actual email address so users have someone to contact if problems crop up. This may indicate that certain defaults have been left in the system that are interfering with Greenstone functioning correctly. Of course, that will be easier to locate once you find out what's gone wrong, so ...
2) Look at the error logs. The http.conf file may overwrite where they exist, but generally you can get there from /etc/httpd/logs/. My guesses would be a permission error (httpd user not allowed to read or write in a folder) or a location error. By location, I mean anything that will give a file or directory not found error. This could be a case difference (e.g., folder is named Greenstone instead of greenstone) or a simple location difference (the files are in a different directory location altogether). Finding the error in the logs will save a whole whack of guesswork.
Hope this helps...
On 18/01/2011 2:02 PM, Cathy Chang wrote:
greenstone-users mailing list