Hello everybody. Everything was OK after clean installing of zenoss stack
2.2.3 on my RHAS5 server. But now I have the next problem. Maybe it began after
my tries to get work failed graphs and zenhub.
Code:
[EMAIL PROTECTED]:/root>/etc/init.d/zenoss-stack start
Starting mysqld.bin daemon with databases from /usr/local/zenoss/mysql/data
STOPPING server from pid file /usr/local/zenoss/mysql/data/nagios.pid
080812 16:22:02 mysqld ended
/usr/local/zenoss/mysql/scripts/ctl.sh : mysql could not be started
Daemon: zeoctl . . . daemon process started, pid=5752
Daemon: zopectl . . daemon process started, pid=6541
Please, help me! Zenoss has already collected 2700 devices! And I don't want
this large and useful db get lost:((. Zendisk worked for 10 days in order to
collect this!
P.S. This is /usr/local/zenoss/mysql/data/mysqld.log
Code:
;InnoDB: End of page dump
080812 16:22:02 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form
checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
080812 16:22:02InnoDB: Error: trying to access a stray pointer 0x36b0fff8
InnoDB: buf pool start is at 0xb6b04000, end at 0xb7304000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: how to force recovery.
080812 16:22:02InnoDB: Assertion failure in thread 3086173888 in file
../include/buf0buf.ic line 259
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
080812 16:22:02 - 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=0
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 =
217599 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=0xbfce66d8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81b9a61
0x839b39f
0x8331c88
0x833be18
0x82f5df2
0x82f4e73
0x82e5097
0x82e3329
0x826c766
0x8263202
0x81bc17c
0x81b9fee
0xad2dec
0x813cf01
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/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.
080812 16:22:02 mysqld ended
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=23577#23577
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
