@sebastian-roth That took care of the problem.

Thank you all.

@brakcounty While I can imagine an upgrade to break things in rare cases I would not think this would happen for a service like ISC-DHCP which has been around for so many years. But hey, you never know. Everything is possible.

@JJ-Fullmer We provide the PrinterManagerHelper with ever release of the fog-client, e.g. https://github.com/FOGProject/fog-client/releases/tag/0.12.0

I know it’s not perfect and sometimes doesn’t provide all the information correctly. Though I don’t have real printers in my test setup and can’t work on this part much.

@sebastian-roth It’s beautiful!
Thanks for figuring that out!

@huecuva That is an interesting update for sure. I believe graphics cards have a bios of some sort and sometimes there’s some option rom boot option related to the gpu in the computer’s bios setting. It would make some sense for the graphics drivers to also update the bios or boot option roms on gpus.
What GPU’s do you have? GPU’s of the gtx 10xx series and newer have a ‘studio’ driver option that’s supposed to be the sort of ‘stable’ branch option. If your cards can use that, maybe using that as a standard could help if it’s not something you’re already doing?

@kdmiller45 Sounds as if the database update at the end of the capture task failed. Please run ls -al /images/dev/ on your FOG server and post output here.

@sebastian-roth I looked in the registry and I deleted the left over fog files, I got it to work after a little tinkering.

Ok, let’s call it quits. I just pushed a commit to the fos repo to add this patch to our build of partclone and add the ignore_crc parameter back to the scripts.

Marking as solved.

@chris-whiteley said in API Help:

The only thing I can’t figure out is how to make that host be associated with a SnapinID. For instance, I want it to be associated with a SnapinID of 1. How can I do that?

While I haven’t tested lately I would think you should be able to create a snapin association like this:

curl -X PUT -d '{"snapins":[1]}' http://x.x.x.x/fog/host/33/edit

Assuming the host you want to associate the snapin (ID 1) to has host ID 33. Don’t forget the API tokens in the call.

@kkthnxbb Thanks for posting the video. Looks like the crash happens exactly at the point where iPXE hands over to the Linux kernel. I stepped through the video and saw it showing ok for both bzImage and init.xz. While it could be a problem with the Linux kernel as well I would expect the issue to be in iPXE.

Do I get this right, migrating the VM from ESXi 6.5.0 to ESXi 6.7.0 fixes the issue for you?

Let’s try to go back to an earlier iPXE version. Which version of FOG did you use before 1.5.9? You can download older iPXE binaries on github using this URL: https://github.com/FOGProject/fogproject/tree/1.5.8/packages/tftp (just put in whichever version you had before, 1.5.8 or 1.5.7 or …). You don’t need to download all the binaries. Just grab ipxe.efi and put that into /tftpboot/ directory on your FOG server. Then boot up the VM again.

You might want to pay attention to the iPXE version string printed when it starts just to make sure the switch of the binary actually worked.

@danboid Thanks for you detailed write up on setting up FOG!

I just tried to edit the first post but I was denied. Could we ditch this rule please, at least for this post?

I didn’t know the forum has such a rule. @Tom-Elliott Do you know if it’s possible to allow editing own posts for users as well?

Here is another comment: We don’t suggest running the installer via sudo directly because the environment variables is different on some Linux systems (and can cause issues!) compared to switching over to the root user via sudo -i or sudo su -.

@kdmiller45
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Installing_-_Linux

@KenM I am sure it’s the fog-client trying to update but fails in every loop because of the run out code signing cert. Re-installing the new version should fix that.

@george1421 Thanks for the input!

I’m not looking to specifically put F2B in; I am putting in code to log to a file login failures and successes, then the SysAdmin can choose to setup a F2B jail based on that. I believe heavily in separation of responsibilities, so I will definitely look into writing a proper tutorial.

Do you think code for simply logging the login attempts would get merged?

@wmw509 Give the steps outlined by George a try but I can imagine this being caused by some fancy logic within the UEFI firmware. As George said FOG is not at all touching any firmware or boot settings… unless you have added post deploy scripts doing something special.

Here is another test: Schedule the deploy task as debug. When you get to the shell run efibootmgr command (don’t know if you need parameters or not from the top of my head) and take a picture of the output in screen. Now start the task with command fog and step through it. At the end run efibootmgr again, take a picture and compare/post here. Before you type reboot schedule another debug task for this machine and see if it PXE boots into it.

@MichMurray I cannot honestly tell if you’re trying to sell a different product or genuinely want to help the use in regards to vpn.

While fog uses different open source tools we use those tools for a specific reason. Adding vpn to the mix is a bit on the advanced side of things and would require a highly technical understanding of what one is doing from a security and bandwidth perspective.

We typically ban spam accounts and this feels like it is but also feels like it could be a genuine interest I. Assisting others.

Maybe that’s the point?

Sorry if I’m too harsh but you fit the bill in spammer ideology, by trying to spring back old posts with seemingly nice posts and the. The bait. Going to remove the link. Please be cautious moving forward.

@Chris-Whiteley The default for a current install of FOG is still 4.19.x series because that is the last / latest LTS version of the linux kernel. When the kernel developers release the next LTS version of the linux kernel (supposedly to be 5.10.x) then the FOG Developers will make that standard.

@Pingolin It’s probably a good idea to follow the things George lined out. Just want to add one question: Did you say yes or no to the installer question “Would you like to use the FOG server for DHCP service”?

If yes was selected then we better take this DHCP offline again as it might mess with your home setup.