@Tom-Elliott I also updated to 1807 and it has fixed it for me as well. As always Tom you are a mad scientist and always figure out the issue. FOG Project is the fastest bug resolution of any software we use and I mean that sincerely. I appreciate this software and your dedication to it so much, thanks for everything!
FOG Hangouts
Being a member of FOG Hangouts will allow you to stay updated about the latest FOG Hangout; the when, the where, and the details. Membership in this group is automatic membership in a mailing list.
Posts
-
RE: Slow computer listing and high CPU with version 1.5.1.01798posted in FOG Problems
-
RE: Slow computer listing and high CPU with version 1.5.1.01798posted in FOG Problems
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.
-
RE: Slow computer listing and high CPU with version 1.5.1.01798posted in FOG Problems
@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.
-
RE: Slow computer listing and high CPU with version 1.5.1.01798posted in FOG Problems
@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.
-
RE: Slow computer listing and high CPU with version 1.5.1.01798posted in FOG Problems
@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) -
RE: Slow computer listing and high CPU with version 1.5.1.01798posted in FOG Problems
@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.

-
RE: All services are globally disabledposted in FOG Problems
I switched back to the dev-branch because fearing there may be a schema mismatch, but i still have the same issues with all the services being globally disabled.
Fogsnapinrep.log
[02-25-26 2:44:26 pm] Interface Ready with IP Address: x.x.x.x
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 10fogserver
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.0.1
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.1.1
[02-25-26 2:44:26 pm] * Starting SnapinReplicator Service
[02-25-26 2:44:26 pm] * Checking for new items every 600 seconds
[02-25-26 2:44:26 pm] * Starting service loop
[02-25-26 2:44:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:44:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:44:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:54:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:54:26 pm] | Sleep time has changed to seconds
[02-25-26 3:04:26 pm] * * Snapin replication is globally disabled
[02-25-26 3:04:26 pm] | Sleep time has changed to secondsfogreplicator.log
[02-25-26 2:44:26 pm] Interface Ready with IP Address: x.x.x.x
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 10fogserver
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.0.1
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.1.1
[02-25-26 2:44:26 pm] * Starting ImageReplicator Service
[02-25-26 2:44:26 pm] * Checking for new items every 600 seconds
[02-25-26 2:44:26 pm] * Starting service loop
[02-25-26 2:44:26 pm] * * Image replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:44:26 pm] * * Image replication is globally disabled
[02-25-26 2:44:26 pm] * * Image replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:54:26 pm] * * Image replication is globally disabled
[02-25-26 2:54:26 pm] | Sleep time has changed to seconds
[02-25-26 3:04:26 pm] * * Image replication is globally disabled
[02-25-26 3:04:26 pm] | Sleep time has changed to secondsfogscheduler.log
[02-25-26 2:44:26 pm] Interface Ready with IP Address: x.x.x.x
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 10fogserver
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.0.1
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.1.1
[02-25-26 2:44:26 pm] * Starting TaskScheduler Service
[02-25-26 2:44:26 pm] * Checking for new items every 60 seconds
[02-25-26 2:44:26 pm] * Starting service loop
[02-25-26 2:44:26 pm] * No tasks found!
[02-25-26 2:45:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:45:26 pm] | Sleep time has changed to seconds
[02-25-26 2:46:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:46:26 pm] | Sleep time has changed to seconds
[02-25-26 2:47:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:47:26 pm] | Sleep time has changed to seconds
[02-25-26 2:48:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:48:26 pm] | Sleep time has changed to seconds
[02-25-26 2:49:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:49:26 pm] | Sleep time has changed to seconds
[02-25-26 2:50:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:50:26 pm] | Sleep time has changed to seconds
[02-25-26 2:51:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:51:26 pm] | Sleep time has changed to seconds
[02-25-26 2:52:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:52:26 pm] | Sleep time has changed to seconds
[02-25-26 2:53:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:53:26 pm] | Sleep time has changed to seconds
[02-25-26 2:54:26 pm] * Task Scheduler is globally disabledThe same for these logs as well.
fogimagesize.log
fogsnapinhash.log
fogsnapinrep.log
pinghost.logI have checked the mysql DB
SELECT settingID, settingKey, settingValue FROM globalSettings WHERE settingKey LIKE '%ENABLED%';"settingID" "settingKey" "settingValue" "33" "FOG_CLIENT_DIRECTORYCLEANER_ENABLED" "0" "35" "FOG_CLIENT_USERCLEANUP_ENABLED" "0" "36" "FOG_CLIENT_GREENFOG_ENABLED" "0" "37" "FOG_CLIENT_AUTOLOGOFF_ENABLED" "0" "38" "FOG_CLIENT_DISPLAYMANAGER_ENABLED" "0" "45" "FOG_CLIENT_HOSTNAMECHANGER_ENABLED" "1" "46" "FOG_CLIENT_SNAPIN_ENABLED" "1" "48" "FOG_CLIENT_CLIENTUPDATER_ENABLED" "0" "49" "FOG_CLIENT_HOSTREGISTER_ENABLED" "1" "50" "FOG_CLIENT_PRINTERMANAGER_ENABLED" "0" "51" "FOG_CLIENT_TASKREBOOT_ENABLED" "1" "52" "FOG_CLIENT_USERTRACKER_ENABLED" "1" "58" "FOG_PLUGINSYS_ENABLED" "1" "121" "FOG_REGISTRATION_ENABLED" "1" "156" "FOG_CLIENT_POWERMANAGEMENT_ENABLED" "1" "174" "IMAGEREPLICATORGLOBALENABLED" "1" "175" "SNAPINREPLICATORGLOBALENABLED" "1" "176" "SNAPINHASHGLOBALENABLED" "1" "177" "PINGHOSTGLOBALENABLED" "1" "178" "SCHEDULERGLOBALENABLED" "1" "179" "MULTICASTGLOBALENABLED" "1" "182" "IMAGESIZEGLOBALENABLED" "1" "187" "FOG_TASKING_ADV_SHUTDOWN_ENABLED" "0" "188" "FOG_TASKING_ADV_WOL_ENABLED" "1" "189" "FOG_TASKING_ADV_DEBUG_ENABLED" "0" "190" "FOG_API_ENABLED" "1" "197" "FOG_SNAPIN_LOCATION_SEND_ENABLED" "1" "200" "FOG_REPLICATOR_GLOBAL_ENABLED" "1" "201" "FOG_SNAPINREPLICATOR_GLOBAL_ENABLED" "1" "203" "FOG_TASK_SCHEDULER_ENABLED" "1"Any hepl would greatly be appreciated…
Thanks!
P.S. I am not apposed to restarting from scratch as long as i can save my snapins and images. -
RE: All services are globally disabledposted in FOG Problems
@Tom-Elliott
That may be my problem Tom. I switched to the Stable build, I may have inconsistant DB schema between the two?
The GUI says I am on Version 1.5.10.1763 -
Debian Trixie Dependancy Errorsposted in Linux Problems
Hello,
I’ve ran into a problem. When upgrading from Debian 12 to Debian 13 I no longer can get to the webpage for fog. I get a 503 service unavailable. After seeing that I decided to re-run the installer to see if that would help but then I get the following dependency conflicts and was wondering if anyone has ran into this yet with Debian 13 Trixie.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
systemd-sysv : Conflicts: initscripts but 3.14-4 is to be installed
Conflicts: insserv but 1.26.0-1 is to be installed
Conflicts: startpar but 0.66-1 is to be installed
Conflicts: sysv-rc but 3.14-4 is to be installed
Conflicts: sysvinit-core but 3.14-4 is to be installed
sysvinit-core : Conflicts: systemd-sysv but 257.9-1~deb13u1 is to be installed
Recommends: orphan-sysvinit-scripts but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:- sysvinit-core:amd64 is not selected for install because:
- systemd-sysv:amd64 is selected for install
- systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2
[selected systemd-sysv:amd64=257.9-1~deb13u1 for install] - sysvinit-core:amd64 Conflicts systemd-sysv
[selected systemd-sysv:amd64=257.9-1~deb13u1]
For context, additional choices that could not be installed:
- In systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2:
- systemd-sysv:amd64=257.8-1~deb13u2 is not selected for install
- sysvinit-core:amd64 is selected for install because:
- sysv-rc-conf:amd64=0.99-10 is selected for install
- sysv-rc-conf:amd64 Depends sysvinit-core
- sysvinit-core:amd64 is not selected for install because:
-
RE: FOG Boot via HTTP without DHCPposted in FOG Problems
Unfortunately, HTTP boot still requires a dhcp server.