Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  13k Topics

  115k Posts

  T

  @piaFOG26 One more item, about the “Access Denied” in the disk usage box on the VM dashboard.

  Your VM and your master node are two full FOG servers, and each has its own database. The master node only trusts requests from the storage nodes in its own database, so it refuses the VM. I fixed this in FOG: a request signed with a shared node key is now accepted. The fix is on dev-branch now and reaches the stable release on November 11.

  To use it, both servers must have the same key. First, finish the schema update on the master node. Then:

  Make a key on either machine: openssl rand -hex 32 On the VM, open Storage Management, then edit the master node (NComun). Paste the key into Node API Signing Key and click Update. On the master node, run this from the fogproject folder you installed from: sudo php bin/fog-node-key.php --set <the same key>

  If you need it before November 11, install dev-branch on the master node. The fix must be on the master node, because that is the server that checks the key.

• Announcements

  Get the latest news on what's happening.

  Security Advisories
  199 Topics

  840 Posts

  T

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

  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-13

  Multicast: canceling one host no longer cancels the whole session (#1903, #1905, #1909). Before, a cancel on one host stopped udp-sender and canceled every host in the session. Now only that host leaves. When every remaining host has connected, the session starts at once, without the max-wait. The FOS receiver also gives up after the session’s max-wait when no sender answers. That half is in FOS EXP_20261019-150930, which the update installs. Secure Boot: the PXE menu enrollment is recorded (#1869, #1899). The Enroll Secure Boot Key menu item opened MokManager, and the host page still showed no enrollment. The server now records mok-pending when it serves the key. The host page tells you how to confirm it. Group create form: the dead boot fields are removed (#1901). Group Kernel, Group Kernel Arguments, Group Init and Group Primary Disk were saved and never used. To set these on many hosts, use Edit selected hosts on the Hosts list. Tab titles in non-ASCII languages (#1910). After sidebar navigation, a Japanese or Chinese tab title was garbled. It now matches a full page load. Japanese translation is complete (#1910, #1913). Every message is translated. Uptime no longer shows an English plural s after a translated unit, such as 日s.

  Thank you to @mashiro-mikage for the tab title fix, the Japanese translation, and the uptime fix.

  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.

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  D

  Thanks @Tom-Elliott . That actually makes a lot more sense now. 😁

  I saw the greyed-out “Mass edit” button, but hadn’t worked out that I had to select multiple items (turn them blue) from the filtered list of hosts in order to be able to use that button to set values across multiple entries. Once I did, it worked as intended.

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  T

  @delacroix fixparts went missing from FOS during a Buildroot update. The fix (fos#195) landed yesterday, and the first build with it is EXP_20261021-160109. I checked that release: /usr/sbin/fixparts is present in init.xz, init_32.xz, and arm_init.cpio.gz.

  Your debug task boots the init that your FOG server serves, not the one you downloaded. Put the new file in place on the server:

  cd /var/www/html/fog/service/ipxe mv init.xz init.xz.old wget https://github.com/FOGProject/fos/releases/download/EXP_20261021-160109/init.xz sha256sum init.xz

  The hash must match the init.xz.sha256 on the release page (it starts 8e3457ad4268add5). To check the content without a boot:

  xz -dc init.xz > /tmp/init.img debugfs -R "ls -l /usr/sbin" /tmp/init.img | grep fixparts

  Then run the capture again. If fixparts is in that listing and the capture still fails, please post the output of fixparts /dev/sdX (or /dev/nvme0n1) from a debug task.