Difference between revisions of "Troubleshoot MySQL"

From FOG Project
Jump to: navigation, search
(added more stuff)
Line 6: Line 6:
  
 
<pre>mysql
 
<pre>mysql
SET GLOBAL max_connections = 500;
+
SET GLOBAL max_connections = 200;
 
flush hosts;</pre>
 
flush hosts;</pre>
  
Line 14: Line 14:
 
/etc/my.cnf
 
/etc/my.cnf
  
max_connections = 500
+
max_connections = 200
  
 
then restart mysql
 
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.
 +
 +
 +
<pre>TRUNCATE TABLE multicastSessions;
 +
TRUNCATE TABLE multicastSessionsAssoc;
 +
DELETE FROM tasks WHERE taskTypeId=8;</pre>
 +
 +
Via MySQL cli or phpmyadmin (easy to install)

Revision as of 15:14, 14 June 2015

Page is currently under construction.


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


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)