cannot get MYSQL To Start
Posted by: caution (---.twcny.res.rr.com)
Date: March 01, 2009 07:21AM

um i keep getting a error log from Mysql that keeps saying this

090227 15:42:17 InnoDB: Error: unable to create temporary file; errno: 2
090227 15:42:17 [ERROR] Plugin 'InnoDB' init function returned error.
090227 15:42:17 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
090227 15:42:17 - mysqld got exception 0xc0000005 ;
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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x22263a0
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...
00560F71 mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 00000000=(null)
thd->thread_id=0
thd->killed=NOT_KILLED
The manual page at [dev.mysql.com] contains
information that should help you find out what is causing the crash.
090227 17:16:31 InnoDB: Error: unable to create temporary file; errno: 2
090227 17:16:31 [ERROR] Plugin 'InnoDB' init function returned error.
090227 17:16:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
090227 17:16:32 - mysqld got exception 0xc0000005 ;
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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x22263a0
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...
00560F71 mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 00000000=(null)
thd->thread_id=0
thd->killed=NOT_KILLED
The manual page at [dev.mysql.com] contains
information that should help you find out what is causing the crash.
090228 18:51:14 InnoDB: Error: unable to create temporary file; errno: 2
090228 18:51:14 [ERROR] Plugin 'InnoDB' init function returned error.
090228 18:51:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
090228 18:51:14 - mysqld got exception 0xc0000005 ;
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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x22263a0
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...
00560F71 mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 00000000=(null)
thd->thread_id=0
thd->killed=NOT_KILLED
The manual page at [dev.mysql.com] contains
information that should help you find out what is causing the crash.

if anyone can please help thanks

Options: ReplyQuote


Sorry, only registered users may post in this forum.