• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. jmeyer
    3. Posts
    J
    • Profile
    • Following 0
    • Followers 1
    • Topics 58
    • Posts 294
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: FOG Secure Boot with Shim

      I remplaced grubx64 by grubnetx64 (not sure if needed but was recommanded for PXE) and create a “grub” directory in tftpboot with “grub.cfg” inside.
      Grub signed look for cfg file in a subdir called “grub” by default.

      cp /usr/lib/grub/x86_64-efi-signed/grubnetx64.efi.signed /tftpboot/grubx64.efi
      mkdir /tftpboot/grub
      chmod -R a+rX /tftpboot/grub
      

      I get grub menu.

      update (10 am) :
      I copied snponly.efi in grub directory and signed it with the FOG-MOK key I generated before.

      sbsign --key /root/secureboot/FOG-MOK.key --cert /root/secureboot/FOG-MOK.crt /tftpboot/snponly.efi --output /tftpboot/grub/snponly.efi
      

      I end with “error ; bad shim signature”.
      I think I need to import the key on the computer with command “mokutil --import /chemin/vers/FOG-MOK.der”

      I keep on searching…

      2nd update (12:30 am):

      To enroll key :

      cp /usr/lib/shim/mmx64.efi.signed /tftpboot/mmx64.efi
      

      and in tftpboot/grub/grub.cfg

      menuentry 'Enroll MOK' {
          insmod tftp
          insmod chain
          chainloader (tftp,192.168.69.10)/mmx64.efi
          boot
      }
      
      menuentry 'Boot FOG (iPXE)' {
          insmod efinet
          insmod tftp
          insmod chain
          net_bootp
          chainloader (tftp,192.168.69.10)/grub/snponly.efi
          boot
      }
      

      Copy the .der on usb key, put it on the computer, run “Enroll MOK” in pxe grub menu then “Enroll from disk”
      Reboot and run “Boot FOG” in pxe menu.

      And at least I have the FOG menu ! 😎
      I think I’m in the right way. 😅

      Let’s keep on working.

      posted in Tutorials
      J
      jmeyer
    • RE: FOG 1.6.0-beta.2644 DHCP

      @Tom-Elliott no, i have bypass dhcp configuration during install.

      posted in FOG Problems
      J
      jmeyer
    • RE: FOG Secure Boot with Shim

      Here is my first steps.

      Install signing tools on your FOG server

      apt update
      apt install sbsigntool openssl mokutil
      

      Install shim & grub

      apt install shim-signed grub-efi-amd64-signed
      cp /usr/lib/shim/shimx64.efi.signed /tftpboot/shimx64.efi
      cp /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed /tftpboot/grubx64.efi
      

      I end with this at PXE boot :
      9bc4ee10-4d23-4310-985a-2f77069082f2-image.png

      Shim signature give this : (sbverify --list shimx64.efi)

      warning: data remaining[831016 vs 957136]: gaps between PE/COFF sections?
      signature 1
      image signature issuers:
       - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011
      image signature certificates:
       - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Windows UEFI Driver Publisher
         issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011
       - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011
         issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation Third Party Marketplace Root
      

      and grub sinature return :

      signature 1
      image signature issuers:
       - /CN=Debian Secure Boot CA
      image signature certificates:
       - subject: /CN=Debian Secure Boot Signer 2022 - grub2
         issuer:  /CN=Debian Secure Boot CA
      

      I tried creating MOK key but I’m stuck with security violation :

      mkdir /root/secureboot
      cd /root/secureboot
      openssl req -new -x509 -newkey rsa:2048 -keyout FOG-MOK.key -out FOG-MOK.crt -nodes -days 3650 -subj "/CN=FOG Secure Boot/"
      openssl x509 -in FOG-MOK.crt -outform DER -out FOG-MOK.der
      

      FOG-MOK.key <-- private key (protect!)
      FOG-MOK.crt
      FOG-MOK.der <-- enroll this on clients

      Sign ipxe.efi and rename it to grubx64.efi

      cd /tftpboot
      cp ipxe.efi ipxe.efi.original
      sbsign --key /root/secureboot/FOG-MOK.key --cert /root/secureboot/FOG-MOK.crt /tftpboot/ipxe.efi --output /tftpboot/ipxe-signed.efi
      cp ipxe-signed.efi grubx64.efi
      

      I think I need to work more and as Fog default exit type is refind, I’ll make more research.

      posted in Tutorials
      J
      jmeyer
    • RE: FOG 1.6.0-beta.2644 DHCP

      @Tom-Elliott

      drwxr-x— 2 _kea _kea 4096 8 juil. 12:39 /etc/kea
      total 12
      drwxr-x— 2 _kea _kea 4096 8 juil. 12:39 .
      drwxr-xr-x 81 root root 4096 8 juil. 11:31 …
      -rw-rw-r-- 1 root root 2236 8 juil. 12:39 kea-dhcp4.conf

      PRETTY_NAME=“Debian GNU/Linux 13 (trixie)”
      NAME=“Debian GNU/Linux”
      kea-dhcp4
      kea-lfc
      /usr/sbin/kea-dhcp4 (938) kea-dhcp4

      I don’t have error log anymore.

      posted in FOG Problems
      J
      jmeyer
    • FOG 1.6.0-beta.2644 DHCP

      Hello,
      I have installed FOG 1.6.0-beta.2644 with DHCP.
      I end with

      Setting up and starting DHCP Server (Kea)...................Failed
      Kea base configuration failed validation (kea-dhcp4 -t); see /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.2644.log
      

      Error logs :

      '/etc/kea/kea-dhcp4.conf' <-> '/etc/kea/kea-dhcp4.conf.1783500988' renommé
      Syntax check failed with: Unable to open file /etc/kea/kea-dhcp4.conf
      

      This break TFTP directory creation even with the -X option.

      Looks to come from Kea.

      root@FOGSERVERDEV:~/fogproject/bin# kea-dhcp4 -t /etc/kea/kea-dhcp4.conf
      Syntax check failed with: Unable to open file /etc/kea/kea-dhcp4.conf
      

      Temporary fix is to run a second time installfog.sh and put a # before “configureDHCP”.

      posted in FOG Problems
      J
      jmeyer
    • RE: FOG Secure Boot with Shim

      @Florent @KMEH
      First problem I see in the ipxe release is “x86-64 UEFI Secure Boot only”.
      So, if SB is not enable, it doesn’t work at all ?
      It also means that we need to make a SB check to say what efi file the computer need to use ?

      I’ll have some time this week, I’ll try make some tests.

      posted in Tutorials
      J
      jmeyer
    • RE: FOG Secure Boot with Shim

      I don’t understand well everything but maybe it’s more complex than this and I understand nothing at all. haha

      On my server I have a “shimx64.efi” in “/boot/efi/EFI/debian/” can I use it directy or I must install shim-signed and use the shimx64.efi.signed ?

      posted in Tutorials
      J
      jmeyer
    • RE: No pending host

      Hello,

      It’s working again.
      I have update to the last version (1.6.0-beta.2273) but I’m not sure it’s fixed with this.
      I have also clean DB using this : https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

      Thank you.

      posted in FOG Problems
      J
      jmeyer
    • RE: No pending host

      @Tom-Elliott Sorry for the lack of clarity in my explanations and the use of screenshots unrelated to my problem.

      I have upgrade to the last beta and deploy on registered host works well.
      Thank you.

      I’ll check if not registered host now appear in Pending Hosts.

      posted in FOG Problems
      J
      jmeyer
    • RE: No pending host

      @Tom-Elliott said in No pending host:

      SELECT * FROM history;

      It’s not my capture, it’s just to show what deploy task display on host.
      Here is a screen of my version :

      05de4216-c440-42d5-80be-ec2fc1ef23e3-image.png

      Here are the logs of this morning.

      • I import host (412 to 437).
      • Added them to groups to edit image ID and AD (438 to 445)
      • Create deploys tasks and went to start computers.
      • Seeing tasks was not starting, I tested to start task from PXE without deleting host on GUI (446 to 448) without luck.
      • I have delete one host on GUI (449) then create an account with password and delete unused one (450 to 460).
      • Run one task manually on one computer then on each other computer from PXE menu.
      • I added imported all host after deploy (461 to end) to let fog rename and join domain.
      | 412 | [2026-01-20 09:51:19] Host ID: 138 NAME: salle17-01 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 413 | [2026-01-20 09:51:19] MACAddressAssociation ID: 408 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 414 | [2026-01-20 09:51:19] Host ID: 139 NAME: salle17-02 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 415 | [2026-01-20 09:51:19] MACAddressAssociation ID: 409 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 416 | [2026-01-20 09:51:19] Host ID: 140 NAME: salle17-03 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 417 | [2026-01-20 09:51:19] MACAddressAssociation ID: 410 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 418 | [2026-01-20 09:51:19] Host ID: 141 NAME: salle17-04 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 419 | [2026-01-20 09:51:19] MACAddressAssociation ID: 411 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 420 | [2026-01-20 09:51:19] Host ID: 142 NAME: salle17-05 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 421 | [2026-01-20 09:51:19] MACAddressAssociation ID: 412 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 422 | [2026-01-20 09:51:19] Host ID: 143 NAME: salle17-06 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 423 | [2026-01-20 09:51:19] MACAddressAssociation ID: 413 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 424 | [2026-01-20 09:51:19] Host ID: 144 NAME: salle17-07 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 425 | [2026-01-20 09:51:19] MACAddressAssociation ID: 414 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 426 | [2026-01-20 09:51:19] Host ID: 145 NAME: salle17-08 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 427 | [2026-01-20 09:51:19] MACAddressAssociation ID: 415 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 428 | [2026-01-20 09:51:19] Host ID: 146 NAME: salle17-09 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 429 | [2026-01-20 09:51:19] MACAddressAssociation ID: 416 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:19 | 10.121.76.19  |
      | 430 | [2026-01-20 09:51:20] Host ID: 147 NAME: salle17-10 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 431 | [2026-01-20 09:51:20] MACAddressAssociation ID: 417 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 432 | [2026-01-20 09:51:20] Host ID: 148 NAME: salle17-11 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 433 | [2026-01-20 09:51:20] MACAddressAssociation ID: 418 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 434 | [2026-01-20 09:51:20] Host ID: 149 NAME: salle17-12 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 435 | [2026-01-20 09:51:20] MACAddressAssociation ID: 419 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 436 | [2026-01-20 09:51:20] Host ID: 150 NAME: salle17-15 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 437 | [2026-01-20 09:51:20] MACAddressAssociation ID: 420 has been successfully updated.                                                                                                   | fog   | 2026-01-20 09:51:20 | 10.121.76.19  |
      | 438 | [2026-01-20 09:52:07] Group ID: 12 NAME: TOUS has been successfully updated.                                                                                                         | fog   | 2026-01-20 09:52:07 | 10.121.76.19  |
      | 439 | [2026-01-20 09:52:21] Group ID: 12 NAME: TOUS has been successfully updated.                                                                                                         | fog   | 2026-01-20 09:52:21 | 10.121.76.19  |
      | 440 | [2026-01-20 09:52:49] Group ID: 12 NAME: TOUS has been successfully updated.                                                                                                         | fog   | 2026-01-20 09:52:49 | 10.121.76.19  |
      | 441 | [2026-01-20 09:53:10] Group ID: 13 NAME: SALLE 17 has been successfully updated.                                                                                                     | fog   | 2026-01-20 09:53:10 | 10.121.76.19  |
      | 442 | [2026-01-20 09:53:24] Group ID: 13 NAME: SALLE 17 has been successfully updated.                                                                                                     | fog   | 2026-01-20 09:53:24 | 10.121.76.19  |
      | 443 | [2026-01-20 09:53:29] Group ID: 13 NAME: SALLE 17 has been successfully updated.                                                                                                     | fog   | 2026-01-20 09:53:29 | 10.121.76.19  |
      | 444 | [2026-01-20 09:54:12] Group ID: 13 NAME: SALLE 17 has been successfully updated.                                                                                                     | fog   | 2026-01-20 09:54:12 | 10.121.76.19  |
      | 445 | [2026-01-20 09:54:40] Group ID: 12 NAME: TOUS has been successfully updated.                                                                                                         | fog   | 2026-01-20 09:54:40 | 10.121.76.19  |
      | 446 | [2026-01-20 10:11:38] Task ID:  Name: Hardware Inventory Task - salle17-12 2026-01-20 10:11:38 has failed to save. Error: Required database field is empty: storagegroupID -> val: 0 | fog   | 2026-01-20 10:11:38 | 10.121.76.19  |
      | 447 | [2026-01-20 10:11:49] Task ID:  Name: Hardware Inventory Task - salle17-12 2026-01-20 10:11:49 has failed to save. Error: Required database field is empty: storagegroupID -> val: 0 | fog   | 2026-01-20 10:11:49 | 10.121.76.19  |
      | 448 | [2026-01-20 10:11:54] Task ID:  Name: Hardware Inventory Task - salle17-12 2026-01-20 10:11:54 has failed to save. Error: Required database field is empty: storagegroupID -> val: 0 | fog   | 2026-01-20 10:11:54 | 10.121.76.19  |
      | 449 | [2026-01-20 10:12:05] Host ID: 149 Name: salle17-12 has been successfully destroyed.                                                                                                 | fog   | 2026-01-20 10:12:05 | 10.121.76.19  |
      | 450 | [2026-01-20 10:14:15] HookEvent ID: 159 NAME: USER_ADD_FIELDS has been successfully updated.                                                                                         | fog   | 2026-01-20 10:14:15 | 10.121.76.19  |
      | 451 | [2026-01-20 10:14:49] HookEvent ID: 160 NAME: USER_ADD_POST has been successfully updated.                                                                                           | fog   | 2026-01-20 10:14:49 | 10.121.76.19  |
      | 452 | [2026-01-20 10:14:50] User ID: 2 NAME: emmir has been successfully updated.                                                                                                          | fog   | 2026-01-20 10:14:50 | 10.121.76.19  |
      | 453 | [2026-01-20 10:14:50] HookEvent ID: 161 NAME: USER_ADD_SUCCESS has been successfully updated.                                                                                        | fog   | 2026-01-20 10:14:50 | 10.121.76.19  |
      | 454 | [2026-01-20 10:15:09] HookEvent ID: 162 NAME: USER_GENERAL_FIELDS has been successfully updated.                                                                                     | fog   | 2026-01-20 10:15:09 | 10.121.76.19  |
      | 455 | [2026-01-20 10:15:09] HookEvent ID: 163 NAME: USER_CHANGEPW_FIELDS has been successfully updated.                                                                                    | fog   | 2026-01-20 10:15:09 | 10.121.76.19  |
      | 456 | [2026-01-20 10:15:09] HookEvent ID: 164 NAME: USER_API_FIELDS has been successfully updated.                                                                                         | fog   | 2026-01-20 10:15:09 | 10.121.76.19  |
      | 457 | [2026-01-20 10:15:32] HookEvent ID: 165 NAME: USER_DELETE_POST has been successfully updated.                                                                                        | fog   | 2026-01-20 10:15:32 | 10.121.76.19  |
      | 458 | [2026-01-20 10:15:32] User ID: 2 Name: emmir has been successfully destroyed.                                                                                                        | fog   | 2026-01-20 10:15:32 | 10.121.76.19  |
      | 459 | [2026-01-20 10:15:32] HookEvent ID: 166 NAME: USER_DELETE_SUCCESS has been successfully updated.                                                                                     | fog   | 2026-01-20 10:15:32 | 10.121.76.19  |
      | 460 | [2026-01-20 10:16:16] User ID: 3 NAME: 1234 has been successfully updated.                                                                                                           | fog   | 2026-01-20 10:16:16 | 10.121.76.19  |
      | 461 | [2026-01-20 11:11:26] Host ID: 151 NAME: salle17-01 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 462 | [2026-01-20 11:11:26] MACAddressAssociation ID: 421 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 463 | [2026-01-20 11:11:26] Host ID: 152 NAME: salle17-02 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 464 | [2026-01-20 11:11:26] MACAddressAssociation ID: 422 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 465 | [2026-01-20 11:11:26] Host ID: 153 NAME: salle17-03 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 466 | [2026-01-20 11:11:26] MACAddressAssociation ID: 423 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 467 | [2026-01-20 11:11:26] Host ID: 154 NAME: salle17-04 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 468 | [2026-01-20 11:11:26] MACAddressAssociation ID: 424 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 469 | [2026-01-20 11:11:26] Host ID: 155 NAME: salle17-05 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 470 | [2026-01-20 11:11:26] MACAddressAssociation ID: 425 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 471 | [2026-01-20 11:11:26] Host ID: 156 NAME: salle17-06 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 472 | [2026-01-20 11:11:26] MACAddressAssociation ID: 426 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 473 | [2026-01-20 11:11:26] Host ID: 157 NAME: salle17-07 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 474 | [2026-01-20 11:11:26] MACAddressAssociation ID: 427 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 475 | [2026-01-20 11:11:26] Host ID: 158 NAME: salle17-08 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 476 | [2026-01-20 11:11:26] MACAddressAssociation ID: 428 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:26 | 10.121.76.19  |
      | 477 | [2026-01-20 11:11:27] Host ID: 159 NAME: salle17-09 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 478 | [2026-01-20 11:11:27] MACAddressAssociation ID: 429 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 479 | [2026-01-20 11:11:27] Host ID: 160 NAME: salle17-10 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 480 | [2026-01-20 11:11:27] MACAddressAssociation ID: 430 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 481 | [2026-01-20 11:11:27] Host ID: 161 NAME: salle17-11 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 482 | [2026-01-20 11:11:27] MACAddressAssociation ID: 431 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 483 | [2026-01-20 11:11:27] Host ID: 162 NAME: salle17-12 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 484 | [2026-01-20 11:11:27] MACAddressAssociation ID: 432 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 485 | [2026-01-20 11:11:27] Host ID: 163 NAME: salle17-13 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 486 | [2026-01-20 11:11:27] MACAddressAssociation ID: 433 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 487 | [2026-01-20 11:11:27] Host ID: 164 NAME: salle17-14 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 488 | [2026-01-20 11:11:27] MACAddressAssociation ID: 434 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 489 | [2026-01-20 11:11:27] Host ID: 165 NAME: salle17-15 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 490 | [2026-01-20 11:11:27] MACAddressAssociation ID: 435 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:11:27 | 10.121.76.19  |
      | 491 | [2026-01-20 11:11:58] Group ID: 13 NAME: SALLE 17 has been successfully updated.                                                                                                     | fog   | 2026-01-20 11:11:58 | 10.121.76.19  |
      | 492 | [2026-01-20 11:12:10] Host ID: 151 NAME: salle17-01 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:12:10 | 10.121.76.19  |
      | 493 | [2026-01-20 11:12:14] Host ID: 151 NAME: salle17-01 has been successfully updated.                                                                                                   | fog   | 2026-01-20 11:12:14 | 10.121.76.19  |
      
      posted in FOG Problems
      J
      jmeyer
    • RE: No pending host

      I tried to add host before tasking but tasks doesn’t start after checking.
      Same as here : https://i.imgur.com/jn4e9Sw.jpeg

      Here are the apache logs.
      IPs match with host I tried to deploy.

      [Tue Jan 20 10:31:17.238886 2026] [proxy_fcgi:error] [pid 472506] [client 10.121.78.67:14339] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399; PHP message: PHP Warning:  Undefined variable $shutdown in /var/www/fog/lib/fog/bootmenu.class.php on line 848; PHP message: PHP Warning:  Undefined variable $mac in /var/www/fog/lib/fog/bootmenu.class.php on line 881'
      [Tue Jan 20 10:31:27.125508 2026] [proxy_fcgi:error] [pid 472506] [client 10.121.78.155:64142] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399'
      [Tue Jan 20 10:31:38.616598 2026] [proxy_fcgi:error] [pid 473008] [client 10.121.78.156:41956] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399'
      [Tue Jan 20 10:33:10.818242 2026] [proxy_fcgi:error] [pid 472395] [client 10.121.78.63:58115] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key 0 in /var/www/fog/lib/fog/bootmenu.class.php on line 273; PHP message: PHP Warning:  foreach() argument must be of type array|object, null given in /var/www/fog/lib/fog/bootmenu.class.php on line 147; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399'
      [Tue Jan 20 10:33:16.259346 2026] [proxy_fcgi:error] [pid 473420] [client 10.121.78.157:28543] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399'
      [Tue Jan 20 10:33:24.579199 2026] [proxy_fcgi:error] [pid 473420] [client 10.121.78.158:26178] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399'
      [Tue Jan 20 10:35:07.952276 2026] [proxy_fcgi:error] [pid 473264] [client 10.121.78.160:15497] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399'
      [Tue Jan 20 10:35:19.308594 2026] [proxy_fcgi:error] [pid 472506] [client 10.121.78.26:27789] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 336; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 341; PHP message: PHP Warning:  Undefined array key "menuAccess" in /var/www/fog/lib/fog/bootmenu.class.php on line 399'
      

      I deploy fine when host is not registered.

      posted in FOG Problems
      J
      jmeyer
    • No pending host

      Hello,
      few computers with fog client (0.13) refuse to appear in pending host from one day to the next without reason.
      Client does 3 times :

      ------------------------------------------------------------------------------
      --------------------------------Authentication--------------------------------
      ------------------------------------------------------------------------------
       13/01/2026 16:14:33 Client-Info Version: 0.13.0
       13/01/2026 16:14:33 Client-Info OS:      Windows
       13/01/2026 16:14:33 Middleware::Authentication Waiting for authentication timeout to pass
       13/01/2026 16:16:32 Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt
       13/01/2026 16:16:32 Middleware::Authentication Cert OK
       13/01/2026 16:16:32 Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
       13/01/2026 16:16:32 Middleware::Authentication ERROR: Could not get security token
       13/01/2026 16:16:32 Middleware::Authentication ERROR: Le fichier 'C:\Program Files (x86)\FOG\token.dat' est introuvable.
       13/01/2026 16:16:32 Middleware::Communication POST URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&authorize&newService
       13/01/2026 16:16:32 Middleware::Response Invalid host
       13/01/2026 16:16:32 Middleware::Communication URL: http://fogserver/fog/service/register.php?hostname=SALLEA08-03&mac=1C:69:7A:C2:4E:23&newService&json
      

      Then end with :

      13/01/2026 16:16:33 Client-Info ERROR: Failed to authenticate, will not run Module Looper.
      

      I was running FOG 1.6.0alpha then update to 1.6.0-beta.2262 but it was the same.
      I had to import them with csv to unlock the situation on the client.

      I don’t know what log to check to understand the problem.

      Thank you for your help.

      posted in FOG Problems
      J
      jmeyer
    • RE: FOG Portable

      @george1421 I have installed fog with DHCP server but DNS doesn’t work at all (no dns server appear on windows client) so I’m stuck.
      It’s my first time installing DHCP and DNS on Debian so I think I made mistakes.
      DHCP work fine.

      edit : It’s fixed. I forgot to add “option domain-name” and “option domain-name-servers” in dhcpd.conf

      For the script, I think it must be simple to set FOG as DHCP server at startup if after 10 min no IP is given from a DHCP server then set server to static IP and start DHCP and DNS services.
      And then reverse this at shutdown.
      Maybe this can be done manually first.

      edit : Here is the first script.
      I have create files ending with .dhcp for conf for external DHCP/DNS and file ending with .static for conf for local DHCP/DNS.
      It looks to work fine.

      # Configuration actuelle
      echo "Etat DNS local :"
      systemctl is-active bind9
      echo "Etat DHCP local :"
      systemctl is-active isc-dhcp-server
      echo ""
      
      loc(){
              # Configuration DHCP local
              echo "DHCP local"
              # Configuration
              if [ -e /etc/network/interfaces.static ]
              then
                      echo "Copie interfaces"
                      cp /etc/network/interfaces.static /etc/network/interfaces
              else
                      echo "interfaces.static not found"
                      exit 1
              fi
              echo "Redemarrage service reseau"
              systemctl restart networking.service
      
              if [ -e /etc/resolv.conf.static ]
              then
                      echo "Copie resolv.conf"
                      cp /etc/resolv.conf.static /etc/resolv.conf
              else
                      echo "resolv.conf.static not found"
                      exit 1
              fi
      
              # Services
              systemctl start bind9
              systemctl start isc-dhcp-server
      }
      
      ext(){
              # Configuration DHCP externe
               echo "DHCP externe"
              # Configuration
              if [ -e /etc/network/interfaces.dhcp ]
              then
                      echo "Copie interfaces"
                      cp /etc/network/interfaces.dhcp /etc/network/interfaces
              else
                      echo "interfaces.dhcp not found"
                      exit 1
              fi
              echo "Redemarrage service reseau"
              systemctl restart networking.service
      
              if [ -e /etc/resolv.conf.dhcp ]
              then
                      echo "Copie resolv.conf"
                      cp /etc/resolv.conf.dhcp /etc/resolv.conf
              else
                      echo "resolv.conf.dhcp not found"
                      exit 1
              fi
      
              # Services
              systemctl stop bind9
              systemctl stop isc-dhcp-server
      }
      
      # Demande de Configuration
      
      while true; do
          read -p "Voulez vous passer en DHCP externe ou en DHCP local? (e:externe l:local) " el
          case $el in
              [Ee]* ) ext; break;;
              [Ll]* ) loc; break;;
              * ) echo "Please answer yes or no.";;
          esac
      done
      
      posted in General
      J
      jmeyer
    • FOG Portable

      Hello,

      i try to build a FOG server that I could move to different network.

      I wonder it the “WEB HOST” and the “TFTP HOST” could be set automaticaly as the hostname of the OS. (already set manually as hostname instead of IP).

      I have ethernet and wifi on the nano computer and both are DHCP.
      How I could set route or something to say lan is for deploy (same range as current ip) and wlan is for the rest.

      Ex : my fog server ip is 192.168.0.73/24 and deploy works only on this subnet other IP (debian updates, fog updates, ntp, …) should use wifi.

      Other point, could I set fog as DHCP server only if it doesn’t have lan ip to be able to deploy with a direct link to an other computer.

      Thanks for your help

      posted in General
      J
      jmeyer
    • RE: Stuck at "ipxe initialising devices.." (Lenovo again)

      @Tom-Elliott
      Of course, it’s disabled. 😉

      posted in Hardware Compatibility
      J
      jmeyer
    • Stuck at "ipxe initialising devices.." (Lenovo again)

      Hello,
      I have 2 installations of FOG, one under version 1.5.10 and another under 1.6.0-alpha.
      On the 1.5.0 I can boot on PXE on the 1.6.0-aplha I get stuck at “ipxe initialising devices…”
      I have update kernels, rebuild efi files and I still don’t find what I have changed to fixe this or what can be different between the two installation.
      I know it’s not snponly.efi since PXE start to load.
      What are the next file use in the UEFI pxe boot process that could I have different from one installation to an other ?
      Thank you.

      posted in Hardware Compatibility
      J
      jmeyer
    • RE: Full registration customised

      Do you think writing this in fog.man.reg after line

      [[ $exists != "#!ok" ]] && handleError "Unable to register host: $exists ($0)\n   Args Passed: $*"
      

      could do it :

      host=""
      imageid="999"
      blDoAD="Y"
      realdoimage=$(echo -n 1 | base64)
      res=""
      user64=$(echo "fog" | tr -d '\012' | base64)
      pass64=$(echo "password" | tr -d '\012' | base64)
      while [[ $res != "#!ok" ]]; do
          echo -n " * Enter hostname for this computer: "
          read host
          if [[ ${#host} -gt 15 ]]; then
              host=${host:0:15}
              echo " | Truncated to 15 characters: $host"
              usleep 2000000
          fi
          host=$(echo $host | base64)
          res=$(curl -Lks --data "host=$host" ${web}service/hostnameloop.php 2>/dev/null)
          [[ $res != "#!ok" ]] && echo "$res"
      done
      
      dots "Attempting to register host"
      res=""
      while [[ -z $res ]]; do
          res=$(curl -Lks --data "sysuuid=${sysuuid}&mac=$mac&advanced=$(echo -n 1 | base64)&host=$host&imageid=$imageid&doimage=$realdoimage&doad=$blDoAD&username=$user64&password=$pass64" ${web}service/auto.register.php 2>/dev/null)
          echo "$res"
          usleep 2000000
      done
      . /bin/fog.inventory
      usleep 2000000
      
      posted in General
      J
      jmeyer
    • Full registration customised

      Hello,
      I plan to create a custom full registration with only name asked.
      I have read how to edit fog.man.reg but I wonder how i can change an image ID properly to 999 for exemple to set it by default in the registration and avoid to edit file again if I capture a new image.
      I also look for setting a domain name and yes to deploy now instead of the “no” set by default.
      Thank you for your help.

      posted in General
      J
      jmeyer
    • RE: Error PXE-E18 - Lenovo ThinkPad E16

      @george1421 I have run all test and first, there were a firewall rule that were blocking TFTP from the FOG server then after running more test, I realised that it’s not link to hardware or sofware on the server.
      During test, I just changed the port on the switch next the computer to keep most of the hardware between server and client.
      On same vlan I run at 450 Mbits/s (around 50 mo/s) and when I change vlan, I run at 150 Mb/s only.
      And under 20 mo/s max with Windows TFTP client so I give up using it to run more tests.
      Colleagues says there is not QOS but there is definitly something reducing the speed.

      a06abb6b-6197-402f-ba10-c8be4fddc41a-image.png

      posted in FOG Problems
      J
      jmeyer
    • 1
    • 2
    • 3
    • 4
    • 5
    • 14
    • 15
    • 1 / 15