• 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.0.14 Master Storage Node not handing off to Slave Storage Nodes

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      29
      0 Votes
      29 Posts
      438 Views
      F

      I set my Master Storage Node and 2 Slave Nodes to 3 clients each. I then imaged 9 computers and everything went smoothly. each Node was imaging 3 clients. This was on Fog Dev 1.6.0.195

    • F

      Fog 1.6.14 Driver Replication Issue

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      17
      0 Votes
      17 Posts
      478 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.

    • L

      Feature request: a way to handle USB Ethernet adapters shared between many hosts

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      12
      0 Votes
      12 Posts
      163 Views
      L

      @Tom-Elliott

      Quick update: we’ve tested PR #2111 and it works perfectly for us.

      Setup

      We also updated from 1.6.0.14 to 1.6.0.158 (stable). On top of it we applied #2100, #2104 and #2111 by hand (we skipped the schema 462 step, since it only changes a setting description). FOG_HOST_IDENTIFY_SMBIOS is set to register.

      Test (two Proxmox VMs)

      We moved the MAC of an already registered host onto a different machine. The machine with the different serial was not taken for the registered host: it booted as unregistered and registered as a new host, and the original host kept its MAC. Exactly the shared USB adapter case from this thread.

      Real laptops with the shared adapter are the next step, and I’ll report back if anything behaves differently. We’ll switch to the stable release on December 11.

      Thanks, Tom, this solves our problem.

    • C

      1.6.0.158 unable to approve agent

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

      @chscduo Glad it works, and thanks for running each check so quickly.

      The fix is in dev-branch, so the next FOG update includes it. The update replaces the helper you installed by hand with the same code, so you have nothing to undo.

    • 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
      514 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
      458 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
      503 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
      341 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
      833 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
      309 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!

    • Y

      FOG 1.6 – Dependencies between Software Management and Snapins?

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

      @lperoma Run before software is ready to test.

      Agent: FOG Agent v0.1.27 is released. It runs snapins marked Run before software first, then the software set, then the other snapins. Server: the Run before software checkbox is going into dev-branch now. You find it on the snapin’s General tab, under Snapin Arguments Hidden. It reaches stable with the December 11 release.

      For your VM test before then:

      Put the test server on dev-branch. Get the VM on v0.1.27. Set its Agent Update Ring to 0, or set its Desired Agent Version to 0.1.27. On the activation snapin, turn on Run before software, and queue it with the Avast package assigned.

      What you should see in the agent log on that check-in:

      the activation snapin’s result first; then the software lines, Avast included; then any other snapins.

      If the activation snapin comes back as a retry, the agent holds the software until the next check-in, so Avast does not install ahead of it.

      Two things to know:

      An agent older than v0.1.27 ignores the flag and still runs the snapin after the software. So check the agent version before you judge the result. If you import snapins from a CSV with no header row, the new column shifts the columns after Snapin Arguments Hidden. An export from the UI has a header row and is not affected.
    • 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
      325 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.

    • Y

      1.6.0.158 Unable to join machine to he domain and change Hostname

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      5
      0 Votes
      5 Posts
      85 Views
      Y

      @Tom-Elliott So that was all it took, thank you very much, the issue is resolved.

    • 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
      158 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”.

    • 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 Solved FOG Problems
      4
      0 Votes
      4 Posts
      113 Views
      L

      @Tom-Elliott Thanks!

    • 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
      160 Views
      S

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

    • 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
      270 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
      537 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!

    • P

      Access denied: Master node

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

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

    • rogalskijR

      FOG Agent on new image PC not communicating with server

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      3
      0 Votes
      3 Posts
      69 Views
      rogalskijR

      @Tom-Elliott I believe that took care of it. As always thank you so much for this product and the wonderful support!

    • 1
    • 2
    • 3
    • 1 / 3