• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • F

      Fog 1.6.14 Driver Replication Issue

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      17
      0 Votes
      17 Posts
      323 Views
      F

      @Tom-Elliott now it is showing

      [11-13-26 8:30:16 pm] * Starting Image Replication. [11-13-26 8:30:16 pm] * We are group ID: 8. We are group name: Nashport Storage Group [11-13-26 8:30:16 pm] * We are node ID: 13. We are node name: TVNE-Fog [11-13-26 8:30:16 pm] * Attempting to perform Group -> Group image replication.

      Replication seems to be working now. After replication completed I restarted the service and nothing was recopied.

    • T

      IPXE boot no longer works after upgrade to 1.6. Error code 0216eb

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      12
      0 Votes
      12 Posts
      474 Views
      T

      @Tom-Elliott

      Hopefully I’ll have the answer to that question within the next two weeks!

    • F

      FOG Server : Certificate validation failed

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      12
      0 Votes
      12 Posts
      414 Views
      Tom ElliottT

      @fgaudin Good to hear it works.

      UEFI alone does not need secureboot=1. The setting is only for computers that have Secure Boot turned on in the firmware. With secureboot=0, FOG does not sign its boot files, and a computer with Secure Boot on refuses to boot them.

      If Secure Boot is off on your computers, keep secureboot='0'. If Secure Boot is on, set secureboot='1' and run ./installfog.sh -y. Do not use -C or -K. Each computer then enrolls the FOG key one time at its first PXE boot.

      Install sudo before you set it to 1. The Secure Boot signing helper needs /etc/sudoers.d.

    • F

      Fog 1.6 Multiple Sites, Location not working as intended

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      12
      0 Votes
      12 Posts
      458 Views
      F

      @Tom-Elliott All good! Thank you and keep up the awesome work!

    • rogalskijR

      LDAP broken since upgrade to 1.6

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      9
      0 Votes
      9 Posts
      307 Views
      Tom ElliottT

      @rogalskij Glad to be of help and your finding did notice an issue that was also addressed on the dev-branch so thank you!

    • G

      PHP Vulnerability Question

      Watching Ignoring Scheduled Pinned Locked Moved General
      9
      0 Votes
      9 Posts
      784 Views
      Tom ElliottT

      @Dominique I can’t promise that, no.

      1.5.10 is the original release, and it is a long way behind now. It was built and tested against PHP 7.x. It may run fine on PHP 8, but I don’t know which PHP 8 version, if any, would be safe for it.

      What we do know works on PHP 8 is the current stable branch. Here is how the branches fit together:

      master is the official 1.5.10 release. We don’t work on it directly. dev-branch is where all the bug fixes and maintenance happen. stable gets everything from dev-branch rolled into it once a month.

      So stable is 1.5.10 plus a few years of fixes, PHP 8 support among them.

      If you want to move to PHP 8 before 1.6.0 comes out, I’d do it in this order:

      Snapshot the server first, so you can roll back. Update FOG to the stable branch and run the installer. Do this while you are still on PHP 7.2. Then move PHP to 8.2. On Red Hat 8 the installer will not do that for you; it installs whichever PHP module is enabled. Run dnf module reset php then dnf module enable php:8.2, then dnf distro-sync. Re-run the FOG installer, so it picks up the new PHP packages. Test the web console, a host registration, and a unicast and a multicast deploy before you call it done.

      Since this is production, your plan to wait for 1.6.0 and try the RC in a test environment first is a good one too.

    • F

      1.6 upgrade: /etc/exports overwritten, captures stuck in /images/dev (SSH on non-standard port)

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      7
      0 Votes
      7 Posts
      273 Views
      F

      @Tom-Elliott Hey Tom, updated to 1.6.0.97 this morning and everything checks out:

      Exports: migrated to /etc/exports.d/fog.exports, and my kubuntu.exports came through untouched.
      SSH keys: fog@fogger key landed in authorized_keys, works on my custom port. Pulled the Match password exception, so the box is key-only again.
      Dashboard: 1.5 history is back, and the Nov 3 runs are on Nov 3 now.
      Capture: new capture shows local time, no asterisk, and moved out of /images/dev over the key with no errors in the log.
      Ports: FOG_SSH_PORT now shows up under FOG Settings → General Settings with my port, and the per-node fields are blank, so it falls back to that.

      Seriously impressive turnaround. Thanks for taking the reports seriously and running with them!

    • P

      Access denied: Master node

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      7
      0 Votes
      7 Posts
      370 Views
      Tom ElliottT

      @piaFOG26 Are you able to confirm if things are now working for you?

    • S

      FOG Server 1.6 Fails to install Secureboot certificates with Custom CA and Secure Boot keys?

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      7
      0 Votes
      7 Posts
      294 Views
      Tom ElliottT

      @Shuttleu Thank you for testing on the HP. That confirms the fix on real firmware.

      The task error after a menu enrollment. This is a FOS bug, not the agent. The menu item runs the enrollment with no task scheduled. When the enrollment finishes, FOS tries to close the task. The server answers “No Active Task found”, and FOS shows an error. The enrollment itself succeeded. The fix is in FOS release 20261106-134043. After a menu run, FOS now says that no task is scheduled and ends normally. The server records the enrollment on the host only when you schedule the task from the web UI.

      FOG Agent. You found the cause. Uninstall keeps C:\ProgramData\FOG on purpose. It holds the machine’s key, its certificate and the trusted CA, so a reinstall keeps the same identity. The reinstall kept the CA of your earlier server, so every connection failed and the token was never used. Agent v0.1.21 fixes this. Setup now checks the stored trust against the server. If it no longer verifies, setup settles trust again like a first install, and the host enrolls again with the token. Until you install v0.1.21, deleting C:\ProgramData\FOG before the reinstall is the right workaround.

      Your server certificate comes from your company CA, which Windows already trusts. So no fingerprint is needed, as the probe said. Leave CAFINGERPRINT out on these machines.

    • S

      FOG 1.6.0.127 — efitools unavailable on Oracle Linux 8 and Secure Boot signing failures

      Watching Ignoring Scheduled Pinned Locked Moved Solved Bug Reports
      5
      0 Votes
      5 Posts
      142 Views
      Tom ElliottT

      @sgennadi Thanks for the write-up. It matches what I found. --addcert first appears in sbsigntools 0.9.4, so 0.9.4 is the minimum. EPEL 8 ships 0.9.2, so this affects every EL8 install, not only Oracle Linux. The Rocky Linux Core SIG package you used is a good way to get a newer version.

      A dev-branch change (PR #2081) makes the installer test for --addcert before it signs. When the option is missing, the installer now names the required version instead of printing a bare “Failed”.

    • R

      Hp z secure boot not booting into windows

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      5
      0 Votes
      5 Posts
      336 Views
      R

      @Tom-Elliott sorry tom yes i am, sorry for the late reply, tbh i think its just hp machines that do this

    • S

      1.6.0.14: Web UI not staying signed in?

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      4
      0 Votes
      4 Posts
      133 Views
      S

      @Tom-Elliott Thank you once again for the amazing support and turnaround.

    • F

      Fog 1.6.0.14 Master Storage Node not handing off to Slave Storage Nodes

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      4
      0 Votes
      4 Posts
      126 Views
      F

      @Tom-Elliott Okay, thank you for the information.

    • F

      1.6 after upgrade: dashboard imaging chart shows 0 for all runs, and Captured times flagged UTC

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      6
      0 Votes
      6 Posts
      250 Views
      F

      @Tom-Elliott All is working now

      Hey Tom, updated to 1.6.0.97 this morning and everything checks out:

      Exports: migrated to /etc/exports.d/fog.exports, and my kubuntu.exports came through untouched.
      SSH keys: fog@fogger key landed in authorized_keys, works on my custom port. Pulled the Match password exception, so the box is key-only again.
      Dashboard: 1.5 history is back, and the Nov 3 runs are on Nov 3 now.
      Capture: new capture shows local time, no asterisk, and moved out of /images/dev over the key with no errors in the log.
      Ports: FOG_SSH_PORT now shows up under FOG Settings → General Settings with my 2416, and the per-node fields are blank, so it falls back to that.

      Seriously impressive turnaround. Thanks for taking the reports seriously and running with them!

    • W

      [1.6.0-beta.5547] Uploading Snapin fails with 500

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      4
      0 Votes
      4 Posts
      503 Views
      W

      @Tom-Elliott Thanks fo the quick reply!
      I did rerun the installer today and it seems to be working now, thanks a lot for the quick feedback and fix!

    • L

      1.6.0.14: "Create new tasking" modal hangs on "Loading, please wait..." if the host has no image

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      0 Votes
      3 Posts
      83 Views
      Tom ElliottT

      @lperoma The fix is now in stable release 1.6.0.158. Update to it, and a refused task shows its reason in the modal instead of hanging on “Loading, please wait…”.

    • R

      "Detected a web certificate managed outside FOG"

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      3
      0 Votes
      3 Posts
      147 Views
      R

      @Tom-Elliott As always, thanks for the answer and quick fix 😊

    • DBailey635D

      Can you apply an image to all hosts within a group in v1.6?

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      191 Views
      DBailey635D

      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.

    • DBailey635D

      Laptops not PXE booting on clean install of v1.6.0-RC-14

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      3
      0 Votes
      3 Posts
      237 Views
      DBailey635D

      @Tom-Elliott

      Thank you!

      As you thought, it was a double DHCP server… Even though .6 was in bridge mode, the DHCP server on it was still enabled, unlike the other MikroTik switches we have. Disabling it brought the iPXE booting back. I’ve run a re-inventory task and am now running an image capture task.

      I’ll have to keep a future eye open for that as we expand our classroom network.

      Cheers!

    • F

      1.6.0.167 Time wrong in logs

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      30 Views
      Tom ElliottT

      @FlareImp yes, this is expected.

      All times are stored in UTC for consistency now and translated to whatever time is configured (by default) and each user can define their own timezone if they want it.

      https://docs.fogproject.org/en/latest/management/web/unadjusted-timestamps/

    • 1
    • 2
    • 3
    • 1 / 3