Subcategories

  • General Developer questions relating to FOG.
    382 Topics
    5k 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

  • Request a new feature to be implemented.
    626 Topics
    4k Posts
    R

    @JJ-Fullmer Dear Fullmer, thanks in advance for your intervention.

    Unfortunatly in the machine that run my fog container there is another mysql database listen on port 3306.
    This is not a problem, i just semi-resolved creating a non-privileged/shared network host mysql container with no exposed port -> place fog container and this database container in a same network (they can ping each other with fqdn) and i’ve just modified the /opt/fog/.fogsettings with your suggestion in the past, but the solution doesnt work:
    The installation goes fine, but the result is a blank http page that it say: database error. (something like that).
    I think (but is only supposition, im not absolutly a developer) that there is written php scripts that must to be point to a localhost database (something in /var/www/html/fog/*).

    This problem is born because the fog container must be in privileged mode, with the same network namespace as the host, and in this host there is another database already.

    Thanks for confirm me the inevitable death of the container version of fog. it really hard to containerize this application without setting privileged mode and/or share the host network. and the huge problem of systemd processes make this containerizzation very difficulty to maintain.

    Thanks for the patience

  • Report a bug with FOG.
    1k Topics
    12k Posts
    F

    I’m having the exact same behavior.
    Was working on the 27, 28 and 29.

    Stopped working start of this week (2 september)
    Added 3 storage nodes in between.
    1a07ba58-be68-4007-a60c-5532e6c42e41-image.png

78

Online

12.2k

Users

17.4k

Topics

155.6k

Posts