@Greg-Plamondon
Please see:
https://news.fogproject.org/fog-client-v0-11-4-released/

0.11.4 now downloads from the storage node if locations are setup.

@coco65 There’s been research in the area of FOG’s compression and delivery times.

The conclusion - 5 to 7 is best.

Read here:
https://wiki.fogproject.org/wiki/index.php?title=Image_Compression_Tests

@Tom-Elliott said in Page timeout when creating multicast task:

This, for now, does mean multicast from groups will not generate the requisite snapin taskings, but it’s only because I need to think of the logic to enable it. It should work hopefully soon.

I’ve been learning about triggers in mysql. It’s really super efficient, you could do all the snapin stuff from deployment with triggers.

Sorry it took so long.

I messed with it quite a lot tonight, and am fairly confident all of the issues (yes there were more than just the OSID issue) of Capone have been patched and appear to be working properly now.

Please update and test, and keep us informed. Thank you,

For a scratch installation, there are literally only 2 extra steps.
https://forums.fogproject.org/topic/7131/fog-on-ubuntu-16-04-php7/27

If MySQL users were messed up, your web interface wouldn’t work. FOG doesn’t setup a ‘fog’ user for MySQL. Typically it uses the root user without password to access MySQL if you’ve not manually defined a user/password in MySQL.

I doubt it’s permissions. It could be a corrupted image - but if that’s the case, it’s likely that the server HDD is dying or underwent a sudden power loss.

What’s stopping you from making a new image and trying that?

@Tom-Elliott you genius

Yes, I was copying files which I captured manually. Your three suggestions, to

temporarily disable replication, not create the image definition,
or use the dev folder

all work, and I’m not sure why I didn’t think of that… #facepalm

@Wayne-Workman thanks, I was meant to say that I had been through that article after searching the forums and finding similar posts.

I also rebooted the server and also tried again after updating, I know it doesn’t really help us in finding what went wrong but I ended up rolling back my FOG VM a few days (both master and node was able to deploy after this). I then updated the master to the latest (to match the storage node) and both are able to deploy images.

thanks again

@Bob-Henderson If you update, we think the bandwidth graph is fixed.

And, it’s fine - I was lost in outer space for months when I started messing with fog. I think I still am sometimes.

@BardWood do you have a hub (as opposed to a switch)? I’m just asking, because there’s something you can do to help solve this.

Have you tried it with a different mechanical HDD? I’ve had hard drives fail right after chkdsk /F /V /R /X reported that there are no errors or bad sectors.

Nvm, I tried another kernel, Version : 4.1.2 and it worked.
Case closed

@Sebastian-Roth
Yes, very much under time pressure in the business at the moment… I had to rebuild another Fog server… and I uploaded my 2 main images onto it manually… so I didnt use any of the backup procedure.
This is all a consequence of being forced by company circumstances to run things into production without any testing time…
the joy of decisions being made above your head and you just being told to get on with it!

@dolf Perhaps this deserves a video.

@Wayne-Workman The problem has been solved. Thanks.

@mabarton I briefly went over this thread because it’s been a while. Have you individually tried every EFI exit type?

I’m on Ubuntu 14.04 though…
Anyway, it’s working with php5.

@Joe-Gill Great job. Boo @Microsoft. Booooo

@jayrob86 this is where it gets a bit complicated if you want to reverse engineer stuff.

The post download scripts are saved on the FOG server, but they are executed by the FOS engine (the linux operating system that captures and deploys images to the target computer).

So to answer your question, the function.sh script is in the init(s) (virtual hard drive that is downloaded to the client along with the kernel (bzImage) when pxe booting).

So you next question may be how can I peek into the inits? There is a wiki for that: https://wiki.fogproject.org/wiki/index.php?title=Modifying_the_Init_Image

The file is in /usr/share/lib/fog (or something like that, its in /usr/share…)