Troubleshoot MySQL

From FOG Project
Revision as of 22:22, 15 June 2015 by Wayne-workman.28155 (talk | contribs) (added remote mysql access)
Jump to: navigation, search

Page is currently under construction.


Below, you may find notes and gibberish that I'm collecting to help make an article.


enable remote mysql access to root:

mysql
GRANT ALL PRIVILEGES ON *.* TO 'LocalLinuxUserNameHere'@'%' IDENTIFIED BY 'UserPasswordHere' WITH GRANT OPTION;




If you're imaging 50 to 200 computers simultaneously, you'll find the below settings helpful.

mysql
SET GLOBAL max_connections = 200;
flush hosts;


and in:

/etc/my.cnf

max_connections = 200

then restart mysql



Ubuntu has issues with mysql. Particularly anything 12 and greater seems to be hugely a problem from my experience.

The quickest way to see if things are running would be: sudo service mysql status

If it’s dead, you’ll restart it with: sudo service mysql restart

Also, if it’s dead, you’ll need to restart the fog services (after mysql is restarted):

sudo service FOGMulticastManager restart sudo service FOGScheduler restart sudo service FOGImageReplicator restart If you’re on SVN you’ll also probably need to add: sudo service FOGSnapinReplicator restart

To help prevent this in the future, follow these steps as needed/particularly the rc.local steps. https://github.com/fogproject/fogproject/issues/1




For issues with Multicast, the DB tables associated with that could be dirty. You'll know this is the case if clients just sit at the partclone screen doing nothing.


TRUNCATE TABLE multicastSessions; 
TRUNCATE TABLE multicastSessionsAssoc; 
DELETE FROM tasks WHERE taskTypeId=8;

Via MySQL cli or phpmyadmin (easy to install)