Categories

  • 13k Topics
    115k Posts
    R

    hi all,

    trying to install fog 1.6 on ubuntu 24.04 but i get this error on the install script

    the exact version im trying to install is

    https://github.com/FOGProject/fogproject/archive/refs/tags/1.6.0-RC-10.tar.gz

    Starting and checking status of web services................Failed! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! The installer was not able to run all the way to the end as !! !! something has caused it to fail. The following few lines are !! !! from the error log file which might help us figure out what's !! !! wrong. Please add this information when reporting an error. !! !! As well you might want to take a look at the full error log !! !! in /tmp/fogproject-1.6.0-RC-10/bin/error_logs/fog_error_1.6.0-RC-10.log !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ├─87893 "php-fpm: pool www" └─87894 "php-fpm: pool www" Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: Starting php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager... Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: Started php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager.

    and when i look at the log

    AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message Syntax OK Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xeu apache2.service" for details. × apache2.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2026-10-14 12:57:09 UTC; 59ms ago Docs: https://httpd.apache.org/docs/2.4/ Process: 87882 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE) CPU: 51ms Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: Starting apache2.service - The Apache HTTP Server... Oct 14 12:57:09 lon-c-clonezilla01 apachectl[87885]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message Oct 14 12:57:09 lon-c-clonezilla01 apachectl[87885]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 Oct 14 12:57:09 lon-c-clonezilla01 apachectl[87885]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80 Oct 14 12:57:09 lon-c-clonezilla01 apachectl[87885]: no listening sockets available, shutting down Oct 14 12:57:09 lon-c-clonezilla01 apachectl[87885]: AH00015: Unable to open logs Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: apache2.service: Failed with result 'exit-code'. Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: Failed to start apache2.service - The Apache HTTP Server. ● php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager Loaded: loaded (/usr/lib/systemd/system/php8.3-fpm.service; enabled; preset: enabled) Active: active (running) since Wed 2026-10-14 12:57:09 UTC; 22ms ago Docs: man:php-fpm8.3(8) Process: 87895 ExecStartPost=/usr/lib/php/php-fpm-socket-helper install /run/php/php-fpm.sock /etc/php/8.3/fpm/pool.d/www.conf 83 (code=exited, status=0/SUCCESS) Main PID: 87883 (php-fpm8.3) Status: "Ready to handle connections" Tasks: 6 (limit: 37986) Memory: 11.8M (peak: 12.3M) CPU: 89ms CGroup: /system.slice/php8.3-fpm.service ├─87883 "php-fpm: master process (/etc/php/8.3/fpm/php-fpm.conf)" ├─87890 "php-fpm: pool www" ├─87891 "php-fpm: pool www" ├─87892 "php-fpm: pool www" ├─87893 "php-fpm: pool www" └─87894 "php-fpm: pool www" Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: Starting php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager... Oct 14 12:57:09 lon-c-clonezilla01 systemd[1]: Started php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager.

    let me know

    thanks,
    rob

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

97

Online

12.8k

Users

17.7k

Topics

157.2k

Posts