I increased net_read_timeout and net_write_timout up to 300 sec, but problem still exists.
My queries are executing only in few seconds, but sometimes mysql shows "Can't connect to server, or Connection lost etc."
I used mysql-4.0.14 server and client, but problem was same and I upgraded to mysql-4.0.15.
Probably running mysql in Windows is not great as in Lunux/FreeBSD. It seems like it is better to switch into
Linux/FreeBSD.
Ganbold
At 07:44 PM 9/25/2003 -0300, you wrote:
At 12:33 25/9/2003 +0900, Ganbold wrote: Hi,
I installed mysql-4.0.15 in Windows 2000 Advanced server. Mysql-max-nt is working fine, except some problems.
Sometimes when I try to use access web pages through php pages, mysql says "Connection to server lost" or
"Can't connect to mysql server" or sometimes query error. Query is tested and works fine most of the time.
And when I refresh web page again everything works fine.
Mysql log says nothing.
Is it problem related to mysql in Windows? Also I tested small C program to query mysql tables and it sometimes
hangs. Is there any solution for this kind of problem?
From the mysql.exe client:
(C) Copyright 1985-2000 Microsoft Corp.
c:\>c:\mysql\bin\mysql -uroot -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 4.0.15-max-nt-log
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> show variables like "%timeout%"; +--------------------------+-------+ | Variable_name | Value | +--------------------------+-------+ | connect_timeout | 5 | | delayed_insert_timeout | 300 | | innodb_lock_wait_timeout | 50 | | interactive_timeout | 28800 | | net_read_timeout | 30 | | net_write_timeout | 60 | | slave_net_timeout | 3600 | | wait_timeout | 28800 | +--------------------------+-------+ 8 rows in set (0.01 sec)
You can see above the net_read_timeout and net_write_timeout, if you are having queries that takes more than 30 seconds the server disconnect the client because the client remains passive and that time exceeds the net_read_timeout.
From 4.0.15 was introduced for socket time outs that before on Windows didn't worked.
So try to configure your server starting it with a more high value than the default according with the necessities.
However, when retrieved with a client 4.0.15 the above don't works, please read:
http://bugs.mysql.com/bug.php?id=1370
for further details and follow up.
-- Regards,
For technical support contracts, visit https://order.mysql.com/ Are you MySQL certified?, http://www.mysql.com/certification/
Miguel Angel Solórzano <[EMAIL PROTECTED]> Săo Paulo - Brazil
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
