Categories

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

    @jmeyer This is a bug in schema step 284 on MySQL. Your data did not cause it.

    Cause: on MySQL, an ALTER TABLE re-checks the default of every column. Your hosts.hostSecTime still has the old default 0000-00-00 00:00:00. MySQL’s default sql_mode (NO_ZERO_DATE) refuses that default, so the step stops. MariaDB servers do not show the problem.

    Fix: https://github.com/FOGProject/fogproject/pull/1838 is merged into dev-branch. While the steps run, the schema updater now relaxes the zero-date check for its own session.

    The fix reaches the stable release on October 11. To continue now, install from dev-branch:

    cd /root git clone -b dev-branch https://github.com/FOGProject/fogproject.git fogproject-dev cd fogproject-dev/bin ./installfog.sh -y

    The failed step changed nothing in your database, so you do not need to restore the backup. The backup the installer made is still at /home/fogDBbackups/fog_sql_1.5.10.2482_20261009_113907.sql.

  • Get the latest news on what's happening.
    Security Advisories
    190 Topics
    831 Posts
    Tom ElliottT

    FOG 1.6.0-RC-6 is available

    The sixth release candidate for FOG 1.6.0 is on the rc-1.6.0 branch. It reports version 1.6.0-RC-6.

    Release page: https://github.com/FOGProject/fogproject/releases/tag/1.6.0-RC-6

    Changed since RC-5

    iPXE Menu: setting “Show with” to Not Registered Hosts failed with “Menu update failed!”. It now saves. (#1832, thanks to Sempyos for #1830) A failed menu save could leave the boot menu with no default item. Default Choice is now changed only after the save succeeds.

    Update (as root)

    A 1.6 beta or RC server: bin/updatefog.sh --channel rc from your FOG checkout. A 1.5 server installed from git: update to the current 1.5 stable, then run bin/updatefog.sh --channel rc. A new server, or a 1.5 server installed from a tarball:
    curl -fsSL https://raw.githubusercontent.com/FOGProject/fogproject/working-1.6/bin/bootstrap.sh | bash -s -- --channel rc

    Test on a lab or non-production server first. The upgrade from 1.5 to 1.6 changes the database schema, and there is no way back. Back up your database and /opt/fog/.fogsettings before you upgrade.

    Report problems at https://github.com/FOGProject/fogproject/issues with your FOG version, your OS, and the installer log from bin/error_logs/.

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

    @Cpasjuste I just wanted to let you know that I’ve added in your method of using userland NFS support to my container. I have given you credit for the method in the README. I’d love for you to test it out if/when you get a chance. Thank you again for your work!

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

    This is a bug in the version check on 1.5.10.2482, not in your install. Your version is current, and you can ignore the banner.

    The check takes the first tag in GitHub’s tag list as the latest stable release. Newer tags (an archive tag and the 1.6.0 release candidates) now sort ahead of 1.5.10.2482, so every stable install shows this warning.

    The fix is merged to dev-branch (https://github.com/FOGProject/fogproject/pull/1823). It asks fogproject.org for the current versions instead. It ships in the next stable release.

64

Online

12.8k

Users

17.7k

Topics

157.2k

Posts