- 论坛徽章:
- 0
|
Number of processes running now: 0
080421 01:53:37 mysqld restarted
080421 1:53:37 InnoDB: Started; log sequence number 0 43665
080421 1:53:37 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mydb2-relay-bin' to avoid this problem.
080421 1:53:37 [ERROR] Failed to open the relay log './myweb1-relay-bin.000002' (relay_log_pos 9
080421 1:53:37 [ERROR] Could not find target log during relay log initialization
080421 1:53:37 [ERROR] Failed to initialize the master info structure
080421 1:53:37 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.26-standard' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
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=67104768
max_used_connections=1
max_connections=500
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3274796 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x89e4c00
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=0xbfe5e718, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a0a12
0x82fb4e8
0x80ec2af
0x80ec020
0x80ec77b
0x80ec5aa
0x80ecfc5
0x80df5da
0x8085f30
0x80822cd
0x80829b5
0x8068904
0x8069354
0x805e701
0x80ed5f5
0x80ed061
0x80ecfd0
0x80df5da
0x80e261e
0x80dea51
0x80b2975
0x80b944a
0x80b0e54
0x80b06f3
0x80afc84
0x82f8c9c
0x83412ea
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8a04c60 = select jid,ctmid,coid,divid,cjname,ejname,cocname,coename,issuedate, validdate, refreshdate,jarea,jnum,providesalary,industrytype1,industrytype2,functype1,functype2,sex,agefrom,ageto,workyear,degreefrom,fl1,fl2,jemail,postchannel,term,status,isreq,is51j,isother,isurgency,jorder,isjump,jumpurl,showmethod,cvlanguage,autoreply,msgdetail,issendemail, flevel1,flevel2,companytype,companysize, poscode, updatedate, cjinfo, ejinfo,workarea,isopen, syncdate from js where jid=36059774-2 and 0<(select count(schema_name) from information_schema.schemata where schema_name = 0x65 and schema_name <> 0x696e666f726d6174696f6e5f736368656d61)
thd->thread_id=215
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
080421 01:54:11 mysqld restarted
080421 1:54:11 InnoDB: Started; log sequence number 0 43665
080421 1:54:11 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mydb2-relay-bin' to avoid this problem.
080421 1:54:11 [ERROR] Failed to open the relay log './myweb1-relay-bin.000002' (relay_log_pos 9
080421 1:54:11 [ERROR] Could not find target log during relay log initialization
080421 1:54:11 [ERROR] Failed to initialize the master info structure
080421 1:54:11 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.26-standard' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
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=67104768
max_used_connections=2
max_connections=500
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3274796 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x89e4c00
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=0xbfe5e718, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a0a12
0x82fb4e8
0x80ec2af
0x80ec020
0x80ec77b
0x80ec5aa
0x80ecfc5
0x80df5da
0x8085f30
0x80822cd
0x80829b5
0x8068904
0x8069354
0x805e701
0x80ed5f5
0x80ed061
0x80ecfd0
0x80df5da
0x80e261e
0x80dea51
0x80b2975
0x80b944a
0x80b0e54
0x80b06f3
0x80afc84
0x82f8c9c
0x83412ea
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8a04c60 = select jid,ctmid,coid,divid,cjname,ejname,cocname,coename,issuedate, validdate, refreshdate,jarea,jnum,providesalary,industrytype1,industrytype2,functype1,functype2,sex,agefrom,ageto,workyear,degreefrom,fl1,fl2,jemail,postchannel,term,status,isreq,is51j,isother,isurgency,jorder,isjump,jumpurl,showmethod,cvlanguage,autoreply,msgdetail,issendemail, flevel1,flevel2,companytype,companysize, poscode, updatedate, cjinfo, ejinfo,workarea,isopen, syncdate from js where jid=36059774-2 and 0<(select count(schema_name) from information_schema.schemata where schema_name = 0x6b and schema_name <> 0x696e666f726d6174696f6e5f736368656d61)
thd->thread_id=475
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. |
|
免费注册
发表于 2008-04-22 10:28
发表于 2008-04-22 11:36
