Categories

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

    @Tom-Elliott said in Login to delete image not passing correct username.:

    erent from the

    I have not changed this account on this…all I did was update to the latest version. Is there somewhere you can point me to where this can be updated properly?

    I tried to follow the instructions listed here, but this did not resolve the issue.
    https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

    I also looked inside the fogftp.class.php file but this looks like it probably pulls its data from the config.class.php file.

    I was able to ftp into the server using the credentials that are listed in the config files on the server and what is stored in the TFTP section in the GUI and the folder permissions on the ipxe folder appear to be correct as well. I have rebooted to see if there was cached information set somewhere, but not luck.

    f82ae984-ba72-40b9-bc2f-afdb125fd7e2-image.png

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

    FOG 1.6.0-RC-5 is available

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

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

    Upgrade to RC-5 if your schema update stopped at step 345. On MariaDB, a re-run of a failed schema update could stop there with error 1292. RC-5 fixes it.

    Changed since RC-4

    A schema update could stop at step 345 on MariaDB with 1292 Truncated incorrect DECIMAL value: ''. It now completes. (#1825) Pending MACs has a new Approve all matching button. It approves every pending MAC that matches your search and filters, on all pages, after a confirm dialog shows the count. (#1828, thanks to Coolguy3289 for #1826)

    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.

53

Online

12.8k

Users

17.7k

Topics

157.2k

Posts