I recently installed koha sucessfully on debian etch 4.0. However, I was unable to start the mysql service and restart apache. I tried starting the Mysql service using: mysql start command But the dollowing error was obtained: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) When i tried restarting Apache I got the following error: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Fri Sep 14 16:44:06 2007] [warn] NameVirtualHost *:8080 has no VirtualHosts [Fri Sep 14 16:44:06 2007] [warn] NameVirtualHost *:80 has no VirtualHosts. We have the following settings for our httpd.conf file: # Koha 2.2 Apache Virtual Host Config File # # Please include this file in your apache configuration. # The best way to do that depends on your site setup. # Some like an Include adding to /etc/apache/httpd.conf # and some prefer a symlink to this file from some dir. # Please refer to your system manuals. # 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. NameVirtualHost *:80 # KOHA's OPAC Configuration <VirtualHost *:80> ServerAdmin user@domain.edu DocumentRoot /usr/local/koha/opac/htdocs ServerName debian ScriptAlias /cgi-bin/koha/ /usr/local/koha/opac/cgi-bin/ Redirect permanent index.html http://opac.ugcsi.edu/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" </VirtualHost> # KOHA's INTRANET Configuration NameVirtualHost *:8080 <VirtualHost *:8080> ServerAdmin user@domain.edu DocumentRoot /usr/local/koha/intranet/htdocs ServerName debian ScriptAlias /cgi-bin/koha/ "/usr/local/koha/intranet/cgi-bin/" Redirect permanent index.html http://intranet.ugcsi.edu: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" </VirtualHost> # If you want to use name based Virtual Hosting: # 1. remove the two Listen lines # 2. replace koha:80 with your.opac.domain.name # 3. replace ServerName koha with ServerName your.opac.domain.name # 4. replace koha:8080 with your intranet domain name # 5. replace ServerName koha with ServerName your.intranet.domain.name # # If you want to use NameVirtualHost'ing (using two names on one ip address): # 1. Follow steps 1-5 above # 2. Uncomment the NameVirtualHost line and set the correct ip address Our ServerName debian is actually the host name of the computer that's running Debian AND ugcsi.edu is our domain name. Any thoughts? Would greatly appreciate your input. Penelope DeFreitas ____________________________________________________________________________________ Got a little couch potato? Check out fun summer activities for kids. http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
penelope defreitas wrote:
I recently installed koha sucessfully on debian etch 4.0.
Hi Penelope ... we've done the same on Debian Etch with great success :)
However, I was unable to start the mysql service and restart apache.
I tried starting the Mysql service using:
mysql start command
You start and stop mysql on Debian as follows: sudo /etc/init.d/mysql start and sudo /etc/init.d/mysql stop Note that "mysql" is the mysql client and /etc/init.d/mysql is the control file for the mysql server.
When i tried restarting Apache I got the following error:
Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Fri Sep 14 16:44:06 2007] [warn] NameVirtualHost *:8080 has no VirtualHosts [Fri Sep 14 16:44:06 2007] [warn] NameVirtualHost *:80 has no VirtualHosts.
See my comments below ....
# KOHA's OPAC Configuration <VirtualHost *:80> ServerAdmin user@domain.edu
ServerAdmin should designate a valid email address. EXAMPLE ServerAdmin penelopedefreitas@yahoo.com
DocumentRoot /usr/local/koha/opac/htdocs ServerName debian
ServerName should designate the fully-qualified domain name (FQDN) of your web server. EXAMPLE ServerName intranet.ugcsi.edu
ServerAdmin user@domain.edu ServerName debian
ditto for the above HTH! cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Traditionally, most of Australia's imports come from overseas. -- Keppel Enderbery
On 9/14/2007 at 10:06 PM, in message <46EB3017.6070007@praxis.com.au>, Rick Welykochy <rick@praxis.com.au> wrote:
Hi Rick, Did you ever have the issue of addbiblio.pl breaking and prompting your browser to "save the file"? I'm thinking is has something to do with the config of my 090 and 050 fields in the Koha config and the records I'm importing. Does this make any sense? F. Grant Johnson 566-0630 / fgjohnson@upei.ca Skype ID = jetsongeorge Systems/Web Coordinator Robertson Library University of Prince Edward Island *************** Attitude is IT! penelope defreitas wrote:
I recently installed koha sucessfully on debian etch 4.0.
Hi Penelope ... we've done the same on Debian Etch with great success :)
However, I was unable to start the mysql service and restart apache.
I tried starting the Mysql service using:
mysql start command
You start and stop mysql on Debian as follows: sudo /etc/init.d/mysql start and sudo /etc/init.d/mysql stop Note that "mysql" is the mysql client and /etc/init.d/mysql is the control file for the mysql server.
When i tried restarting Apache I got the following error:
Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Fri Sep 14 16:44:06 2007] [warn] NameVirtualHost *:8080 has no VirtualHosts [Fri Sep 14 16:44:06 2007] [warn] NameVirtualHost *:80 has no VirtualHosts.
See my comments below ....
# KOHA's OPAC Configuration <VirtualHost *:80> ServerAdmin user@domain.edu
ServerAdmin should designate a valid email address. EXAMPLE ServerAdmin penelopedefreitas@yahoo.com
DocumentRoot /usr/local/koha/opac/htdocs ServerName debian
ServerName should designate the fully-qualified domain name (FQDN) of your web server. EXAMPLE ServerName intranet.ugcsi.edu
ServerAdmin user@domain.edu ServerName debian
ditto for the above HTH! cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Traditionally, most of Australia's imports come from overseas. -- Keppel Enderbery _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Grant Johnson wrote:
Did you ever have the issue of addbiblio.pl breaking and prompting your browser to "save the file"?
Nope.
I'm thinking is has something to do with the config of my 090 and 050 fields in the Koha config and the records I'm importing. Does this make any sense?
The error you mention above has occurred many times. It is not for the reason you mention. It is much more basic than that. When a Perl script dies before the HTTP header has been output, the browser does not know that the content type is HTML ... so it attempts to download the script itself and save it to disk (!) When this happens, you of course want to see what the error is. The following always works for me: 1. find the file causing trouble, e.g. addbiblio.pl in your case 2. add the following line after the "use CGI" line: use CGI::Carp qw(fatalsToBrowser); Now, when any error occurs it will be displayed in your browser. Try the above and let the list know what error you have. We can then help you. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services When will governments realise that we do not want to live in economies, we want to live in societies. -- Les Twentyman
Since I'm fighting with the same problem: Rick Welykochy schrieb:
Grant Johnson wrote:
When this happens, you of course want to see what the error is.
The following always works for me:
1. find the file causing trouble, e.g. addbiblio.pl in your case
2. add the following line after the "use CGI" line:
use CGI::Carp qw(fatalsToBrowser);
Now, when any error occurs it will be displayed in your browser.
Try the above and let the list know what error you have.
Here it is: Arguments must be MARC::Field object at /usr/local/koha/intranet/modules/C4/Biblio.pm line 1440 Btw: Is there a way to _remove_ all perl-related stuff from my server (not only the packages I installed with apt-get, but also all the modules installed from CPAN) so I could try to start installing again? Greetings Beda
Beda Szukics wrote:
Rick Welykochy schrieb:
Grant Johnson wrote: When this happens, you of course want to see what the error is. The following always works for me: 1. find the file causing trouble, e.g. addbiblio.pl in your case 2. add the following line after the "use CGI" line: use CGI::Carp qw(fatalsToBrowser); Now, when any error occurs it will be displayed in your browser.
Try the above and let the list know what error you have.
Here it is: Arguments must be MARC::Field object at /usr/local/koha/intranet/modules/C4/Biblio.pm line 1440
Any MARC experts? I have no idea about the above error.
Btw: Is there a way to _remove_ all perl-related stuff from my server (not only the packages I installed with apt-get, but also all the modules installed from CPAN) so I could try to start installing again?
Other than a manual seek and destroy, I do not know if CPAN will help you deleting the modules. You can find out which modules have been installed and where they were installed by examining the install pod with perldoc: perldoc perllocal which produces the following (edited) output on my system: PERLLOCAL(1) User Contributed Perl Documentation PERLLOCAL(1) Mon Apr 9 14:26:35 2007: "Module" Event ? "installed into: /usr/local/share/perl/5.8.8" ? "VERSION: 1.08" Mon Apr 9 14:30:18 2007: "Module" MARC::Record ? "installed into: /usr/local/share/perl/5.8.8" ? "VERSION: 2.0" etc. If you find that only your Koha related modules are in /usr/local/share/perl/5.8.8 (or wherever), simply delete the entire directory and start again. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services When will governments realise that we do not want to live in economies, we want to live in societies. -- Les Twentyman
Rick Welykochy schrieb:
You can find out which modules have been installed and where they were installed by examining the install pod with perldoc:
perldoc perllocal
Strange. That gives me only (a little bit edited): verwaltung:~# perldoc perllocal PERLLOCAL(1) User Contributed Perl Documentation PERLLOCAL(1) Tue Oct 2 16:48:02 2007: "Module" Event · "installed into: /usr/local/share/perl/5.8.8" · "LINKTYPE: dynamic" · "VERSION: 1.09" · "EXE_FILES: " Tue Oct 2 16:48:59 2007: "Module" Test::Harness [shortened] Tue Oct 2 16:49:03 2007: "Module" ExtUtils::CBuilder [shortened] perl v5.8.8 2007-10-02 PERLLOCAL(1) But: verwaltung:~# ls /usr/local/share/perl/5.8.8/ shows: Archive/ Carp/ Digest/ IO/ PDF/ Text/ auto/ Class/ ExtUtils/ MARC/ Sub/ XML/ Barcode/ Compress/ File/ Module/ Term/ YAML/ Business/ Convert/ GD/ Net/ Test/ YAML.pm There are shurely more modules installed than the three mentioned above. I guess I have to try to start all over again :-( Thanks Beda
participants (4)
-
Beda Szukics -
Grant Johnson -
penelope defreitas -
Rick Welykochy