Difference between revisions of "Troubleshoot MySQL"
m (Added example for importing and exporting the DB on the FOG server.) |
|||
Line 5: | Line 5: | ||
-------------------------------------------------------------------------- | -------------------------------------------------------------------------- | ||
+ | '''Manually export / import Fog database.''' | ||
− | enable remote mysql access to a linux user account: | + | Export: |
+ | |||
+ | <pre>mysqldump -u USERNAME -p PASSWORD -h HOSTNAME fog > fogDB.sql</pre> | ||
+ | |||
+ | Import: | ||
+ | |||
+ | <pre>mysql -u USERNAME -p PASSWORD -h HOSTNAME fog < fogDB.sql</pre> | ||
+ | |||
+ | |||
+ | Example using root and 13375p3@k as the password on the local host. | ||
+ | |||
+ | <pre>#Exporting my DB locally on my FOG server... | ||
+ | mysql -u root -p 13375p3@k fog > fog_backup.sql | ||
+ | # | ||
+ | #Here is an import example... | ||
+ | mysql -u root -p 13375p3@k fog < fog_backup.sql | ||
+ | # | ||
+ | #Here is an example of exporting a remote DB to your current directory, where x.x.x.x would be replaced by the IP of the remote system... | ||
+ | mysql -u root -p 13375p3@k -h x.x.x.x fog > fog_backup.sql</pre> | ||
+ | |||
+ | |||
+ | -------------------------------------------------------------------------- | ||
+ | |||
+ | '''enable remote mysql access''' to a linux user account: | ||
<pre>mysql | <pre>mysql |
Revision as of 17:41, 28 July 2015
Page is currently under construction.
Below, you may find notes and gibberish that I'm collecting to help make an article.
Manually export / import Fog database.
Export:
mysqldump -u USERNAME -p PASSWORD -h HOSTNAME fog > fogDB.sql
Import:
mysql -u USERNAME -p PASSWORD -h HOSTNAME fog < fogDB.sql
Example using root and 13375p3@k as the password on the local host.
#Exporting my DB locally on my FOG server... mysql -u root -p 13375p3@k fog > fog_backup.sql # #Here is an import example... mysql -u root -p 13375p3@k fog < fog_backup.sql # #Here is an example of exporting a remote DB to your current directory, where x.x.x.x would be replaced by the IP of the remote system... mysql -u root -p 13375p3@k -h x.x.x.x fog > fog_backup.sql
enable remote mysql access to a linux user account:
mysql GRANT ALL PRIVILEGES ON *.* TO 'LocalLinuxUserNameHere'@'%' IDENTIFIED BY 'UserPasswordHere' WITH GRANT OPTION;
Some systems have a bind address set. You can disable that in the my.cnf file.
Search for that file with this:
find / | grep my.cnf
Comment out these lines with a hash tag #
#skip-networking #bind-address = 127.0.0.1
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)