On 12/19/06, Frank Steinborn <[EMAIL PROTECTED]> wrote:
If I run mysqld_safe directly mysqld starts as expected. I had a look
into the script but could not find the source of the problem. I'm not
sure if that's a misconfiguration just on my site - anyone else seeing
this?
OK - I just edited the script so that it won't send mysqld_safe's
output to /dev/null and got the following:
Starting mysql.
Starting mysqld daemon with databases from /var/db/mysql
STOPPING server from pid file /var/db/mysql/shodan.nognu.de.pid
061220 04:05:50 mysqld ended
/var/db/mysql/shodan.nognu.de.err says this:
061220 04:04:03 mysqld started
061220 4:04:03 [ERROR] Can't find messagefile
'/usr/local/share/mysql/english/errmsg.sys'
061220 4:04:03 [ERROR] Aborting
Strange. /usr/local/share/mysql/english/errmsg.sys is there and mysqld
just starts fine if I start it manually. Any clues are welcome.
When you run the script, mysqld_safe is run as the mysql user.
What happens when you run mysqld_safe as the mysql user?
Does the mysql user have read access to this file (including sub
directories leading to the file)?
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
