Slow computer listing and high CPU with version 1.5.1.01798
-
Can you all edit /var/www/fog/lib/db/pdodb.class.php at line -> 125:
change:
PDO::ATTR_EMULATE_PREPARES => false,to:
PDO::ATTR_EMULATE_PREPARES => true,I’m pretty sure this is going to break other things, but it will give me a data point I’m trying to narrow down.
-
Hello @Tom-Elliott
From my side nothing changes. I tried on my production server and my fresh server with production database.
I still have some stucking time when I show hosts.
I checked on logs files, nothing new
-
No improvement after changing the PDO::ATTR_EMULATE_PREPARES value.
(I did a reboot of the server to be sure.) -
@Tom-Elliott I modified the file. No change.
-
@Infojoe I am getting this exact same issue. Very long load times on the “Hosts” and “FOG Configuration” pages. Additionally there is a number now appended to the front of all the hosts for some reason.
I updated to the latest dev branch version 1.5.10.1804 hoping for a fix, but alas, no change. I applied patches to Alma Linux 9.7 and rebooted but still seeing high CPU on several processes including apache. I am happy to test anything and everything to assist in fixing this issue.

-
@rogalskij The number in front of all hosts (and groups/snapins/images/etc…) is the Database ID of the object in question, that’s expected.
I’m trying to follow what caused this and I’m having a difficult time reproducing it.
-
@Tom-Elliott Thank you for looking into this. Are there any log files from my setup I can provide that would help you? For reference, my server environment is:
Dell Poweredge R620
2x Intel Xeon E5-2640vs 2ghz CPUs
128 Gb ram
Alma Linux 9.7
Fog 1.5.10.1804 (was 1798) -
@rogalskij I don’t know OS:
PHP error logs
/var/log/php-fpm/www-error.log (redhat based)
/var/log/apache2/error.log (debian based)SQL:
SELECT * FROM history;I doubt the sql will be of much help, but anything is better than nothing.
Most of the logs I’ve gotten this far don’t appear to have anything and maybe none of them do, in which case I don’t know when the issue was directly introduced.
If anyone is able to bisect known good and the obvious current as the starting bad to figure out when it got introduced?
I’m assuming we’ve all tried reverting to the first known good and verified it is still “good” as well?
Basically if someone doens’t mind taking where they know they’re broken, and iterating back to when it works great to exactly when it fails, it may help us figure out where to start otherwise I’m currently flying blind.
-
@Tom-Elliott I collected both log files and sent them to you directly via “Chat”. you should see all of them in there. Thanks so much for investigating this issue.
-
Is everyone having this particular problem consistently using the LDAP plugin by chance?
-
@Tom-Elliott Yes we utilize the LDAP Plugin for all logins. Version 1.5.5, I will tried logging in with a local account but the slowness persisted.
-
A test for anyone having this issue. I did a little trouble shooting, and if you go to: Reports > Pending Mac List and approve all the pending mac addresses at once, performance improved somewhat.
I am unsure if this is coincidental but for me my “Hosts” tab is now much more responsive. Same thing with the “Fog Settings” tab. Give that a try. Certainly worked for me for the moment.