@Gary-Kulovics said in Amount Fog can image:

Any answer on how to change at the main fog menu boot to hard drive from 5 seconds to a different time

Web Interface -> FOG Configuration -> iPXE Boot Menu -> Menu timeout

And, You never responded to me from your Multicast problem thread:
https://forums.fogproject.org/topic/8106/multicast

I can confirm that updating to fog 1.3 helped 🙂

@Wayne-Workman sure! Thanks for your help!

@Wayne-Workman said in Which table to check in db to see if there are pending wakeup entrys:

quote

How is the payment and which country is it? I have attachment with me 😄

@Stilty Re-downloaded cleanly??

@Wayne-Workman

Ah, so that’s what you were basing that question on. I was really just very confused about why you were on about disk space, now that makes sense.

@Tom-Elliott

Interesting. I am fairly sure it was working before the latest git pull, so I’m not sure where the init image I’m looking at came from. I will update the init image, but I do wonder now what else might not have taken since the update. Perhaps it is time to rebuild that server.

Thank you all for your help.

Thanks, Wayne!

@Tom-Elliott Thanks! this did the trick. WOL to groups is now working, but the apache log is spitting out this error now.

[Thu Aug 11 07:17:07.370532 2016] [:error] [pid 32376] [client 10.100.150.44:64341] PHP Warning: array_count_values(): Can only count STRING and INTEGER values! in /var/www/html/fog/lib/fog/fogmanagercontroller.class.php on line 111, referer: http://fog/fog/management/index.php?node=group&sub=edit&id=1532

Fairly sure this is fixed now. I don’t know why the hashes were all sorts of strange, but I believe this was partially related to the timeout as seen https://forums.fogproject.org/topic/8278/rc6-snapins-no-longer-working/13.

With any luck, this was all it was, and I’m just going to guess what was seen from the start was from a download that timed timed out, while the hashing mechanism was able to run much faster and return within its own allotted time.

@tmerrick client log before it’s deleted, please.

@Wayne-Workman

That worked.

@dolf The one marked as the answer. We keep the FOG Client article updated, because it’s important.

@Tom-Elliott One more you can clean up:

rm -rf error_log-20160807

Marking this as solved.

The spikes aren’t that big (50Mbps). These are most likely clients that are booting up and are passing through network boot first, the spikes are them pulling the boot ROM from the fog server.

The OP’s problem can be solved with the location plugin in FOG 1.2.0, and FOG 1.3.0. Documentation on the plugin are linked below. Marking this thread as solved.
https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

The OP’s problem is almost surely a simple FTP credentials mis-match, this was common in FOG 1.2.0. Instructions on fixing it can be found here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

Marking this thread as solved.

Cool, thank you so much. I love everything about FOG and how it handles, however I can’t stand the white background, so I changed that to black, and now I’m wanting to change the font color to something a little easier on the eyes. Thanks again!

@Tom-Elliott typing error, Now it works. Client updated to 0.11.5 a few second after installing svn.

@Wayne-Workman

All right I got. The lines:

DELETE FROM multicastSessions WHERE 1;
DELETE FROM multicastSessionsAssoc WHERE 1;

returned syntax errors “check your manual”. but truncating the two tables worked.

everything seems to work normally now. 🙂 thanks, guys.