Hello.
Check that you don't have problems with filesystem. Start mysqld directly, specify the corresponding variables in the command line. If it doesn't produce errors switch to the debug version of the server and use the trace files to find where the problem is. Ron Gilbert <[EMAIL PROTECTED]> wrote: > 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? > > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [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]
