@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.
@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 :
Here are the logs of this morning.
| 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 |
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.
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.
@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
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
@Tom-Elliott
Of course, it’s disabled. 
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.
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
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.
@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.
@george1421
Do you mean using brand adapteur certified for PXE such as :
https://www.dell.com/en-us/shop/dell-adapter-usb-30-to-ethernet-pxe-boot/apd/443-bbbd/pc-accessories
or
https://www.lenovo.com/fr/fr/p/accessories-and-software/cables-and-adapters/cables-and-adapters_adapters/4x90s91831
@george1421 I have created a 500mo file since most of original files are small in the FOG tftpboot directory and try to download it with Windows TFTP client.
It takes me around 10 to 15 min to download it.
I have also tested on ThinkPad E15 gen 4.
Is there a speed limit in TFTP ?
On the E15 and the E16, it’s a Realtek RTL 8168 Series.
ID on E15 is PCI\VEN_10EC&DEV_8168&SUBSYS_50B117AA&REV_15
ID on E16 is PCI\VEN_10EC&DEV_8168&SUBSYS_50D517AA&REV_15
edit : I have find out that Windows TFTP client is mess up with max speed.
I have reach 450Mb/s with Ivanti from PXE when I still stuck at less than 20 Mb/s with Windows TFTP client.
Another thing is that I have add FOG menu entry to download a file from Ivanti PXE (chain command) and I also download at only 6 Mb/s.
I’ll run more test directly from PXE diring the next days.
We found IPS rules (I think it’s the name) on the firewall that was blocking TFTP.
It’s now loading but terribly slow (average 6 Mb/s on a Gb link).
We will make more test today.
As said, no problem with legacy boot that use same configuration on dhcp (option 66 and 67) and use the same vlans.
I get well the IP then it give timeout.
I’m not on the same vlan but is there differences between legacy and efi or if one work, the other should ?
Maybe it’s rights between vlan that block only efi.
I’m not sure since when I have the problem but we changed switchs few weeks ago.
I’ll put a wireshark tomorow to look what happen.
Thank you
Hello,
I have a timeout during pxe boot with an install of FOG (version 1.5.10.1622) on a Lenovo ThinkPad E16 gen 1.
SecureBoot is disabled.
I didn’t notice error with legacy boot on older computers and a tftp client under Windows can download the “.efi” files.
I tested with snponly.efi and ipxe.efi, same error.
My personnal FOG server under version 1.6.0 doesn’t give any error.
In other high school, I didn’t had problem with a FOG 1.5.10
I have download last kernel (6.6.49), the last Initrd (2024.02.5) and build ipxe file using the doc here : https://docs.fogproject.org/en/latest/kb/reference/compile_ipxe_binaries/ but problem is the same.
I’m out of idea.
Thank you for your help.
@george1421 Rebuild to last version didn’t fix the problem.
@Tom-Elliott Exit type to EXIT give a “chainloading failed…”
using snponly.efi fixed the problem.
Thank you for your help.
Hello,
For the first time, I had “zstd /stdin unsupported format” during deploy after moving an image between FOG servers and crossing two Windows computers.
I end checking CRC with the commands directly inside image directory :
cksum *
Result :
4102865288 6 d1.fixed_size_partitions
1553301511 1048576 d1.mbr
21074109 873 d1.minimum.partitions
3930731312 20 d1.original.fstypes
4294967295 0 d1.original.swapuuids
3323012245 11304005 d1p1.img
4080882029 767 d1p2.img
4038447468 7834146234 d1p3.img
1735290603 153344 d1p4.img
1356735187 873 d1.partitions
2087979657 873 d1.shrunken.partitions
Get-ChildItem * | Select-Object -Property Name,@{name="Hash";expression={(Get-FileHash $_.FullName).hash}}
Result :
d1.fixed_size_partitions 8F2326E98FF66634578EC07879B45A6ADA0B681444819A581F5F3BFCA5FA6029
d1.mbr 5113DDB273F26E0D6F88367B5330BEF6E2A7FD399984EDB3519268DDE7B4FFCE
d1.minimum.partitions 8A04A480F69C6A6084DDF9EB43F37E913C14C5EF57AF58CBB7406CD2CB832CAC
d1.original.fstypes A061EFCFAA6B32FBD533450D14E71E2C1EC422AC67A8F8296B773A46407F5914
d1.original.swapuuids E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855
d1.partitions 3F23AA64C5AFDCE83CCB59AACF2F03EDAD3EA6429B22010339C43B29DE406D2C
d1.shrunken.partitions 59D5B234D923B3B73EA0CB808853397B8D19644C9E135BFDD8C538633ECE4106
d1p1.img 6B3A9D5B0C26BE448A24339F7DE1067A4C0F3615D9BE42B86BEB355BA6F9BCE6
d1p2.img 511CBE019A39980DF90F7D9A547BAE4521551EEF53625705538713AB14311DD0
d1p3.img 5F2223BB3D63C9400C77C10A5ADF5AE2DCA48D8C768AC2097F20E3731E843FC9
d1p4.img A8D21F3E22C596EA01B8F7BAC981C9FB265938D0A1A3F2C3599ADF170A75CE9E
This way I can check between my 2 computer under Windows before checking between my two FOG servers.
@george1421 As it’s happening only on my personnal FOG install, I don’t care to have to unplug lan cable.
I’ll try rebluild iPXE when I have time.
Thank you.
@garrett-stevenson
I’m not sure of your question but I have installed fog from zip without internet (I am also behind a firewall) by using the -X (–exitFail Do not exit if item fails").
Then I downloaded them with other computer and have copied them in the /var/www/html/fog/service/ipxe/ directory with winscp (using home as intermediate directory and then puting back rights and owner)
Yet I had all packages needed to run fog already installed.