Mysql crashing
Posted: Mon Dec 17, 2007 5:29 am
I have discovered that when I click on an event from the console page in the hour column I get this message in the spawning window:
"Lost connection to MySQL server during query"
if I go to the events column and select the very same event it works fine.
and these started popping up in messages
zms[17845]: ERR [Got signal (Segmentation fault), crashing]
Anyone seen an error like this before? The system has been working pretty well until this.
error from mysql log.
071216 21:18:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.45' socket: '/var/lib/mysql/mysql.sock' port: 3306 SUSE MySQL RPM
071216 21:19:48 - 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=258048
max_used_connections=3
max_connections=100
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x221ebf0
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=0x4410afe0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x221ebf0 failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using ... 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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x2224d60 = select E.* from Events as E inner join Monitors as M on E.MonitorId = M.Id where E.StartTime <= '2007-12-16 20:22:59' and ( E.MonitorId = 2 and E.Archived = 0 and E.StartTime >= '2007-12-16 20:19:48' ) order by E.StartTime desc
thd->thread_id=5
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
071216 21:19:48 mysqld restarted
071216 21:19:49 InnoDB: Started; log sequence number 0 43655
071216 21:19:49 [Note] /usr/sbin/mysqld: ready for connections.
"Lost connection to MySQL server during query"
if I go to the events column and select the very same event it works fine.
and these started popping up in messages
zms[17845]: ERR [Got signal (Segmentation fault), crashing]
Anyone seen an error like this before? The system has been working pretty well until this.
error from mysql log.
071216 21:18:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.45' socket: '/var/lib/mysql/mysql.sock' port: 3306 SUSE MySQL RPM
071216 21:19:48 - 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=258048
max_used_connections=3
max_connections=100
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x221ebf0
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=0x4410afe0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x221ebf0 failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using ... 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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x2224d60 = select E.* from Events as E inner join Monitors as M on E.MonitorId = M.Id where E.StartTime <= '2007-12-16 20:22:59' and ( E.MonitorId = 2 and E.Archived = 0 and E.StartTime >= '2007-12-16 20:19:48' ) order by E.StartTime desc
thd->thread_id=5
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
071216 21:19:48 mysqld restarted
071216 21:19:49 InnoDB: Started; log sequence number 0 43655
071216 21:19:49 [Note] /usr/sbin/mysqld: ready for connections.