O/S Deployment Thread, Can't connect to mysql database in Technical; Using FOG v0.27, had everything (including multicasting) working fine. Unfortunately this has now all changed! When I start a multicast ...
27th October 2009, 02:32 PM #1
Can't connect to mysql database
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?!
27th October 2009, 04:43 PM #2
have you tried restarting mysql/or the computer hosting fog?
28th October 2009, 09:06 AM #3
Just tried both, no joy unfortunately
28th October 2009, 09:20 AM #4
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
28th October 2009, 09:28 AM #5
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%';
28th October 2009, 10:03 AM #6
28th October 2009, 10:16 AM #7
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.
28th October 2009, 10:17 AM #8
Thanks for your help kmount
I'm running Ubuntu 9.04
28th October 2009, 10:21 AM #9
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)
28th October 2009, 10:28 AM #10
Just run this from the local box, timeout is currently set to 10.
Originally Posted by kmount
28th October 2009, 10:43 AM #11
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!
Thanks to kmount from:
jack0w (28th October 2009)
28th October 2009, 10:48 AM #12
28th October 2009, 10:52 AM #13
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
Last Post: 25th June 2011, 06:46 PM
By Quackers in forum Scripts
Last Post: 3rd February 2009, 11:42 PM
By deano in forum Web Development
Last Post: 28th September 2007, 04:09 PM
By StewartKnight in forum Web Development
Last Post: 21st February 2007, 09:53 AM
By ryan_powell in forum MIS Systems
Last Post: 26th October 2006, 07:31 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)