I've managed to work this issue out. Thanks for your help. The solution was to have a FULLY QUALIFED DOMAIN NAME for your virtual host in you koha-httpd.conf file. I was using an abbreviated host name in hopes of our windows domain controllers resolving the name, in most cases this works out fine but not with the koha virtual host include to apache. For example I can set up most serves behind our firewall by creating a DNS record on the DC and in the host configiuration with the host name set to: example And it will resolve out to: example.domain.org. For some reason koha and debian/apache seems to prefer the fully qualified domain name in the koha-httpd.conf file . Thanks again for your help. Best Chris Borkowski Guggenheim Museum On 5/13/06 2:27 AM, "MJ Ray" <mjr@phonecoop.coop> wrote:
Christopher Borkowski <cborkowski@guggenheim.org>
[Wed May 10 15:35:16 2006] [error] [client 192.168.1.68] script not found or unable to stat: /usr/lib/cgi-bin/koha
We may need to return to this.
[Wed May 10 15:35:50 2006] [notice] SIGHUP received. Attempting to restart (98)Address already in use: make_sock: could not bind to address 0.0.0.0:8080 no listening sockets available, shutting down Unable to open logs
Maybe Listen 8080 or similar is already in httpd.conf and having it in there a second time breaks something? It would surprise me.
Apache will start sometimes after the include directive is put in httpd.conf other times it won't ?
This suggests that Apache maybe not restarting quickly enough and Apache tries to start again before it has stopped. Does it always start correctly with /etc/init.d/apache stop && sleep 1 && /etc/init.d/apache start ?
I guess this looks like it can find or execute the koha scritps? Permissions ? Path issue ? I'll double check
Thank you. Check everything, take notes and slowly change things until it works. Standard engineering, but very irritating.