[fog] Can't connect to mysql database

[jack0w]

Using FOG v0.27, had everything (including multicasting) working fine. Unfortunately this has now all changed! When I start a multicast image all clients sit on the blue screen waiting.

 

I've found this error in the multicastmanager log:

 

Failed to connect to database server, will try again in next iteration.

 

If I try to connect to the mysql database from a terminal session on the storage node I recieve the following error:

 

ERROR 2013 (HY000): Lost connection to MySQL server at 'reading authorization packet', system error: 0

 

I've been through and checked that the mysql password is correct in the config files and am now out of ideas, can anyone help me?!

[computer_expert]

have you tried restarting mysql/or the computer hosting fog?

[jack0w]

Just tried both, no joy unfortunately

[kmount]

Some interesting posts on the net about this error.

 

Is MySQL running on the same server at FOG and are you using localhost as the db host?

 

Does mysql -u username -p

 

(insert password)

 

work?

[kmount]

Might be worth checking:

 

Speed of network uplink (if it's saturated and connecting to a remote mysql server this could happen)

 

May be worth editing my.cnf to increase the timeout from 10 seconds (default) to something higher as apparently this error is badly documented as a timeout!

 

Finally, they recommend checking whether the connection is indeed being dropped on the MySQL Server itself, log in as root to mysql using the command in my other post and then type

 

show status like 'abort%';

[jack0w]

Some interesting posts on the net about this error.

 

Is MySQL running on the same server at FOG and are you using localhost as the db host?

 

Does mysql -u username -p

 

(insert password)

 

work?

 

MySQL isn't running on the same server, I've changed the db host to the servers ip address and removed the skip-networking bit as per some instructions I found a while ago.

 

If I run the above command on the server hosting the db it works fine, its just from the remote server it fails

 

I've just tried increasing the timeout as per your other post but unfortunately no joy

 

Running the command from your second post gave me this:

 

Variable_Name Value

 

Aborted_clients 1

Aborted_connects 8982

[kmount]

From the remote box you'll need -h

 

mysql -h ipofmysqlserverbox -u username -p

 

Have a look for my.cnf (probably in /etc) and try upping the connect_timeout in there.

 

Which distro are you using and I'll see if I can find where it lives.

 

I've been reading from here mostly if you want a nose there.

[jack0w]

Thanks for your help kmount

 

I'm running Ubuntu 9.04

[kmount]

Run

 

mysql -u root -p (on the local box is fine) or use -h remotely.

 

In the mysql shell type "show variables;"

 

Let's just check what your connect_timeout is set to. (mine is set to 5)

[jack0w]

Run

 

mysql -u root -p (on the local box is fine) or use -h remotely.

 

In the mysql shell type "show variables;"

 

Let's just check what your connect_timeout is set to. (mine is set to 5)

 

Just run this from the local box, timeout is currently set to 10.

[kmount]

I'm sure I posted an update to this thread with instructions on how to up this!

 

(eyes the database)

 

ok, in /etc/my.cnf under the [mysqld] section put

 

connect_timeout = 5000

 

then save it, restart mysql with (/etc/init.d/mysql restart) and try it again to make sure the timeout has increased to that silly high number.

 

(then try your fog stuff)

 

If it still doesn't work I'm a little stumped!

[jack0w]

I'm sure I posted an update to this thread with instructions on how to up this!

 

(eyes the database)

 

ok, in /etc/my.cnf under the [mysqld] section put

 

connect_timeout = 5000

 

then save it, restart mysql with (/etc/init.d/mysql restart) and try it again to make sure the timeout has increased to that silly high number.

 

(then try your fog stuff)

 

If it still doesn't work I'm a little stumped!

 

Kmount you're a legend! All working fine now.

 

Thanks so much for your help

[kmount]

You're very welcome mate, might be worth dropping that down a bit or at least making sure mysql isn't publicly accessible as currently it will now wait 5000 seconds before closing off / rejecting an invalid connection (ie, a telnet host 3306)

 

Glad it's working