This is a problem with only mySQL. I upgraded MySQL 4.0.21 to 4.0.22 because I was going to install Session support on my server for PHP4.

After upgrading, mySQL was not running, and will not run if I run the daemon. It gives me this error:

Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
041031 12:31:10 Aborting
041031 12:31:10 ./mysqld: Shutdown Complete

I AM running the daemon as root. If I run the command like this:

./mysqld --user=root

It does start the server, but it sits in the console, and the only way to get out is to break it (Ctrl+C), then the server is back off.

Anyone else experience this error or know what the hell is up?

("mysql-server.sh start" does not work by the way)

Thanks,
Tom 🙂

    Ok, that makes sense. All my files are set as user "mysql" which is what the daemon was running under before.

    The mysql.sock file is set to owner root / group wheel

    This document you referred me to talks about the my.cnf file. I've done a complete search of my directory structure and can't find it.

    Unless I set the socket owner to mysql it won't let me run "mysqld --user=mysql"

    How did upgrading hose things up so badly? 🙂 Any more help to get this thing back to a working state would be appreciated.

    Thanks,
    Tom 🙂

      Little update. I looked at another server I run and the socket file was owned by the mysql user, so I chown'd the one on my box at home and still no luck using the mysql-server script. Not even an error..

      Please let me know if anyone thinks of any problem this could be.

      Thanks again,
      Tom

        Write a Reply...