I just set up a slave server and it seemed to be working alright, catching up with the new data, and then the server suddenly went away. Looking at the slave's data directory, there are approximately 20000 relay-bin files. I can't even restart the server now, because it gets a signal 11 immediately. Most of the relay-bin files have nothing in them, but the ones that do have data give me something like this:
[EMAIL PROTECTED] data]# mysqlbinlog stout-relay-bin.1588
# at 4
#700101 0:00:00 server id 3 log_pos 0 Rotate to kazoo-binlog.020 pos: 560177478
ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 302717, event_type: 2
ERROR: Could not read entry at offset 47 : Error in log format or read error
[EMAIL PROTECTED] data]#
I'm not even sure where to start here...I figure I'm going to have to get a fresh copy of all the data from the master, but it's about 350 gigs so that will take a while. Meanwhile I'm trying to figure out how to make this not happen again...
Here's a bit from my .err file:
030929 15:28:29 mysqld started
030929 15:28:30 InnoDB: Started
030929 15:28:30 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306
030929 19:39:59 mysqld started
030929 19:40:00 InnoDB: Started
030929 19:40:00 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.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=268435456
read_buffer_size=2093056
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1187439 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x885ff10
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=0x41f08b78, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80dbe1f
0x40037f75
0x420828fc
0x8351165
0x8350f93
0x8350f54
0x8350f54
0x8350f54
0x8350f54
0x8351b6f
0x83711b9
0x837118d
0x83711c9
0x837118d
0x83711c9
0x837118d
0x837118d
0x83711c9
0x837118d
0x83709b9
0x83520fa
0x8351ed5
0x83508df
0x8136669
0x81108b8
0x814d74c
0x814cf7c
0x80e9363
0x80ea88b
0x80e5ed3
0x80ebe0e
0x80e50bf
0x40034fef
0x420e779a
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8870968 = load data local infile '/db2/data/tmp/FcstHr_ece.txt' replace into table FcstHr_ece
thd->thread_id=49
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
031001 00:57:10 mysqld restarted
031001 0:57:11 InnoDB: Started
031001 0:57:11 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.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=268435456
read_buffer_size=2093056
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1187439 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x88323e8
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=0x41ed7b48, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80dbe1f
0x40037f75
0x420828fc
0x8351165
0x8350f93
0x8350f54
0x8350f54
0x8350f54
0x8350f54
0x8351b6f
0x83711b9
0x837118d
0x837118d
0x837118d
0x837118d
0x83711c9
0x83711c9
0x83711c9
0x837118d
0x837118d
0x83709b9
0x83520fa
0x8351ed5
0x83508df
0x8136669
0x81108b8
0x814d74c
0x814cf7c
0x80e9363
0x80ea88b
0x80e5ed3
0x80ebe0e
0x80e50bf
0x40034fef
0x420e779a
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x88674c8 = load data local infile '/db2/data/tmp/FcstHr_ece.txt' replace into table FcstHr_ece
thd->thread_id=68
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
031001 03:05:18 mysqld restarted
031001 3:05:20 InnoDB: Started
031001 3:05:20 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.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=268435456
read_buffer_size=2093056
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1187439 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x885a0c8
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=0x41ed7b48, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80dbe1f
0x40037f75
0x420828fc
0x8351165
0x8350f93
0x8350f54
0x8350f54
0x8350f54
0x8350f54
0x8351b6f
0x83711b9
0x837118d
0x837118d
0x837118d
0x837118d
0x83711c9
0x83711c9
0x83711c9
0x837118d
0x837118d
0x83709b9
0x83520fa
0x8351ed5
0x83508df
0x8136669
0x81108b8
0x814d74c
0x814cf7c
0x80e9363
0x80ea88b
0x80e5ed3
0x80ebe0e
0x80e50bf
0x40034fef
0x420e779a
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8830210 = load data local infile '/db2/data/tmp/FcstHr_ece.txt' replace into table FcstHr_ece
thd->thread_id=31
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
031001 03:21:04 mysqld restarted
031001 3:21:05 InnoDB: Started
031001 3:21:05 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306
031001 3:30:21 /usr/sbin/mysqld-max: Normal shutdown
031001 3:30:21 InnoDB: Starting shutdown... 031001 3:30:23 InnoDB: Shutdown completed 031001 3:30:23 /usr/sbin/mysqld-max: Shutdown Complete
031001 03:30:23 mysqld ended
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
