Troubleshoot MySQL - Revision history

Wayne-workman.28155: /* MySQL Config File */

2018-01-30T01:43:57Z

‎MySQL Config File

Wayne-workman.28155: /* Database Maintenance Commands */

2017-12-16T14:13:49Z

‎Database Maintenance Commands

Wayne-workman.28155: /* Database Maintenance Commands */

2017-12-16T14:13:12Z

‎Database Maintenance Commands

Wayne-workman.28155: /* Database Maintenance Commands */

2017-12-16T14:08:48Z

‎Database Maintenance Commands

Wayne-workman.28155: /* Database Maintenance Commands */

2017-12-16T14:08:12Z

‎Database Maintenance Commands

Wayne-workman.28155: /* Database Maintenance Commands */ Added multicast cleaning to db maintenance commands.

2017-12-16T14:07:26Z

‎Database Maintenance Commands: Added multicast cleaning to db maintenance commands.

Wayne-workman.28155: /* Database Maintenance Commands */

2017-11-02T11:52:37Z

‎Database Maintenance Commands

Wayne-workman.28155: /* Reset MySQL fog user and password */

2017-07-26T18:59:49Z

‎Reset MySQL fog user and password

Wayne-workman.28155: /* Reset MySQL fog user and password */

2017-07-26T18:59:25Z

‎Reset MySQL fog user and password

Wayne-workman.28155: /* Reset MySQL fog user and password */

2017-07-26T18:59:14Z

‎Reset MySQL fog user and password

@@ Line 62: / Line 62: @@
 The location of this file varies based on the distribution of Linux you're using. Usually it's called my.cnf and it's probably best to just issue a search command for the file and then figure out which one of the results it is, generally you can pick it out quickly based on the path that the file is in. Here's how to search:
-<pre>find / | grep /my.cnf</pre>
+<pre>find / -type f -name my.cnf</pre>
 Here is a sample output from Fedora 23:
@@ Line 74: / Line 74: @@
 In this case, the first result is the right file, <font color="red">/etc/my.cnf</font> Looking into this particular file (on Fedora 23), there is a line that says <font color="red">!includedir /etc/my.cnf.d</font> This means any files in that directory, <font color="red">/etc/my.cnf.d</font> are included in MySQL's configuration.
 =MySQL credentials for FOG Main and Storage Nodes=

@@ Line 275: / Line 275: @@
-# The following chunk of commands are safe to run on any fog system, and will clean out most problems:
+# The following chunk of commands will clean out most problems and are safe:
 DELETE FROM `hosts` WHERE `hostID` = '0';
 DELETE FROM `hostMAC` WHERE hmID = '0' OR `hmHostID` = '0';

@@ Line 275: / Line 275: @@
 DELETE FROM `hosts` WHERE `hostID` = '0';
 DELETE FROM `hostMAC` WHERE hmID = '0' OR `hmHostID` = '0';
@@ Line 291: / Line 292: @@
 DELETE FROM tasks WHERE taskTypeId=8;
 quit
 </pre>

@@ Line 271: / Line 271: @@
 mysql -D fog
-#Password:
+# Password:
 mysql --user=UsernameHere --password=PasswordHere -D fog

@@ Line 265: / Line 265: @@
 = Database Maintenance Commands =
-Sometimes, a host will be created with an ID of 0 (zero). Sometimes, there are MAC addresses that loose their association with a host, and in a sense become orphaned. Sometimes there are tasks that just need cleared out. Sometimes there are hosts without MACs. Sometimes groups of ID 0 get made, sometimes snapins of ID 0 get made. Sometimes snapins are associated with hosts that don't exist anymore. Other things go wrong sometimes. These things cause problems with FOG's operation and need cleared out in order to have a clean & healthy database. The below commands are intended to run on FOG 1.3, 1.4, and 1.5 series, they will clear these problems for you. This also fixes problems with multicast occasionally, where the db gets gummed up with bad multicast data.
+Sometimes, a host will be created with an ID of 0 (zero). Sometimes, there are MAC addresses that loose their association with a host, and in a sense become orphaned. Sometimes there are tasks that just need cleared out. Sometimes there are hosts without MACs. Sometimes groups of ID 0 get made, sometimes snapins of ID 0 get made. Sometimes snapins are associated with hosts that don't exist anymore. Other things go wrong sometimes. These things cause problems with FOG's operation and need cleared out in order to have a clean & healthy database. The below commands are intended to run on FOG 1.3, 1.4, and 1.5 series, they will clear these problems for you. This also fixes problems with multicast occasionally, where the partclone screen just sits there doing nothing.
 <pre>

@@ Line 108: / Line 108: @@
 <pre>
 ALTER USER 'fog'@'localhost' IDENTIFIED WITH mysql_native_password BY 'YourPasswordGoesHere';
-Or:
+#Or:
 ALTER USER 'fog'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY 'YourPasswordGoesHere';
-Or no password:
+#Or no password:
 ALTER USER 'fog'@'localhost' IDENTIFIED WITH mysql_native_password BY '';
 </pre>

@@ Line 113: / Line 113: @@
 ALTER USER 'fog'@'localhost' IDENTIFIED WITH mysql_native_password BY '';
 </pre>
 =Change MySQL user's password=