Bug #26928 New value of fp=(nil) failed sanity check, terminating stack trace!
Submitted: 7 Mar 2007 18:17 Modified: 11 Mar 2007 18:49
Reporter: [ name withheld ] Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: General Severity:S2 (Serious)
Version: OS:Linux (Debian sarge)
Assigned to: CPU Architecture:Any

[7 Mar 2007 18:17] [ name withheld ]
Description:
Security Events
=-=-=-=-=-=-=-=
Mar  7 16:32:13 evolish mysqld[29848]: New value of fp=(nil) failed sanity check, terminating stack trace!

System Events
=-=-=-=-=-=-=
Mar  7 16:32:12 evolish mysqld[29848]: mysqld got signal 11;
Mar  7 16:32:13 evolish mysqld[29848]: This could be because you hit a bug. It is also possible that this binary
Mar  7 16:32:13 evolish mysqld[29848]: or one of the libraries it was linked against is corrupt, improperly built,
Mar  7 16:32:13 evolish mysqld[29848]: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar  7 16:32:13 evolish mysqld[29848]: We will try our best to scrape up some info that will hopefully help diagnose
Mar  7 16:32:13 evolish mysqld[29848]: the problem, but since we have already crashed, something is definitely wrong
Mar  7 16:32:13 evolish mysqld[29848]: and this may fail.
Mar  7 16:32:13 evolish mysqld[29848]:
Mar  7 16:32:13 evolish mysqld[29848]: key_buffer_size=16777216
Mar  7 16:32:13 evolish mysqld[29848]: read_buffer_size=131072
Mar  7 16:32:13 evolish mysqld[29848]: max_used_connections=42
Mar  7 16:32:13 evolish mysqld[29848]: max_connections=100
Mar  7 16:32:13 evolish mysqld[29848]: threads_connected=1
Mar  7 16:32:13 evolish mysqld[29848]: It is possible that mysqld could use up to
Mar  7 16:32:13 evolish mysqld[29848]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
Mar  7 16:32:13 evolish mysqld[29848]: bytes of memory
Mar  7 16:32:13 evolish mysqld[29848]: Hope that's ok; if not, decrease some variables in the equation.
Mar  7 16:32:13 evolish mysqld[29848]:
Mar  7 16:32:13 evolish mysqld[29848]: thd=0x46bf6800
Mar  7 16:32:13 evolish mysqld[29848]: Attempting backtrace. You can use the following information to find out
Mar  7 16:32:13 evolish mysqld[29848]: where mysqld died. If you see no messages after this, something went
Mar  7 16:32:13 evolish mysqld[29848]: terribly wrong...
Mar  7 16:32:13 evolish mysqld[29848]: Cannot determine thread, fp=0x46c3f56c, backtrace may not be correct.
Mar  7 16:32:13 evolish mysqld[29848]: Stack range sanity check OK, backtrace follows:
Mar  7 16:32:13 evolish mysqld[29848]: 0x818935f
Mar  7 16:32:13 evolish mysqld[29848]: 0x4004faf8
Mar  7 16:32:13 evolish mysqld[29848]: (nil)
Mar  7 16:32:13 evolish mysqld[29848]: 0x819b1c0
Mar  7 16:32:13 evolish mysqld[29848]: 0x40049b63
Mar  7 16:32:13 evolish mysqld[29848]: 0x4025318a
Mar  7 16:32:13 evolish mysqld[29848]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow 
instructions on how to resolve the stack trace. Resolved
Mar  7 16:32:13 evolish mysqld[29848]: stack trace is much more helpful in diagnosing the problem, so please do
Mar  7 16:32:13 evolish mysqld[29848]: resolve it
Mar  7 16:32:13 evolish mysqld[29848]: Trying to get some variables.
Mar  7 16:32:13 evolish mysqld[29848]: Some pointers may be invalid and cause the dump to abort...
Mar  7 16:32:13 evolish mysqld[29848]: thd->query at (nil)  is invalid pointer
Mar  7 16:32:13 evolish mysqld[29848]: thd->thread_id=3900638
Mar  7 16:32:13 evolish mysqld[29848]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Mar  7 16:32:13 evolish mysqld[29848]: information that should help you find out what is causing the crash.
Mar  7 16:32:13 evolish mysqld_safe[3429]: Number of processes running now: 0
Mar  7 16:32:13 evolish mysqld_safe[3431]: restarted
Mar  7 16:32:13 evolish mysqld[3434]: 070307 16:32:13  InnoDB: Database was not shut down normally!
Mar  7 16:32:13 evolish mysqld[3434]: InnoDB: Starting crash recovery.
Mar  7 16:32:13 evolish mysqld[3434]: InnoDB: Reading tablespace information from the .ibd files...
Mar  7 16:32:13 evolish mysqld[3434]: InnoDB: Restoring possible half-written data pages from the doublewrite
Mar  7 16:32:13 evolish mysqld[3434]: InnoDB: buffer...
Mar  7 16:32:13 evolish mysqld[3434]: 070307 16:32:13  InnoDB: Starting log scan based on checkpoint at
Mar  7 16:32:13 evolish mysqld[3434]: InnoDB: log sequence number 0 43838.
Mar  7 16:32:13 evolish mysqld[3434]: InnoDB: Doing recovery: scanned up to log sequence number 0 43838
Mar  7 16:32:13 evolish mysqld[3434]: InnoDB: Last MySQL binlog file position 0 79, file name 
/var/log/mysql/mysql-bin.000009
Mar  7 16:32:13 evolish mysqld[3434]: 070307 16:32:13  InnoDB: Flushing modified pages from the buffer pool...
Mar  7 16:32:13 evolish mysqld[3434]: 070307 16:32:13  InnoDB: Started; log sequence number 0 43838
Mar  7 16:32:13 evolish mysqld[3434]: Version: '4.1.11-Debian_4sarge7-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 
3306  Source distribution

