Can't Run 5.0

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I just upgraded my Slackware Linux box from MySQL 4.0 to 5.0 and I'm
getting a strange error when I try to start the service. The error log

/usr/libexec/mysqld: File '/var/log/mysql.000001' not found (Errcode:
060324 15:05:19 [ERROR] Could not use /var/log/mysql for logging (error
13). Turning logging off for the whole duration of the MySQL server
process. To turn it on again: fix the cause, shutdown the MySQL server
and restart it.
060324 15:05:19 [ERROR] Aborting

If I create that file (/var/log/mysql.000001) then the error just says
"/var/log/mysql.000002" and then "/var/log/mysql.000003" and so on.
What would be causing something like this, and how would I fix it?

David P. Donahue

Re: Can't Run 5.0

Quoted text here. Click to load it

Is the mysqld process running as a user id (e.g. user mysql) that lacks the
privilege to create files in /var/log?

Bill K.

Re: Can't Run 5.0

Strange.  Your reply got me poking around with file permissions and
whatnot, and you're right about that.  The strange part, though, was
that this seems to be some kind of change between 4.0 and 5.0.

My config file for 4.0 specified a couple log files in /var/log for
query logging, which were owned by the mysql user and worked fine.  But
the default log file location was still the mysql data directory for
anything else.  With 5.0, it seems that those couple log specifications
were enough to change the default directory of all mysqld logging to
the same directory that those specific ones were in (/var/log).

I'll just give the mysql user a subdirectory of /var/log and let it
write to that.  I wonder if this is some kind of side effect to another
change between 4.0 and 5.0 that just hasn't been documented, or if I
just missed the documentation on it.  Anyway, thanks for pointing me in
the right direction :)

David P. Donahue

Site Timeline