I seem to recall in the past that there was a nice little walk through provided by someone on how to get koha working with a multi part call number (using the k, h, and i) subfields, but, I can not seem to find that information anywhere in the archives or linked from the howto's. Anyone able to point me in the correct direction or give some pointers on how to keep the three separate subfields and also have koha display them as a single call number? Tim
I've installed Koha 2.2.5 on a Debian Sarge build and after adding the "Include /ect/koha-httpd.conf" to apache's http.conf file the webserver stops running or answering on ports 80 and 8080. Below is my koha-httpd.conf files. Any thoughts why ? Thanks Chris Borkowski Guggenheim Museum # Ports to listen to for Koha # uncomment these if they aren't already in main httpd.conf # Listen 8080 # NameVirtualHost is used by one of the optional configurations detailed below # Please make sure this line is correct before uncommenting. # See http://httpd.apache.org/docs/vhosts/ for some guides. # KOHA's OPAC Configuration <VirtualHost opac1:80> ServerAdmin cborkowski@guggenheim.org DocumentRoot /usr/local/koha/opac/htdocs ServerName opac1 ScriptAlias /cgi-bin/koha/ /usr/local/koha/opac/cgi-bin/ Redirect permanent index.html http://opac1:80/cgi-bin/koha/opac-main.pl ErrorLog /usr/local/koha/log/opac-error_log TransferLog /usr/local/koha/log/opac-access_log # SetEnv PERL5LIB "/usr/local/koha/intranet/modules" # SetEnv KOHA_CONF "/etc/koha.conf" SetEnvIf Request_URI "\.pls" PERL5LIB "/usr/local/koha/intranet/modules" SetEnvIf Request_URI "\.pls" KOHA_CONF "/etc/koha.conf" </VirtualHost> # KOHA's INTRANET Configuration <VirtualHost opac1:8080> ServerAdmin cborkowski@guggenheim.org DocumentRoot /usr/local/koha/intranet/htdocs ServerName opac1 ScriptAlias /cgi-bin/koha/ "/usr/local/koha/intranet/cgi-bin/" Redirect permanent index.html http://opac1:8080/cgi-bin/koha/mainpage.pl ErrorLog /usr/local/koha/log/koha-error_log TransferLog /usr/local/koha/log/koha-access_log # SetEnv PERL5LIB "/usr/local/koha/intranet/modules" # SetEnv KOHA_CONF "/etc/koha.conf" SetEnvIf Request_URI "\.pls" PERL5LIB "/usr/local/koha/intranet/modules" SetEnvIf Request_URI "\.pls" KOHA_CONF "/etc/koha.conf" </VirtualHost>
Christopher Borkowski <cborkowski@guggenheim.org>
I've installed Koha 2.2.5 on a Debian Sarge build and after adding the "Include /ect/koha-httpd.conf" to apache's http.conf file the webserver stops running or answering on ports 80 and 8080. Below is my koha-httpd.conf files.
Any thoughts why ?
Apache should tell you why in its error.log or on the stderr when you try to start it again. Post that and someone might know. You did mean etc not ect, didn't you? Good luck, -- MJ Ray - personal email, see http://mjr.towers.org.uk/email.html Work: http://www.ttllp.co.uk/ irc.oftc.net/slef Jabber/SIP ask
Thanks MJ - and yes I meant /etc Heres the log output: [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 [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 Apache will start sometimes after the include directive is put in httpd.conf other times it won't ? I guess this looks like it can find or execute the koha scritps? Permissions ? Path issue ? I'll double check On 5/11/06 2:27 AM, "MJ Ray" <mjr@phonecoop.coop> wrote:
Christopher Borkowski <cborkowski@guggenheim.org>
I've installed Koha 2.2.5 on a Debian Sarge build and after adding the "Include /ect/koha-httpd.conf" to apache's http.conf file the webserver stops running or answering on ports 80 and 8080. Below is my koha-httpd.conf files.
Any thoughts why ?
Apache should tell you why in its error.log or on the stderr when you try to start it again. Post that and someone might know.
You did mean etc not ect, didn't you?
Good luck,
I've just installed Koha 2.2.5 and a Debina Sarge build and when the page loads I get this error Can't locate C4/Database.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.4 /$ [Thu May 11 11:02:19 2006] [error] [client 192.168.1.103] BEGIN failed--compilation aborted at /usr/local/koha/intranet/cgi-bin/mainpage.pl line 5.$ [Thu May 11 11:02:19 2006] [error] [client 192.168.1.103] Premature end of script headers: mainpage.pl, referer: http://opac1.guggenheim.org:8080/ Any ideas on how fix this ? Thanks Chris Borkowski Guggenheim Museum
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. -- MJ Ray - personal email, see http://mjr.towers.org.uk/email.html Work: http://www.ttllp.co.uk/ irc.oftc.net/slef Jabber/SIP ask
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.
participants (3)
-
Christopher Borkowski -
Krieger, Tim -
MJ Ray