I can confirm the 100% cpu usage issue. I don’t have any storage nodes in my setup and have a c2750 based atom processor running my FOG virtual machine. I only have 2 test images, each around 1G.

I found that when I downgraded to version 6753, the high cpu usage disappeared. 6755, 6757 and up all produced the issue.

The next git commit has this in the log.

Author: Tom Elliott <tommygunsster@gmail.com>
Date:   Wed Mar 16 00:42:03 2016 +0000

Ensure variables are set even on initial startup (init.php).

git-svn-id: https://svn.code.sf.net/p/freeghost/code/trunk@5027 71f96598-fa45-0410-b640-bcd6f8691b32

Hope that helps!

-baggar11

Sorry guys! I have been rolling the dev version for so long without issue, I totally forgot about the startup services possibly being an issue. I’m all set now. Here’s what I did.

Ran this on each service

sudo update-rc.d FOG*service* disable

Then, as suggested, added these line to my rc.local

sleep 5
service FOG*service* start

Wanted to post another update. Updated to 6893 this morning. Removed my sleep and service stop commands from rc.local and rebooted. CPU seems to be in check again. Thanks for all your hard work!

@Tom-Elliott said:

@baggar11 Okay, I’ve added a sleep time of 10 seconds, just in case of these situations where the int returned is 0. We must have at least 1 second sleeptime ( I believe ), and this just isn’t happening.

The only word of caution I can think of, now, is while this might help with CPU Cycles, it will not make the FOG Services actually work properly as from Ubuntu’s standpoint the service is already running. While I could, potentially, come up with a way to restart the services more appropriately, I don’t know where to start at the moment.

I’m not a coder so take this with a grain of salt. The following is a similar approach to another open source project I use.

Make a script to run as a cron job every 5 minutes. On 1st boot, the script essentially checks for things like MySQL and network being up, and if all checks out starts the FOG services. All other times it runs, it would really only check for FOG services running and then exit. heh…

Of course, it’s probably a waste of time as I assume systemd will probably take care of these things more intelligently than regular init and/or upstart. Which Fedora is already using and Ubuntu’s next LTS will be running.

I really appreciate you taking a look into these things Tom. FOG is a very cool project.

@Tom-Elliott said:

@baggar11 as I understand it, this is still potentially due to starting the services before its dependencies have started. This is different from the pegged on update, I think.

Can you simply try reinstall and see if it’s still happening? Or did update always work, only reboot caused these issues?

For my upgrades, anything after 6753 would peg my cpu after a reboot. During and after the upgrade process using the install.sh, everything was fine. It’s only after the reboot that the services would max out the cpu. Probably the infinite loop issue as you wrote about below.

@Tom-Elliott said:

@baggar11, @Raymond-Bell I believe I may have fixed this now.
With any luck, this issue will be gone now. Please update and let me know.

Just updated to 6795, removed my “restart” lines from rc.local and rebooted. CPU was pegged again. Restarting the services manually brought cpu back down to idle.

I just realized after going through another git pull upgrade that the CPU spike will probably happen every time since the services are reinstalled. Here’s how I fixed my problem again, hopefully in a cleaner way. After upgrading to 6791, it seems to be working so far with a couple reboot tests.

Add this to your rc.local. Adjust sleep time based on your setup. My FOG setup is virtual, so 5 seconds seems to work well.

sleep 5
service FOGImageReplicator restart
service FOGMulticastManager restart
service FOGPingHosts restart
service FOGScheduler restart
service FOGSnapinReplicator restart

Sorry guys! I have been rolling the dev version for so long without issue, I totally forgot about the startup services possibly being an issue. I’m all set now. Here’s what I did.

Ran this on each service

sudo update-rc.d FOG*service* disable

Then, as suggested, added these line to my rc.local

sleep 5
service FOG*service* start

One thing that I noted was interesting was after an upgrade, cpu cycles are normal. System is idling. FOG WebUI works fine, no issues.

Once I restart the virtual machine and the FOG services start up on boot, that’s when those 3 services start consuming all of the cpu.

@Tom-Elliott Uptime is now at 17 minutes and nothing has changed in CPU cycle regard.

@Tom-Elliott For a full view of processes, I gave an output of ps aux | grep FOG down below. These are the top 3 though.

FOGImageReplicator
FOGMulticastManager
FOGSnapinReplicator

@Tom-Elliott Here’s what I’m seeing after stopping all services, clearing the logs and then rebooting.

cat error.log 
[Wed Mar 16 16:10:53.258602 2016] [mpm_prefork:notice] [pid 946] AH00163: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g configured -- resuming normal operations
[Wed Mar 16 16:10:53.258795 2016] [core:notice] [pid 946] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 16 16:11:35.735081 2016] [:error] [pid 950] [client 192.168.10.15:53300] PHP Strict Standards:  Only variables should be passed by reference in /var/www/fog/lib/pages/dashboardpage.class.php on line 71, referer: http://192.168.10.14/fog/management/index.php