Re: mysterious "can't connect" error message in our logs(2)

2004-03-25 Thread Sinisa Milivojevic
Sasha Pachev writes: > Jigal van Hemert wrote: > > It's a bug. I would recommend to patch libmysql.c for now until MySQL developers > fix it. > > -- > Sasha Pachev > Create online surveys at http://www.surveyz.com/ > Our client side uses select() but only when waiting for data, and not on teh

Re: mysterious "can't connect" error message in our logs(2)

2004-03-24 Thread Sasha Pachev
Jigal van Hemert wrote: The continuing saga: Can't connect to MySQL server on '192.168.13.205' (4) Our sysadmin has been searching in the sources of the MySQL client and came up with this: The errormessage (4) is probably (only place where this error could be found) raised by this fragment in

mysterious "can't connect" error message in our logs(2)

2004-03-22 Thread Jigal van Hemert
The continuing saga: > Can't connect to MySQL server on '192.168.13.205' (4) Our sysadmin has been searching in the sources of the MySQL client and came up with this: The errormessage (4) is probably (only place where this error could be found) raised by this fragment in libmysql.c: if ((soc

mysterious "can't connect" error message in our logs

2004-03-22 Thread Jigal van Hemert
Hi list, We recently installed a new MySQL server (Redhat 8, MySQL 4.0.18, same as old machine, but with more powerful hardware) and every now and then the following error appears in the errorlog (the result of the mysql_error() function of PHP): Can't connect to MySQL server on '192.168.13.20