Categories

  • 13k Topics
    115k Posts
    P

    Hi;

    Objective: Build a “standalone” FOG server environment i.e. one machine as the FOG server and three others as hosts of FOG tasks such as full wipes/capture/deploy I am trying to get the while screen so I can do a registration of a “target” machine. However I am getting the following error(s) instead which I cannot get past.

    **iPXE initialising devices…•

    autoexec.ipxe… Not found (https://ipxe.org/2d12618e)
    /autoexec. ipxe… Not found (https://ipxe.org/2d12618e)
    ASSERT c:tedk2\udk2010.sr1.x2\MdeModulePkg\Library\UefiHiilib\Hiilib.c(257): Hii
    Handle != ((void ж) 0)

    ASSERT_EFI_ERROR (Status = Not Found)
    ASSERT c:ledk2\udk2010.sr1.x2\MdeModulePkg\Library\Uef1H11L1b\H11Lib.c(259): IEF
    I_ERROR (Status)
    ASSERT c:sedk2\udk2010.sr1.x2\MdePkg\Library \BaseL ib\LinkedList.c(60): List 1= ( .(void ) o)*

    Reproduction Steps:

    Build FOG Server

    Perform a clean Ubuntu Desktop 26.04.1 installation (then reboot machine) Open UBUNTU App Centre and perform an Update All to ensure all applications are up to date (reboot machine) Run Firmware Updater to bring firmware up to date (reboot machine) Open terminal:
    execute sudo apt update && sudo apt upgrade -y
    execute sudo apt autoremove -y

    Reboot machine

    2)Install FOG
    Based on current installation instructions for FOG 1.5:
    Install git
    clone fog project from github
    run the ./installfog.sh bash script

    Try to register “target” machine
    Check BIOS for
    latest version
    UEFI boot enabled
    PXE boot enabled
    Set boot order so IPv4 and IPv6 are first in boot order

    Restart machine and hope for white screen to Register a Host. Get above error. Please note I have tried more flavours of the reproduction steps than Baskin Robbins has ice cream flavours e.g. with/without SecureBoot, DHCP, DNS, router even Ubuntu 24.04.5 and Ubuntu 26.04.1 all with the same errors on my host machine. I even broke down and did an RTFM of fog docs, wiki, and forums.

    Fog install log files:
    fog_error_1.5.10.2518.log
    foginstall.log

  • Get the latest news on what's happening.
    195 Topics
    836 Posts
    Tom ElliottT

    The tenth release candidate for FOG 1.6.0 is available on the rc-1.6.0 branch. It reports version 1.6.0-RC-10.

    Test it on a lab or non-production server first. The upgrade from 1.5 to 1.6 is one-way: it changes the database schema, and there is no down-migration.

    Changed since RC-9

    iPXE: boot no longer freezes on some UEFI firmware (forum 18271, #1857). default.ipxe read the SecureBoot and SetupMode EFI variables. On some older firmware that read never returns, and the host froze before the menu. The installer no longer writes those two lines. Run the update to rewrite default.ipxe. Hosts no longer report their Secure Boot state on PXE boot. FOS still reports it when the enrollment task runs. CSV import reads a file that FOG exported (GH-1851, #1855). “CSV (All)” starts the file with a UTF-8 byte-order mark. The import did not skip it, so it did not find the header row. It imported the header as a host, and the row failed with “No viable macs to use”. The import now skips the mark.

    Before you upgrade

    Back up your database and /opt/fog/.fogsettings. Read the release notes: https://github.com/FOGProject/fogproject/blob/rc-1.6.0/docs/release/1.6.0-release-notes.md 1.6 removes Display Manager, Directory Cleaner, User Cleanup, Client Updater, Green FOG and the persistentgroups plugin. Their data is dropped. The site and accesscontrol plugins move into core. PHP 7.4 or later is required. Plugins built for 1.5 do not load.

    Install or update (as root)

    A 1.6 beta or RC server: run 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 from the checkout. 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

    Report problems

    Open an issue at https://github.com/FOGProject/fogproject/issues. Include your FOG version, your OS, and the installer log from bin/error_logs/. Report a security problem through “Report a vulnerability” on the same repository, not in a public issue.

  • View tutorials or talk about FOG in general.
    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.
    2k Topics
    21k Posts
    Tom ElliottT

    @Paladin1 Thanks for the report. You’re right, the docs were out of date.

    The installer now asks Install/update the FOG database schema now? (Y/n) and does the schema update itself when you answer yes, which is the default. The browser step only applies if you answer no.

    The “Denied” you saw is expected on a new install. With no FOG users yet, the schema page only accepts the link the installer prints, which ends in &fogtoken=.... On an existing install, you log in as an admin instead.

    The install pages are updated for both versions:

    1.5: https://docs.fogproject.org/en/latest/1.5/installation/server/install-fog-server/ 1.6: https://docs.fogproject.org/en/latest/1.6/installation/server/install-fog-server/

73

Online

12.8k

Users

17.7k

Topics

157.2k

Posts