This line probably should have been a good hint:
>>InnoDB: File operation call: 'tmpfile'.
Any idea why the server crashed in the first place? That's not the sort of thing you want just randomly happening, I'd imagine. Although it might make life a bit more interesting...
Cheers.
--V
Chris Blackwell wrote:
I have resolved this issue now, it was actually the permission on /tmp that had become corrupted as a result of the crash I can only assume
chmod 777 /tmp chmod +t /tmp
this fixed the problem but could have been fixed within minutes not days if the error message had told me which directory was causing the problem :/
chris
-----Original Message-----
From: Egor Egorov [mailto:[EMAIL PROTECTED] Sent: 12 August 2004 10:26
To: [EMAIL PROTECTED]
Subject: Re: MySQL won't start... was runnnig fine
"Chris Blackwell" <[EMAIL PROTECTED]> wrote:
now when ever i try to start mysql i get the following error in log
040812 09:52:34 mysqld started
040812 9:52:34 Warning: Asked for 196608 thread stack, but got 126976
040812 9:52:34 InnoDB: Error: unable to create temporary file
040812 9:52:34 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File operation call: 'tmpfile'.
InnoDB: Cannot continue operation.
040812 09:52:34 mysqld ended
[EMAIL PROTECTED] egor]$ perror 13 Error code 13: Permission denied
i have chown -R the /var/lib/mysql directory
So anyway permission denied. Check the rights on /var/lib/mysql itself
-- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