How to repeat:
dunno
[7 Mar 2007 18:46] Valeriy Kravchuk
Thank you for a problem report. Please, send your my.cnf file content and send the results of:

uname -a
free

What version of MySQL server do you use?
[7 Mar 2007 19:37] [ name withheld ]
>>> my.cnf:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "/var/lib/mysql/my.cnf" to set server-specific options or
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/english
skip-external-locking
#
# For compatibility to other Debian packages that still use
# libmysqlclient10 and libmysqlclient12.
old_passwords   = 1
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address            = 0.0.0.0
#
# * Fine Tuning
#
key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 128K
#
# * Query Cache Configuration
#
query_cache_limit       = 1048576
query_cache_size        = 16777216
query_cache_type        = 1
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log            = /var/log/mysql.log
#log            = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log-slow-queries       = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication.
#server-id              = 1
log-bin                 = /var/log/mysql/mysql-bin.log
# See /etc/mysql/debian-log-rotate.conf for the number of files kept.
max_binlog_size         = 104857600
#binlog-do-db           = include_database_name
#binlog-ignore-db       = include_database_name
#
# * BerkeleyDB
#
# According to an MySQL employee the use of BerkeleyDB is now discouraged
# and support for it will probably cease in the next versions.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# If you want to enable SSL support (recommended) read the manual or my
# HOWTO in /usr/share/doc/mysql-server/SSL-MINI-HOWTO.txt.gz
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

>>> free
             total       used       free     shared    buffers     cached
Mem:       3362012    3314944      47068          0       8520    2515096
-/+ buffers/cache:     791328    2570684
Swap:      8008392      53664    7954728

>>> uname
Linux evolish.be 2.6.8-022stab070.5-smp #1 SMP Tue Apr 4 22:44:57 MSD 2006 i686 GNU/Linux

>>> Version
mysql-server-4 4.1.11a-4sarge
[8 Mar 2007 9:15] Valeriy Kravchuk
Please, try to repeat with a newer version of MySQL server, 4.1.22, and inform about the results. It can be just a result of bug fixed long time ago.
[10 Mar 2007 22:57] [ name withheld ]
hm well, after the new debian update from php4-mysql it works fine
i dont install such software fro source im using apt-get :)
thanks for the fast help! good work!
regards
michael l.
[11 Mar 2007 18:49] Valeriy Kravchuk
Closed as not repeatable with recent versions(s) of MySQL 4.1.x.