Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    13k Topics
    115k Posts
    S

    @Tom-Elliott Fog server has not been working since this entire thread was created… it’s not working.
    So far the database has refused to update and the web management console is 100% unavailable since the only thing it does is prompt me to update the database.

    Tried the manual update with
    sudo curl -X POST -H “X-Fog-Install-Token: 14dbb4a059bc201b2bf585b625087f92f4b5f8fd6dc70de8a0bef17845f00321” -d “schemaupdate=1” “http://10.46.10.40/fog/management/index.php?node=schema”

    but it responded with
    {“error”:“Unable to update schema”,“title”,“Schema Update Fail”}

    Here’s some data you requested earlier
    ebea6aea-521d-4527-aede-c586a08d8821-image.png

  • 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!

  • View tutorials or talk about FOG in general.
    General Tutorials
    2k Topics
    19k Posts
    8

    @Cpasjuste

    Thank you, I appreciate that. And yes, I did spend a lot of time on it.

    I agree that it bypasses the official installer in order to make use of Docker environment variables; however, at this stage, I don’t believe that FOG is going to change so dramatically that it’ll break it often.

    I will add that if this could get adopted as an official docker image, we could work with the FOG team to make sure nothing gets to pushed to the FOG code that would break the container until we can adjust the container as well.

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    Tom ElliottT

    @Valer Thanks for the report and the writeup, that’s a good catch. You’re right about the cause. Debian 13 dropped the sysv-rc-conf package since it’s fully on systemd now, so the installer chokes trying to apt-get it. We never actually use that tool on a systemd system anyway, it only ever got called on the old non-systemd paths, so it was just dead weight on Trixie.

    I pushed a fix to working-1.6. It leaves the package off the list on Debian 13 and up, and it also strips it out of a cached .fogsettings so an in-place upgrade doesn’t drag it back in. Older Debian keeps installing it like before so nothing changes there.

    If you want to get moving before you pull the update, you can either grab the latest working-1.6 and rerun the installer, or just open /opt/fog/.fogsettings and delete sysv-rc-conf from the packages line, then run the installer again. Either one gets you past it.

    Let me know if you hit anything else on Trixie.

113

Online

12.7k

Users

17.6k

Topics

156.8k

Posts