Ron,
I have run into the issue you described in the past. Do the following: touch path_to_mysql/name_of_pid chown mysql:mysql path_to_mysql/name_of_pid
Hope this helps.
Quoting Ron Gilbert <[EMAIL PROTECTED]>:
After almost a year of being up, my RH9 server lost power and rebooted. When it came back up, mysql was not running. I went in and ran safe_mysql to start it back up (I also tried the init.d script) but it failed to start. No errors, nothing in the log. After some investigation, it appears that the .pid file is never being created, so the safe_mysql ends immediately. The only entry in the log or error files in the a notice that mysqld ended, and that's it.
The only clue I have is several month ago I was playing around with the mysql user and gave it a password. I can't imagine how that would cause a problem, but it's the only thing I can think of. If this is the problem, I'm not sure how to get the mysql user back to the default state.
Is the problem the mysql user? All the permission for all the database directories are set correctly. I'm am puzzled that mysqld just ends, not messages.
Any clues?
-- MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
James Nobis Web Developer Academic Superstore 223 W. Anderson Ln. Suite A110, Austin, TX 78752 Voice: (512) 450-1199 x453 Fax: (512) 450-0263 http://www.academicsuperstore.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
