Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  12.3k
  Topics
  113.4k
  Posts

  G

  @Donutsrule5

  OK lets see if we can boot from a usb drive. This tutorial will instruct you on how to build a usb boot image. https://forums.fogproject.org/post/69606 the google drive link below will take you to step 7 in the thread.

  https://drive.google.com/file/d/1psCrPVzBTvlakLkCMvhdoScAEZp1CKE6/view?usp=drive_link

  Once you build the usb boot drive, take the kernel and init.xz from your current version of fog and replace the ones on the flash drive with the ones in from the FOG server. The files are in /var/www/html/fog/service/ipxe directory.

  Once you have the usb drive ready, pxe boot into the grub menu on the flash drive, then go into debug mode. After several pages of text you need to clear with the enter key you will be dropped at a fos linux command prompt. If you can get that far then fos linux is OK and the problem is probably with ipxe or the handoff between the two.

  If you want to image with the flash drive, schedule the task in the fog server BEFORE you usb boot and select option 1 from the menu. If you get it out of sequence you will get an error that says something about Null. Basically its saying you don’t have a task scheduled on the fog server so there is nothing to do. Lets see if we can get it to boot this way.

• Announcements

  Get the latest news on what's happening.

  Security Advisories
  184
  Topics
  825
  Posts

  A

  @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2.4k
  Topics
  18.5k
  Posts

  D

  I read that the LDAP plugin does not currently support 636 and certificate authentication but that article was from 2017. Have there been any updates to this? I prefer using LDAP to authenticate for imaging and management but the credentials are being sent in clear-text. I can always go back to disabling LDAP and setting up local users for all the techs and admins. Just wondering.

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2.3k
  Topics
  20.9k
  Posts

  N

  Hello,

  I’m running FOG 1.5.10 and have set up a global postdownload script at /images/postdownloadscripts/fog.postdownload. The script sends a Slack notification via webhook when a deploy finishes.

  The script is configured in the database (FOG_POST_DOWNLOAD_SCRIPT), and the file has correct executable permissions.

  However, the script is not being executed automatically after deploy, even though deploys complete successfully and show in the Active Tasks list.

  I have tried:

  Adding debug logs inside the script writing to /tmp/fog-post.log (only updates when running manually).

  Watching the PXE client console during deploy but don’t see any message about using the postdownload script.

  Confirming the global postdownload path is set correctly in the database.

  Verifying that no “Post Download Script” option exists per image in the web UI.

  What I need:

  Clear steps or checklist to verify why the postdownload script is not running automatically.

  How to confirm if the postdownload script is actually called by FOG after deploy.

  If there is any additional configuration required in FOG 1.5.10 to enable postdownload scripts.

  How to properly debug this issue (logs to check, commands to run).

  Any known issues or tips specific to FOG 1.5.10 regarding postdownload scripts.

  Thank you for your he