Results 1 to 12 of 12
  1. #1
    Join Date
    Apr 2009
    Location
    Ottawa, Canada
    Posts
    26

    Timeout error occurred trying to start MySQL Daemon

    I just installed mySQL server on a brand new dedicated server and am getting Timeout error occurred trying to start MySQL Daemon. I have uninstalled and reinstalled it a few times and am still getting the same error.

  2. #2
    Join Date
    Apr 2008
    Posts
    444

  3. #3
    Join Date
    Apr 2009
    Location
    Ottawa, Canada
    Posts
    26
    This is the exact error
    Timeout error occurred trying to start MySQL Daemon

    I get it when I try to start the mySQL server.

  4. #4
    When connecting to a MySQL server located on the local system, the mysql client connects through a local file called a socket instead of connecting to the localhost loopback address 127.0.0.1. For the mysql client, the default location of this socket file is /tmp/mysql.sock. But sometimes many MySQL installations place this socket file somewhere else like /var/lib/mysql/mysql.sock.

    While it is possible to make this work by specifying the socket file directly in the mysql client command

    mysql --socket=/var/lib/mysql/mysql.sock

    it is not practical to type this in every time. If you must do so this way (because you don’t have permissions to the file in the solution below), you could create an alias in your shell to make this work (like alias mysql=”mysql –socket=/var/lib/mysql/mysql.sock” depending on your shell).

    It will be easy if you can make a simple change to the MySQL configuration file /etc/my.cnf that will permanently set the socket file used by the mysql client. After making a backup copy of /etc/my.cnf, open it in your favorite editor. The file is divided into sections such as

    [mysqld]
    datadir=/usr/local/mysql/data
    socket=/var/lib/mysql/mysql.sock

    [mysql.server]
    user=mysql
    basedir=/usr/local/mysql

    If there is not currently a section called [client], add one at the bottom of the file and copy the socket= line under the [mysqld] section such as:

    [client]
    socket=/var/lib/mysql/mysql.sock

    If there is already a [client] section in the my.cnf file, add or edit the socket line as appropriate. You won’t need to restart your server or any other processes. Subsequent uses of the mysql client will use the proper socket file.

  5. #5
    Join Date
    Apr 2009
    Location
    Ottawa, Canada
    Posts
    26
    Here is a screen sht of my current my.cnf file http://screenshots.squangle.org/2009-10-30_0424.png

    Here is a screenshot of the error I receive http://screenshots.squangle.org/2009-10-30_0427.png

  6. #6
    Join Date
    Apr 2008
    Posts
    444

  7. #7
    Join Date
    Apr 2009
    Location
    Ottawa, Canada
    Posts
    26
    there is no .err fiel, just mysql and test

  8. #8
    This is caused by the MySQL start up script incorrectly attempting to do a TCP port ping to contact the server. The solution is:

    1) Edit the script /etc/rc.d/init.d/mysqld.

    2) Search for the two mysqladmin lines with the word ping in them and insert the string “-u $RANDOM” before the word “ping”:

    if [ -n "`/usr/bin/mysqladmin -u $RANDOM ping 2> /dev/null`" ]; then
    if !([ -n "`/usr/bin/mysqladmin -u $RANDOM ping 2> /dev/null`" ]); then

    3) Restart MySQL.

    After doing this MySQL should function correctly even after a reboot.

  9. #9
    Join Date
    Apr 2009
    Location
    Ottawa, Canada
    Posts
    26
    I took a look at that file and their was only 1 line with mysql admin in it, see screenshot
    http://screenshots.squangle.org/2009-10-30_0501.png

  10. #10
    Also checked the size of the partitions, sometime this might happens due to lack space in the /var partition so you need to reduce the size. Check this by using command,
    #df -h
    #cd /var
    #du - sh*

  11. #11
    Join Date
    Apr 2009
    Location
    Ottawa, Canada
    Posts
    26
    /var is not mounted as a separate filesystem and this is a brand new server so it's still got a lot of space.

  12. #12
    Join Date
    Apr 2009
    Location
    Ottawa, Canada
    Posts
    26
    Problem solved by reinstalling the operating system and making sure that the data center didn't install anything but the OS.

Similar Threads

  1. Timeout error occured trying to start MySQL Daemon
    By netlink in forum Hosting Security and Technology
    Replies: 6
    Last Post: 08-01-2010, 04:28 AM
  2. [a fatal error or timeout occurred while processing this directive]
    By LENOVOhost in forum Hosting Security and Technology
    Replies: 3
    Last Post: 09-08-2009, 07:51 AM
  3. a fatal error or timeout occurred while processing this directive
    By LP560 in forum Hosting Security and Technology
    Replies: 4
    Last Post: 09-04-2009, 11:52 AM
  4. A fatal error or timeout occurred while processing this directive
    By LENOVOhost in forum Hosting Security and Technology
    Replies: 10
    Last Post: 07-22-2009, 05:59 PM
  5. [a fatal error or timeout occurred while processing this directive]
    By cannibal in forum Hosting Security and Technology
    Replies: 9
    Last Post: 03-05-2007, 12:09 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •