[root@vox01 mysql]# cat vox01.err 
051123 13:32:51  mysqld started
051123 13:32:51 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/ibJxVHMK' (Errcode: 13)
051123 13:32:51  InnoDB: Error: unable to create temporary file; errno: 13
051123 13:32:51 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
[root@vox01 mysql]# cat vox01.err 
051123 13:32:51  mysqld started
051123 13:32:51 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/ibJxVHMK' (Errcode: 13)
051123 13:32:51  InnoDB: Error: unable to create temporary file; errno: 13
051123 13:32:51 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/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=8388600
read_buffer_size=131072
max_used_connections=3
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 = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8a04008
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=0xbff3ead8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a13b7
0x82e77a8
0x8192a64
0x81427eb
0x8134414
0x815c088
0x815d15c
0x80e157b
0x80e28c9
0x80df251
0x80b32d0
0x80b9a9a
0x80b1843
0x80b1114
0x80b0634
0x82e4f5c
0x830e85a
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 0x8a99f08 = SHOW GLOBAL STATUS
thd->thread_id=56
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
051123 14:16:01  mysqld restarted
051123 14:16:01 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/ibOgJ7Sf' (Errcode: 13)
051123 14:16:01  InnoDB: Error: unable to create temporary file; errno: 13
051123 14:16:01 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/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=8388600
read_buffer_size=131072
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 = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x895a128
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=0xbff5ead8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a13b7
0x82e77a8
0x8192a64
0x81427eb
0x8134414
0x815c088
0x815d15c
0x80e157b
0x80e28c9
0x80df251
0x80b32d0
0x80b9a9a
0x80b1843
0x80b1114
0x80b0634
0x82e4f5c
0x830e85a
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 0x8986058 = SHOW GLOBAL STATUS
thd->thread_id=1
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
051123 14:16:06  mysqld restarted
051123 14:16:06 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/iboKiOi9' (Errcode: 13)
051123 14:16:06  InnoDB: Error: unable to create temporary file; errno: 13
051123 14:16:06 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/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=8388600
read_buffer_size=131072
max_used_connections=2
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 = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x895a128
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=0xbff5ead8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a13b7
0x82e77a8
0x8192a64
0x81427eb
0x8134414
0x815c088
0x815d15c
0x80e157b
0x80e28c9
0x80df251
0x80b32d0
0x80b9a9a
0x80b1843
0x80b1114
0x80b0634
0x82e4f5c
0x830e85a
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 0x8986058 = SHOW GLOBAL STATUS
thd->thread_id=1
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
051123 14:16:16  mysqld restarted
051123 14:16:16 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/ibyCYr24' (Errcode: 13)
051123 14:16:16  InnoDB: Error: unable to create temporary file; errno: 13
051123 14:16:16 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/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=8388600
read_buffer_size=131072
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 = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x895a128
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=0xbff5ead8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a13b7
0x82e77a8
0x8192a64
0x81427eb
0x8134414
0x815c088
0x815d15c
0x80e157b
0x80e28c9
0x80df251
0x80b32d0
0x80b9a9a
0x80b1843
0x80b1114
0x80b0634
0x82e4f5c
0x830e85a
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 0x8986058 = SHOW GLOBAL STATUS
thd->thread_id=1
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
051123 14:16:19  mysqld restarted
051123 14:16:19 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/ibEH6dcC' (Errcode: 13)
051123 14:16:19  InnoDB: Error: unable to create temporary file; errno: 13
051123 14:16:19 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/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=8388600
read_buffer_size=131072
max_used_connections=2
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 = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x895a128
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=0xbff5ead8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a13b7
0x82e77a8
0x8192a64
0x81427eb
0x8134414
0x815c088
0x815d15c
0x80e157b
0x80e28c9
0x80df251
0x80b32d0
0x80b9a9a
0x80b1843
0x80b1114
0x80b0634
0x82e4f5c
0x830e85a
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 0x8986058 = SHOW GLOBAL STATUS
thd->thread_id=1
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
051123 14:16:29  mysqld restarted
051123 14:16:29 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/ibEah9UI' (Errcode: 13)
051123 14:16:29  InnoDB: Error: unable to create temporary file; errno: 13
051123 14:16:29 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/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=8388600
read_buffer_size=131072
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 = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x895a128
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=0xbff5ead8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a13b7
0x82e77a8
0x8192a64
0x81427eb
0x8134414
0x815c088
0x815d15c
0x80e157b
0x80e28c9
0x80df251
0x80b32d0
0x80b9a9a
0x80b1843
0x80b1114
0x80b0634
0x82e4f5c
0x830e85a
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 0x8986058 = SHOW GLOBAL STATUS
thd->thread_id=1
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
051123 14:16:32  mysqld restarted
051123 14:16:32 [Warning] Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
/usr/sbin/mysqld: Can't create/write to file '/root/tmp/ibweAhCR' (Errcode: 13)
051123 14:16:32  InnoDB: Error: unable to create temporary file; errno: 13
051123 14:16:32 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.16-standard'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
[root@vox01 mysql]# date
Wed Nov 23 14:17:39 GMT 2005
[root@vox01 mysql]#