During a z3950 search, I find some servers respond with a not found message, and then I see stuff like: DBD::mysql::st execute failed: MySQL server has gone away at /home/vhosts/koha.no1.com.au/scripts/z3950daemon/processz3950queue line 142. DBD::mysql::st execute failed: MySQL server has gone away at /home/vhosts/koha.no1.com.au/scripts/z3950daemon/processz3950queue line 145. DBD::mysql::st execute failed: MySQL server has gone away at /home/vhosts/koha.no1.com.au/scripts/z3950daemon/processz3950queue line 150. DBD::mysql::st fetchrow failed: fetch() without execute() at /home/vhosts/koha.no1.com.au/scripts/z3950daemon/processz3950queue line 151. DBD::mysql::st execute failed: MySQL server has gone away at /home/vhosts/koha.no1.com.au/scripts/z3950daemon/processz3950queue line I notice that someone else has reported this problem, and the recommended solution was to increase a mysql timeout. I have tried increasing all mysql timeout values, but the problem still happens. Any advice appreciated Data from about page for version info: Koha version2.2.0 OS version ('uname -a')Linux retroroms.foreverchat.net 2.6.3-7mdk-p3-smp-64GB #1 SMP Wed Mar 17 15:34:39 CET 2004 i686 unknown unknown GNU/Linux Perl version5.008003 MySQL versionmysql Ver 12.22 Distrib 4.0.18, for mandrake-linux-gnu (i586) Apache versionServer version: Apache-AdvancedExtranetServer/2.0.48 Server built: Jun 28 2004 15:45:14
participants (1)
-
Greg Kuhnert