Around 100% cpu usage constantly

[Tom Elliott]

I’ve added some code in hopes to prevent runaway services such as this. With any luck the 100% cpu do to FOG services will be no more.

The Defaults, in case of issues:

FOGImageReplicator = 600 seconds (10 Minutes)
FOGSnapinReplicator = 600 seconds (10 Minutes)
FOGPingHosts = 300 seconds (5 Minutes)
FOGScheduler = 60 seconds (1 Minute)
FOGMulticastManager = 10 seconds

The writing to log files isn’t as important as the timing. It’s the timing that’s causing the run away CPU cycles as they’re running infinitely. Without a sleep to slow it all down, the services will keep doing work without a break, causing the spikes you’re describing.

[coco65]

@Tom-Elliott

Just updated both the fog-server and the fog-node to 7945 on debian 8 both. Nothing has changed I am afraid. The fog server runs fine but the storage node is at a constant 100% processor load. The 4 FOG services (ImageReplicator etc) keep using every processor cycle they can get.

[Tom Elliott]

@coco65 Run the script as it was designed earlier.

service FOGMulticastManager stop && sleep 5 && service FOGMulticastManager start
service FOGPingHosts stop && sleep 5 && service FOGPingHosts start
service FOGImageReplicator stop && sleep 5 && service FOGImageReplicator start
service FOGSnapinReplicator stop && sleep 5 && service FOGSnapinReplicator start
service FOGScheduler stop && sleep 5 && service FOGScheduler start

OR:

systemctl stop FOGMulticastManager && sleep 5 && systemctl start FOGMulticastManager
systemctl stop FOGPingHosts && sleep 5 && systemctl start FOGPingHosts
systemctl stop FOGImageReplicator && sleep 5 && systemctl start FOGImageReplicator
systemctl stop FOGSnapinReplicator && sleep 5 && systemctl start FOGSnapinReplicator
systemctl stop FOGScheduler && sleep 5 && systemctl start FOGScheduler

This is going to make sure the services have enough time to restart. The Installer appears to not satisfy the “timing” properly.

[coco65]

@Tom-Elliott : Thank you that works (the second version with systemctrl)

[Tom Elliott]

That’s why I post both. I have no idea what type your system is going to use so I just brute force them all.

In either case, this shouldn’t be a problem even on subsequent updates now.