RE: [Koha-devel] log about z3950
As far as I know, you have to start the z3950 daemon manually (I use "z3950-daemon-launch.sh" to start it). A "ps -ef | grep z3950" should show if it's running. When you press the z3950 search button, it starts a process that communicates with the z3950 daemon, but it doesn't start the daemon. Deric -----Original Message----- From: Benedykt P. Barszcz [mailto:kb2qzv@poczta.wp.pl] Sent: 26 February, 2004 13:10 To: Sullivan,Deric [CMC] Cc: 'koha-devel@lists.sourceforge.net' Subject: RE: [Koha-devel] log about z3950 W liście z czw, 26-02-2004, godz. 18:48, Sullivan,Deric [CMC] pisze:
Hi Benedict,
Is your processz3950queue process running and is it started with z3950-daemon-launch.sh?
Deric I am not ware of it being started by me personally. I just hope koha installation took care of it. Doesn't it happen when I press the z3950search button?
Benedict
I get this: [root@localhost z3950daemon]# ps -ef | grep z39 root 16167 1 0 19:10 pts/1 00:00:00 su -s /bin/sh -c /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-shell.sh - apache apache 16168 16167 0 19:10 pts/1 00:00:04 /usr/bin/perl /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue /usr/local/koha/log apache 16202 16168 0 19:10 pts/1 00:00:00 [processz3950que <defunct>] apache 16208 16168 0 19:10 pts/1 00:00:00 [processz3950que <defunct>] apache 16209 16168 0 19:10 pts/1 00:00:00 [processz3950que <defunct>] apache 16210 16168 0 19:10 pts/1 00:00:00 [processz3950que <defunct>] root 16287 1 0 19:34 pts/1 00:00:00 su -s /bin/sh -c /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-shell.sh - apache apache 16288 16287 1 19:34 pts/1 00:00:02 /usr/bin/perl /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue /usr/local/koha/log root 16364 3081 0 19:37 pts/1 00:00:00 grep z39 [root@localhost z3950daemon]# Benedict What should the parameters be for the daemon? I mean host, password, port, name of db, etc?
Benedykt P. Barszcz wrote:
Benedict What should the parameters be for the daemon? I mean host, password, port, name of db, etc?
2 tips : * for DEBUGGING purposes, launch processz3950queue in a console. You'll see "starting loop" every 5 seconds, and other things when you launch a z3950 request. * use export PERL5LIB=/path/to/koha and export KOHA_CONF=/path/to/koha.conf before launching it. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
Here is what I get after launching processz3950queue. Before that I exported PERL5LIB to /usr/local/koha/intranet/modules and KOHA_CONF to /etc/koha.conf [root@localhost z3950daemon]# ./processz3950queue starting loop 3221/13 : Processing isbn=0-385-24767-2 at Library of Congress z3950.loc.gov:7090 voyager MARC21 (1 forks) 3222/14 : Processing isbn=83-01-02448-8 at Library of Congress z3950.loc.gov:7090 voyager MARC21 (2 forks) 3223/15 : Processing isbn=83-01-02448-8 at Library of Congress z3950.loc.gov:7090 voyager MARC21 (3 forks) 3222/14 : 2 >> 3222/14 : creating and 3222/14 : working on results entry 11 DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 232. 3223/15 : 2 >> 3222/14 : connected to Library of Congress 3223/15 : creating and 3223/15 : working on results entry 0 DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 232. 3221/13 : 2 >> 3223/15 : connected to Library of Congress 3223/15 : Library of Congress : no records found 3222/14 : Library of Congress : no records found 3221/13 : creating and 3221/13 : working on results entry 0 3222/14 : z3950.loc.gov:7090 search done. DBD::mysql::st execute failed: Lost connection to MySQL server during query at ./processz3950queue line 246. 3221/13 : connected to Library of Congress DBD::mysql::st execute failed: Lost connection to MySQL server during query at ./processz3950queue line 306. 3223/15 : z3950.loc.gov:7090 search done. 3221/13 : Library of Congress : no records found DBD::mysql::db selectrow_array failed: MySQL server has gone away at /usr/local/koha/intranet/modules/C4/Context.pm line 320. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 302. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 306. 3221/13 : z3950.loc.gov:7090 search done. starting loop DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 139. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 144. DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 145. starting loop DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 136. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 139. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 144. DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 145. starting loop DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 136. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 139. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 144. DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 145. starting loop DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 136. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 139. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 144. DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 145. starting loop DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 136. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 139. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 144. DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 145.
Benedykt P. Barszcz wrote:
Here is what I get after launching processz3950queue. Before that I exported PERL5LIB to /usr/local/koha/intranet/modules and KOHA_CONF to /etc/koha.conf
ok, do you update your CVS 10mn ago ? I just commit some things. what's your perl version ? and your /etc/my.cnf file ? (see previous mails in the ml) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
This is even more informative. I am using Fedora Core 1. [root@localhost z3950daemon]# perl -V Summary of my perl5 (revision 5.0 version 8 subversion 1) configuration: Name : mysql Relocations: (not relocateable) Version : 3.23.58 Vendor: Red Hat, Inc. 3351/16 : Processing isbn=83-01-02448-8 at Library of Congress z3950.loc.gov:7090 voyager MARC21 (1 forks) 3351/16 : 2 >> 3351/16 : creating and 3351/16 : working on results entry 14 3351/16 : connected to Library of Congress 3351/16 : Library of Congress : no records found 3351/16 : z3950.loc.gov:7090 search done. starting loop DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 144. DBD::mysql::st execute failed: MySQL server has gone away at ./processz3950queue line 149. DBD::mysql::st fetchrow failed: fetch() without execute() at ./processz3950queue line 150. starting loop
cat /etc/my.cnf [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock skip-innodb set-variable = key_buffer=32M set-variable = max_allowed_packet=1M set-variable = table_cache=256 set-variable = sort_buffer=4M set-variable = record_buffer=1M set-variable = myisam_sort_buffer_size=16M set-variable = thread_cache=8 [mysql.server] user=mysql port=3306 basedir=/var/lib [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid [root@localhost z3950daemon]#
participants (3)
-
Benedykt P. Barszcz -
paul POULAIN -
Sullivan,Deric [CMC]