Hi All,
Ever since I upgraded msql-2.0.9 to 2.0.11, its
behavior has been quite moody. When I tried to access
it from the Web interface using a perl script, I often
got the follwoing error message in Apache server's
error_log:
Socket read on 6 for length failed : Bad file number
DBD::mSQL::st execute failed: MSQL server has gone
away at /ucmbordb/apache/perlscripts/list2.cgi line
124.
httpd: [Fri Oct 15 14:51:14 1999] [error] Statement
failed: MSQL server has gone away at
/ucmbordb/apache/perlscripts/list2.cgi line 125.
(note: the code referred in those two lines are
something like the following:
my $sth = $dbh->prepare($sql);
unless ($sth->execute) {
die "Statement failed: " . $sth->errstr;
}
All are standard calls to msql drivers)
After the upgrade, I re-installed
Msql-Mysql-modules-1.2202, so I suppose it's not
caused by a broken link between DBD and msql library.
Please also note that I have the same database in a
mysql server on the same machine. I have used the same
perl script (with necessary change of function calls
to database engine, of course) to access this database
and have not had any problems (i.e. the DBD::mysql
part of the module seems working fine).
Any idea on how to fix the problem?
Thanks a lot.
WL
=====
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
-------------------------------------------------------------------------
To unsubscribe, go to http://www.Hughes.com.au/extras/email/
This archive was generated by hypermail 2b30 : Mon Mar 04 2002 - 09:03:51 EST