Topics created by cammykool

@cammykool OK based on the picture and the “Boot to FOG” message I see you are using dnsmasq and its at least running. Please post the dnsmasq config file here. If the config file looks good, then we will perform a packet capture of the dhcp process to see what the target computer is being told to do.

@cammykool said in Unable to restore GPT partition tables on one image:

this is the stuff that broke after that init move.

That has nothing to do with the init change. The version information in the FOG web UI is pulled from the fogproject.org server and I would guess either there was a connection issue or your network admin restricted access to this URL.

@quazz said in Fog/dnsmasq and EFI booting:

SecureBoot must be disabled for EFI

i…

That was it. I feel like an idiot! thank you!

@george1421 said in FOG image drive failed. What now?:

@cammykool This image error is related to the php code. Apache off load php (the language the web ui is written in) to php-fpm (dedicated php execution engine). The error you see is apache saying that php-fpm did not answer it was done with the task in time so apache timed out.

There may be some clues to what is at fault in /var/log/php-fpm/error.log tail that and see if it tells you what its not liking. If you set the permissions of 777 on /images nothing should stop it from moving files.

i had my coworker crack away at it. He got them all to delete and we are in good shape! Everything seems to be working and happy!

@cammykool I would search for bonding and your linux distro. Bonding or teaming (depends on which method you use) is setup at the OS level. You will also need to get with your infrastructure folks to setup the switch the fog server’s plugged into for bonding. I would suggest LACP also called 802.1ad. Both the switch and the server needs to be configured for the same bonding type. When you setup bonding on the linux side, it will create a new network adapter typically called bond0. That virtual network adapter will then talk to its slave interfaces (the real physical nics). You will apply the IP address to the bonding nic and not the physical nics. The bonding driver will manage the physical interfaces once its setup. When you configure FOG you will tell it to use bond0 (or what ever the bonding interface name that is created). Once you have bonding setup and WORKING at the linux level then you can forget about it and install FOG. Don’t install FOG without or before bonding setup.

@cammykool It can do remote execution, printer management, power management, login recording, and other things. I’ve used it to run scripts, deploy software, and other things. Check out these wiki articles below, they might help you understand the capabilities.

There’s also a ton of stuff on the forums about printer management. Here is one with some detail: https://forums.fogproject.org/topic/8051/printer-deployment?page=1 though there’s probably hundreds of topics about printers.

@cammykool Is this topic still being discussed or done? From what I see in the PCAP the PXE boot cannot work. No servername (next server) given, two DHCP answers that might confuse the client…