@Arrowtron Well, what I would like to do is make it worse to make it better. The meaning is to reset as much of the fixes you’ve done to this point to put it back to what way FOG was installed. This includes any adjustments suggested by the mysql tuner script. We need to have it as close to as installed as possible. Also reset the fog client check in time.
Run it in the as installed configuration for a few hours during your peak business time. Use top and sort by processor usage. Grab a screen shot of the top screen.
Shutdown apache
Lets make sure we have a good backup of the mysql server before doing anything. From the fog server linux command prompt key in mysqldump -u root -p --all-databases > all-databases-backup.sql
login to the mysql command line tool with mysql -u root -p fog You will need to use the password you created for the root database user when you installed fog. If you don’t know the password that could be a problem. The older version of FOG had a black password for the mysql root user. Understand I’m using mysql to mean both mysql and mariadb. The command line tool is the same.
At db prompt paste in this command.
SELECT TABLE_NAME,ENGINE
FROM information_schema.TABLES
WHERE TABLE_SCHEMA = 'fog' and ENGINE = 'MyISAM';
You should see an output that looks like this
+------------------------+--------+
| TABLE_NAME | ENGINE |
+------------------------+--------+
| LDAPServers | MyISAM |
| clientUpdates | MyISAM |
| dirCleaner | MyISAM |
| globalSettings | MyISAM |
| greenFog | MyISAM |
| groupMembers | MyISAM |
| groups | MyISAM |
| history | MyISAM |
| hookEvents | MyISAM |
| hostAutoLogOut | MyISAM |
| hostMAC | MyISAM |
| hostScreenSettings | MyISAM |
| hosts | MyISAM |
| imageGroupAssoc | MyISAM |
| imagePartitionTypes | MyISAM |
| imageTypes | MyISAM |
| images | MyISAM |
| imagingLog | MyISAM |
| inventory | MyISAM |
| ipxeTable | MyISAM |
| keySequence | MyISAM |
| location | MyISAM |
| locationAssoc | MyISAM |
| moduleStatusByHost | MyISAM |
| modules | MyISAM |
| multicastSessions | MyISAM |
| multicastSessionsAssoc | MyISAM |
| nfsFailures | MyISAM |
| nfsGroupMembers | MyISAM |
| nfsGroups | MyISAM |
| notifyEvents | MyISAM |
| os | MyISAM |
| oui | MyISAM |
| plugins | MyISAM |
| powerManagement | MyISAM |
| printerAssoc | MyISAM |
| printers | MyISAM |
| pxeMenu | MyISAM |
| scheduledTasks | MyISAM |
| schemaVersion | MyISAM |
| snapinAssoc | MyISAM |
| snapinGroupAssoc | MyISAM |
| snapinJobs | MyISAM |
| snapinTasks | MyISAM |
| snapins | MyISAM |
| supportedOS | MyISAM |
| taskLog | MyISAM |
| taskStates | MyISAM |
| taskTypes | MyISAM |
| tasks | MyISAM |
| userCleanup | MyISAM |
| userTracking | MyISAM |
| users | MyISAM |
| virus | MyISAM |
| wolbroadcast | MyISAM |
+------------------------+--------+
55 rows in set (0.00 sec)
If your tables show innodb then we have to stop because your database is not in the default state.
If your database files say MyISAM then proceed and paste in these lines. You can do them in one block paste in. Just make sure the last line is entered too.
ALTER TABLE LDAPServers ENGINE=InnoDB;
ALTER TABLE clientUpdates ENGINE=InnoDB;
ALTER TABLE dirCleaner ENGINE=InnoDB;
ALTER TABLE globalSettings ENGINE=InnoDB;
ALTER TABLE greenFog ENGINE=InnoDB;
ALTER TABLE groupMembers ENGINE=InnoDB;
ALTER TABLE groups ENGINE=InnoDB;
ALTER TABLE history ENGINE=InnoDB;
ALTER TABLE hookEvents ENGINE=InnoDB;
ALTER TABLE hostAutoLogOut ENGINE=InnoDB;
ALTER TABLE hostMAC ENGINE=InnoDB;
ALTER TABLE hostScreenSettings ENGINE=InnoDB;
ALTER TABLE hosts ENGINE=InnoDB;
ALTER TABLE imageGroupAssoc ENGINE=InnoDB;
ALTER TABLE imagePartitionTypes ENGINE=InnoDB;
ALTER TABLE imageTypes ENGINE=InnoDB;
ALTER TABLE images ENGINE=InnoDB;
ALTER TABLE imagingLog ENGINE=InnoDB;
ALTER TABLE inventory ENGINE=InnoDB;
ALTER TABLE ipxeTable ENGINE=InnoDB;
ALTER TABLE keySequence ENGINE=InnoDB;
ALTER TABLE location ENGINE=InnoDB;
ALTER TABLE locationAssoc ENGINE=InnoDB;
ALTER TABLE moduleStatusByHost ENGINE=InnoDB;
ALTER TABLE modules ENGINE=InnoDB;
ALTER TABLE multicastSessions ENGINE=InnoDB;
ALTER TABLE multicastSessionsAssoc ENGINE=InnoDB;
ALTER TABLE nfsFailures ENGINE=InnoDB;
ALTER TABLE nfsGroupMembers ENGINE=InnoDB;
ALTER TABLE nfsGroups ENGINE=InnoDB;
ALTER TABLE notifyEvents ENGINE=InnoDB;
ALTER TABLE os ENGINE=InnoDB;
ALTER TABLE oui ENGINE=InnoDB;
ALTER TABLE plugins ENGINE=InnoDB;
ALTER TABLE powerManagement ENGINE=InnoDB;
ALTER TABLE printerAssoc ENGINE=InnoDB;
ALTER TABLE printers ENGINE=InnoDB;
ALTER TABLE pxeMenu ENGINE=InnoDB;
ALTER TABLE scheduledTasks ENGINE=InnoDB;
ALTER TABLE schemaVersion ENGINE=InnoDB;
ALTER TABLE snapinAssoc ENGINE=InnoDB;
ALTER TABLE snapinGroupAssoc ENGINE=InnoDB;
ALTER TABLE snapinJobs ENGINE=InnoDB;
ALTER TABLE snapinTasks ENGINE=InnoDB;
ALTER TABLE snapins ENGINE=InnoDB;
ALTER TABLE supportedOS ENGINE=InnoDB;
ALTER TABLE taskLog ENGINE=InnoDB;
ALTER TABLE taskStates ENGINE=InnoDB;
ALTER TABLE taskTypes ENGINE=InnoDB;
ALTER TABLE tasks ENGINE=InnoDB;
ALTER TABLE userCleanup ENGINE=InnoDB;
ALTER TABLE userTracking ENGINE=InnoDB;
ALTER TABLE users ENGINE=InnoDB;
ALTER TABLE virus ENGINE=InnoDB;
ALTER TABLE wolbroadcast ENGINE=InnoDB;
Once that is done run the same query again to make sure all of the tables now say innodb
SELECT TABLE_NAME,ENGINE
FROM information_schema.TABLES
WHERE TABLE_SCHEMA = 'fog';
If they are all innodb then you can exit the mysql program if I missed one then run the ALTER TABLE command on those missing tables. Please not any table I missed.
At this point reboot the FOG server.
When the fog server comes back up make sure the web ui works as expected. Let the FOG server run for a few hours then again capture a snapshot for the settings using top. Post the results here.
This next test is to let the FOG server run for a week using the innodb format then rerun the mysql tuner script. DON’T apply the settings, but post the results here. Let us look at the recommendations before you apply them to the FOG server’s database.
In the end what we need to know is the change in performance by simply changing the database engine from isam to innodb format. Also to see the recommendations provided by mysqltuner. I have some default settings for the innodb that I would start out with, but they may not be right for all situation.
Let me say we do need help from FOG Admins who have either unique target hardware or large installations that can’t be simulated easily. With your help I feel strongly that we can improve FOG’s performance and move everyone’s FOG install in a positive direction.
