mysql crash when opening a connection
Hi, I have installed mysql 4.0.18 on my debian box. I am quite new to linux. mysql works fine with the command line (mysql) and with apache/phpmyadmin too. But when i try to connect from Windows or if i telnet from Debian, i got: Number of processes running now: 0 040622 21:27:33 mysqld restarted Warning: Ignoring user change to 'mysql' because the user was set to 'mysql' earlier on the command line /usr/sbin/mysqld: ready for connections. Version: '4.0.18-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbfffc4d8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x810f50b 0x40176825 0x40022e15 0x400221a2 0x400213ee 0x40021297 0x88d 0x811059d 0x40292dc6 0x80c12f1 New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 040622 21:27:59 mysqld restarted Warning: Ignoring user change to 'mysql' because the user was set to 'mysql' earlier on the command line /usr/sbin/mysqld: ready for connections. Version: '4.0.18-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Créez gratuitement votre Yahoo! Mail avec 100 Mo de stockage ! Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem: Communication Link Failure
I have a web application that uses ConnectorJ to connect to a MySQL database. When I had MySQL on windows, I never had a problem. However, now that I'm running MySQL on a linux box, I get a weird problem: If I have not logged in to MySQL through the mysql command-line utility in a while, the web application cannot connect to the database. When it tries to connect through JDBC, it comes back with a communication link error. This continues until I log in (through a bash prompt) with the mysql command-line utility. Then the web app can suddenly get through. Does anyone know why this is? What might be causing this? How can I stop this from happening? I'm not 100% sure, but I think what might be happening is this: 1. Connection Pool Manager creates connection and returns it 2. Connection is used by app, close() called and is returned to pool 3. Connection not used for long time, mysql times it out 4. Pool manager doesn't know it's timed out, returns it when connection asked for Does this sound correct? If this is the problem, how would I fix this? Unfortunately, the javax.sql.PooledConnection and Listener interfaces don't offer any callbacks for timeouts. So how would I timeout a connection? Or should I, before returning a pooled connection, test it first? The only thing is this adds an extra trip to the DB for every time someone asks for a connection. But I don't see any other way to handle this, except maybe the timeout on a connection in the "idle" pool? _ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail - 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
