Bonjour Sinisa,
SM> The above could indicate some timeout problem.
SM> Can you build mysql --with-debug and start it with --debug and see in
SM> the trace file when are the above timeouts reported ??
SM> Also, do you have clients that do not call mysql_close at the end ,
SM> like PHP programs ?
No. I don't think so. Nothing queries the server. Each time I do a
'mysqladmin stat' I see only one more query which is the stat query
in fact.
I've just compiled with --with-debug and run the server with
--debug. I changed nothing else. Here is what happens now :
010320 17:09:44 mysqld started
Innobase: Started
/usr/local/mysql/libexec/mysqld: ready for connections
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
010320 17:10:30 mysqld restarted
Innobase: Started
/usr/local/mysql/libexec/mysqld: ready for connections
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
010320 17:13:02 mysqld restarted
Innobase: Database was not shut down normally.
Innobase: Starting recovery from log files...
Innobase: Starting log scan based on checkpoint at
Innobase: log sequence number 0 744725926
Innobase: Started
/usr/local/mysql/libexec/mysqld: ready for connections
I continue to investigate.
Regards,
Alex.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
