@george1421 said in [BUG] iPXE Boot Loop & Menu Failure After FOG 1.5.10.1660 Upgrade:
If undionly.kpxe worked in bios mode then snp.efi should work in uefi mode
Hi George, the BIOS claims its in UEFI mode but when booting it looks suspiciously like legacy (larger text etc). Its an old Viglin with a second generation i3 which is being retired this October so its not too much of a deal now I have a workaround.
@Tom-Elliott Hi Tom, sorry that I’ve misposted. Your suggestion of trying a realtek.efi didn’t work but it prompted me to try using undionly.kpxe instead. This worked, so maybe its a UEFI / legacy hybrid BIOS? Not sure how its working, but it is.
Thanks, and sorry to crash OP’s post.
@Jim-Holcomb @Tom-Elliott Did you get anywhere with this? We’re having a similar issue that started today. Only affecting older machines, UEFI boot.
See attached for Pcap, PC hangs at “iPXE initialising devices… autoexec.ipxe not found”
Doesn’t matter if I set snp.efi, snponly.efi or ipxe.efi. PC hangs for exactly five minutes then reboots.
We’re on working-1.6, latest update. I’ve done a git clean as suggested above.
@AUTH-IT-Center Super, thank you very much! Looks like its working again 
I’ve recreated our master FOG server onto a new VM, imaging is working correctly. However, the CA certificates have presumably changed to match and the FOG clients installed on all our machines (and images) now won’t connect as the CA doesn’t match.
Is there a way to either:
copy over the old certificates from the original server to the new one OR
copy / install the new CA certificate to the client machines so they reconnect?
Cheers
I deleted the private and public SSL certs and reran the installer, seems to have fixed it.
/opt/fog/snapins/ssl/.srvprivate.key
/var/www/html/fog/management/other/ssl/srvpublic.crt
I’ve migrated our FOG server to a new host with these instructions: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
New master node server working well, but the storage nodes are not communicating. If I try to run the installer again, I get an error at
Certificate request self-signature ok
subject=CN=10.16.46.84
renamed '/etc/httpd/conf.d/fog.conf' -> '/etc/httpd/conf.d/fog.conf.1739201432'
ln: failed to create symbolic link '/var/www/html/fog/fog': File exists
Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xeu httpd.service" for details.
× httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/httpd.service.d
└─php-fpm.conf
Active: failed (Result: exit-code) since Mon 2025-02-10 15:33:08 GMT; 1s ago
Duration: 1w 3d 1h 35min 55.053s
Docs: man:httpd.service(8)
Process: 3352073 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 3352073 (code=exited, status=1/FAILURE)
Status: "Reading configuration..."
CPU: 80ms
Feb 10 15:33:02 tila-fog09 systemd[1]: Starting The Apache HTTP Server...
Feb 10 15:33:08 tila-fog09 httpd[3352073]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe
80::215:5dff:fe32:8b01%eth0. Set the 'ServerName' directive globally to suppress this message
Feb 10 15:33:08 tila-fog09 systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Feb 10 15:33:08 tila-fog09 systemd[1]: httpd.service: Failed with result 'exit-code'.
Feb 10 15:33:08 tila-fog09 systemd[1]: Failed to start The Apache HTTP Server.
@robertkwild This is ours, it boots into Windows automatically, where FOG starts (using the startup script) and renames the PC and adds to domain
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-GB</UILanguage>
</SetupUILanguage>
<InputLocale>en-GB</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Size>500</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>2</Order>
<Type>EFI</Type>
<Extend>false</Extend>
<Size>100</Size>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>3</Order>
<Size>16</Size>
<Type>MSR</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Extend>true</Extend>
<Order>4</Order>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Format>NTFS</Format>
<Label>WinRE</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
<TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Format>FAT32</Format>
<Label>System</Label>
<Order>2</Order>
<PartitionID>2</PartitionID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Order>3</Order>
<PartitionID>3</PartitionID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Format>NTFS</Format>
<Label>Windows</Label>
<Letter>C</Letter>
<Order>4</Order>
<PartitionID>4</PartitionID>
</ModifyPartition>
</ModifyPartitions>
<WillWipeDisk>true</WillWipeDisk>
<DiskID>0</DiskID>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>4</PartitionID>
</InstallTo>
</OSImage>
</ImageInstall>
<UserData>
<ProductKey>
<Key>**REDACTED**</Key>
</ProductKey>
<AcceptEula>true</AcceptEula>
<Organization>**REDACTED**</Organization>
</UserData>
<Display>
<HorizontalResolution>1920</HorizontalResolution>
<VerticalResolution>1080</VerticalResolution>
</Display>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>*</ComputerName>
<RegisteredOwner>**REDACTED**</RegisteredOwner>
<RegisteredOrganization>**REDACTED**</RegisteredOrganization>
<TimeZone>GMT Standard Time</TimeZone>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-GB</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>**REDACTED**</Value>
<PlainText>false</PlainText>
</Password>
<Description>Admin</Description>
<DisplayName>Admin</DisplayName>
<Group>Administrators</Group>
<Name>Admin</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<Display>
<HorizontalResolution>1920</HorizontalResolution>
<VerticalResolution>1080</VerticalResolution>
</Display>
<AutoLogon>
<Password>
<Value>**REDACTED**</Value>
<PlainText>false</PlainText>
</Password>
<Username>Admin</Username>
<LogonCount>1</LogonCount>
<Enabled>true</Enabled>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>C:\Windows\Setup\scripts\SetupComplete.cmd</CommandLine>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:c:/customise/win10/sources/install11edu.wim#Windows 11 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
@dejv Ah, came here to say secure boot! Nice one.
@rogalskij said in OS Details no longer working:
For those experiencing the same issue on mainstream linux distros, navigate to your “resolv.conf” config file located in /etc/resolv.conf and add your individual search domains. Test a ping to a DNS name via command line on the box itself, then check your GUI again. Took about 2 minutes for it to reflect and show for me.
I’ve just done this, and now noticing a remarkable increase in performance of the 1.6 web page. Thank you!
Previously, we were able to search hosts by serial number, the SN that was stored in Inventory Static under “System Serial”. This no longer works in the latest version.
Not sure if bug or by design.
@Laurent we’re on FOG 1.6, but I think its the same as 1.5.10. FOG doesn’t let you see the AD password once input, but I’d echo @JJ-Fullmer’s point of using a specific account
Do you get any error message in the FOG.log file in the root of C on a client?
@Tom-Elliott latest pull working correctly again. Thanks for sorting!
@Tom-Elliott updated to 2138 but now snapins not working. No http or https in the Communication download string. This is on the master FOG server, I haven’t updated the storage nodes yet.
------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
18/10/2024 11:10:05 Client-Info Client Version: 0.13.0
18/10/2024 11:10:05 Client-Info Client OS: Windows
18/10/2024 11:10:05 Client-Info Server Version: 1.6.0-beta.2138
18/10/2024 11:10:05 Middleware::Response Success
18/10/2024 11:10:05 SnapinClient Running snapin IPEvo-Visualiser
18/10/2024 11:10:05 Middleware::Communication Download: ://10.16.46.84//fog/service/snapins.file.php?mac=0C:9D:92:C9:DE:33|0C:9D:92:C9:DE:32&taskid=1711
18/10/2024 11:10:05 Middleware::Communication ERROR: Could not download file
18/10/2024 11:10:05 Middleware::Communication ERROR: Illegal characters in path.
18/10/2024 11:10:05 SnapinClient C:\Program Files (x86)\FOG\tmp\Visualizer_win7-11_v3.6.0.1.msi
18/10/2024 11:10:05 Middleware::Communication URL: http://10.16.46.84/fog/service/snapins.checkin.php?taskid=1711&exitcode=-1&mac=0C:9D:92:C9:DE:33|0C:9D:92:C9:DE:32&newService&json
------------------------------------------------------------------------------
Restoring the /var/www/html/fog/lib/client/snapinclient.class.php file from beta 2132 starts working again
@Tom-Elliott said in Snapins not deploying: Illegal characters in path.:
You use location plugin, correct?
Yes, that’s right.
I’ve pushed another fix that I think might help here and it takes a slightly different approach albeit similar.
Awesome, thanks. I’ll give it a try today
@JJ-Fullmer You were correct about the download link not being formed properly. I went looking in the code and found a change in the /var/www/html/fog/lib/client/snapinclient.class.php file from a working version of FOG (1.6 beta 2132) to the latest version.
Copying over the old version of this file and snapins are installing correctly now.
@Tom-Elliott this should probably be moved to the Bug Reports forum if that’s possible? The difference in the files is the latest version is missing the below code around line 185
$location = sprintf(
'%s://%s/%s',
self::$httpproto,
$StorageNode->get('ip'),
$StorageNode->get('webroot')
);
and there are a few changes elsewhere too.
Thanks all!
@JJ-Fullmer yes, that could be it. I’ve found a FOG.log from a few weeks ago that has http:// in the download link:
------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
03/10/2024 11:22:15 Client-Info Client Version: 0.13.0
03/10/2024 11:22:15 Client-Info Client OS: Windows
03/10/2024 11:22:15 Client-Info Server Version: 1.6.0-beta.2132
03/10/2024 11:22:15 Middleware::Response Success
03/10/2024 11:22:15 SnapinClient Running snapin LetterJoin Fonts - Little Mead
03/10/2024 11:22:15 Middleware::Communication Download: http://10.xx.yy.zz//fog/service/snapins.file.php?mac=B4:B6:86:DF:3A:9B|92:32:4B:5B:31:DD|D2:32:4B:5B:31:DD|90:32:4B:5B:31:DE||90:32:4B:5B:31:DD&taskid=1618
03/10/2024 11:22:38 SnapinClient C:\Program Files (x86)\FOG\tmp\f1k1w2x2z2.msi
03/10/2024 11:22:38 Bus Emmiting message on channel: Notification
03/10/2024 11:22:38 SnapinClient Starting snapin
03/10/2024 11:22:40 SnapinClient Snapin finished
03/10/2024 11:22:40 SnapinClient Return Code: 0
03/10/2024 11:22:40 Bus Emmiting message on channel: Notification
03/10/2024 11:22:40 Middleware::Communication URL: http://10.xx.yy.zz/fog/service/snapins.checkin.php?taskid=1618&exitcode=0&mac=B4:B6:86:DF:3A:9B|92:32:4B:5B:31:DD|D2:32:4B:5B:31:DD|90:32:4B:5B:31:DE||90:32:4B:5B:31:DD&newService&json
------------------------------------------------------------------------------