• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. lperoma
    3. Topics
    L
    • Profile
    • Following 0
    • Followers 0
    • Topics 13
    • Posts 53
    • Groups 0

    Topics

    • L

      A reimaged host stays stuck on an old directory join plan ("marker absent; automatic retry refused")

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      0 Votes
      3 Posts
      45 Views
      L

      @Tom-Elliott

      Thanks Tom, I tested #2122 and it does what you described.

      I applied the two src files of the PR by hand on top of the patches channel (schema 465, agent 0.1.28) and reproduced the same situation with test-bios. First Deploy (16928): the agent asked for the directory join and the plan went to awaiting_reboot (attempt 12f448e3…, trigger_task_id 16928). Before it rebooted I powered the VM off and queued a second Deploy (16929), which completed normally. The agent enrolled by itself after that (rebind, approved via deploy).

      For a while the old plan was still in hdRejoinState, still awaiting_reboot with trigger 16928, so right after queuing the Deploy nothing had changed. Once the machine booted the new Windows and the agent checked in, FOG replaced it on its own. A minute later there was a new attempt (3e64f53…, trigger 16929, awaiting_reboot). I didn’t touch “Clear directory operation review” or edit anything in the database. After one reboot the host was verified, hdJoined=1, hdKind=ad, secure_channel: healthy.

      So the old attempt is dropped after the new Deploy and the first boot, not at the moment the Deploy is created, which matches what you wrote. It only looks odd if you check the host in between and still see the old plan. No problem on my side, just mentioning it in case anyone else notices the same thing.

      One idea, only if you think it’s worth it: a checkbox in the Deploy task form, something like “discard every pending task of this host”, unchecked by default. The automatic rules are safer for the normal case, but sometimes the admin knows everything left over from the previous install is dead (queued tasks, snapins, a pending directory join) and wants to force a clean start right when the Deploy is queued, without waiting for the first boot and without the “Clear directory operation review” box. In our case, when a machine misbehaves it often keeps snapin tasks queued, and today you have to open the host, work out which tasks it has and delete them one by one. In a big fleet that is slow and easy to get wrong, whereas one box on the Deploy would clean the slate in a single step.

      I’ll drop my manual patch when #2122 reaches patches.

    • L

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

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      14
      0 Votes
      14 Posts
      269 Views
      Tom ElliottT

      @lperoma Thanks for the detail. There are two server fixes and one agent fix.

      Please update instead of copying files this time. This fix changes the database (schema step 465), and the code depends on it. Copied files without that step make enrollment saves fail in a new way. Your server is also now several changes past 1.6.0.158. Run the updater on the patches channel. It installs the files and runs the schema update together. Or wait for the stable release on December 11.

      Server (FOG PRs #2116 and #2118):

      Agent enrollment now follows the boot rule for a shared adapter. The firmware names one host, and the adapter’s MAC is on another host. If that other host’s stored serial differs from the reported serial, the firmware’s host wins. Your laptop then enrolls as its own host, with the normal “known-host-no-agent” reason. The firmware host must match the serial too. A copied UUID alone never wins over a MAC. Any other disagreement stays an identity conflict. The row is now saved with no host, instead of host 0, so the foreign key no longer refuses it. The agent gets “pending”, not 409, and the row shows in All Pending Agents. For a conflict, All Pending Agents now shows which other host has the MAC. After you remove the cause (for example the stray MAC), the next agent poll binds the request to the right host. Then you approve it. A conflict is never approved automatically, not by a token and not by a recent deploy (#2118 closes this for older agents too).

      Agent (fog-agent PR FOGProject/fog-agent#52): a key whose first request went in without the directory feature cannot add the feature later. That is deliberate on the server. The agent now makes a new key once when the server answers enrollment_upgrade_requires_new_key, and enrolls again. This is in agent v0.1.28. Agents update to it on their own.

    • 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
      123 Views
      L

      @Tom-Elliott Thanks!

    • L

      Feature request: a "Troubleshooting" menu in the web UI to find hosts that fail to authenticate

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      2
      0 Votes
      2 Posts
      121 Views
      Tom ElliottT

      @lperoma Thank you for the detailed write-up. The detection notes made this quick to scope.

      FOG 1.6 covers this as follows:

      FOG Client cannot authorize. This was the real gap, and a pull request now adds it: https://github.com/FOGProject/fogproject/pull/2089. The server records each host whose client fails the handshake: since when, how many times, the source address and the reason. A new list report, Reports > Client Authentication Failures, shows them with the fix next to each one. A host leaves the list when its client authenticates again. Two reasons are recorded:

      The security token does not match. Reset Encryption Data fixes this. The server cannot decrypt the client’s key. This means the certificate the server publishes for clients does not pair with its private key, so every host fails at once. A reset does not help. Running the installer with --recreate-keys issues a new pair.

      One case stays invisible to the server. A client that trusts a different FOG CA refuses the server’s certificate and never sends a login, so there is nothing to record. Its fog.log shows “Certificate is not from FOG CA”.

      Rejected iPXE menu logins. 1.6 already records each rejected login in the audit trail, with the username and the address. Look under Reports > Audit Report.

      Hosts with no contact. 1.6 stores the last check-in and the last ping for each host. Fleet Report shows the last check-in, so you can sort on it.

      All of this is 1.6 only. 1.5.x does not get these changes, so your script remains the answer there until you move to 1.6.

    • L

      Update to working-1.6 fails with mysql: unrecognized service

      Watching Ignoring Scheduled Pinned Locked Moved Solved Linux Problems
      6
      0 Votes
      6 Posts
      3k Views
      L

      @Tom-Elliott Success. I switched to single-user with init 1, and installing systemd-sysv worked fine.

      As this is a machine upgraded from debian 11, maybe it wasn’t using systemd. Installation of 1.6 worked no problem Thanks,

    • L

      Attempting to join domain: The parameter is incorrect, code = 87

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      2
      0 Votes
      2 Posts
      709 Views
      L

      This worked for me :

      Domain name: subdomain.domain.tld
      OU: OU=Computers,DC=SUBDOMAIN,DC=DOMAIN,DC=TLD
      AD DEFAULT USER: adminuser
      Domain Password: supersecret
      Name Change/AD Join Forced reboot?: cheked

      Not sure if I was doing anything wrong, I tried too many things, but this now works. Thanks.

    • L

      Could not mount /dev/sda3: Metadata kept in Windows cache, refused to mount.

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      4
      0 Votes
      4 Posts
      1k Views
      L

      @george1421 This is correct. It works fine. Thanks,

    • L

      Chainloading failed, hit 's' for the iPXE shell

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      10
      0 Votes
      10 Posts
      3k Views
      L

      I have the impression this issue has something to do with DHCP server in the gateway competing with proxydhcp in the fog server.

      I have updated DHCP settings in Unifi to allow / block DHCP traffic (DHCP Guarding). I have included FOG’s dhcppxory address and seems to be working ok now.

    • L

      PXE Boot Error - "Kernel Panic" Issue "XZ decompressor ran out of memory"

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      19
      0 Votes
      19 Posts
      6k Views
      P

      I was able to find a work around after running into this issue. In FOG Settings under TFTP Server update the “TFTP PXE KERNAL 32” to bzImage and “PXE BOOT IMAGE” to init.xz. I was able get thing working after that.

      53e33ef4-25c1-496f-85c4-e3ff864a9aeb-image.png

    • L

      KMV installation can not locate images folder upon image deploy or capture.

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      11
      0 Votes
      11 Posts
      3k Views
      S

      @lperoma Thanks for the update. Good to hear you found this and were able to fix it. Well done! This is beyond FOG itself and it would have taken a lot of posting forth and back to figure this out for us. Although I don’t know much about virtiofs I can imagine it causing problems when being exported as NFS (as FOG does).

    • L

      Fog migration

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      3
      0 Votes
      3 Posts
      677 Views
      L

      @sebastian-roth Thanks Sebastian! That solved all issues!

    • L

      Adobe Acrobat Reader snapin not working

      Watching Ignoring Scheduled Pinned Locked Moved Solved Windows Problems
      6
      0 Votes
      6 Posts
      2k Views
      george1421G

      @astrugatch said in Adobe Acrobat Reader snapin not working:

      If I recall correctly the Acrobat exe installer has an MSI baked inside of it.

      There is two ways to grab the MSI.

      7zip will sometimes open self extracting installers so you can grab the contents. Launch the .exe program but stop at the eula, possibly one later question. Then go to your temp directory The contents of the installer should be in a guid named directory in your temp. The alternate location might be in ProgramData\adobe path.
    • L

      Snapin Update Fail after upgrading to 1.5.7

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      6
      0 Votes
      6 Posts
      2k Views
      S

      @lperoma The grep error can be ignored.

    • 1 / 1