@Sebastian-Roth I had to reinstall node.js, but I followed a different set of directions than before, and wouldn’t you know, node-dhcproxy functions as it should. I’m guessing that I did not have node.js setup properly the last time I ran it. I’ve attached the dump file anyway.
Thanks for your help on this, it is nice to have another option for our network environment should dnsmasq becomes unusable. -kurt
From what I can tell, the installer is adding lines to the fog.conf file that keeps the httpd service from restarting.
I can take out the bad lines from the fog.conf file and the httpd service restarts as it should.
-kurt
That did it, problem solved. Thanks for the info on the new DNSMasq binary.
-kurt
Disabling IPv6 did the trick. I ran:
sudo echo "1" > /proc/sys/net/ipv6/conf/all/disable_ipv6
and the installer ran normally. I’ll need to shut it down permanently.
Thank you for your help. Is this IPv6 issue consistent in all of the builds?
-kurt
I’ve set the FOG_MEMTEST_KERNEL in the General Settings to memtest.bin with no luck, same error. There is a file called “memdisk” in the same folder, it errors in the same way.
Yes. the Memtest ISO boots fine from a USB drive via UEFI.
I am wondering, are other users having this same problem with the FOG installed Memtest when booting as UEFI clients? I’d like to know if my environment here is playing a role here.
Are users with UEFI clients needing to set their PXE menu exit to REFIND_EFI in order to boot to the disk from the FOG menu? For me its the only way to get the our machines into the OS from the boot menu.
@george1421 The new 7.0 memtest ISO does not have those two files (memtest and memtest.bin) within it. The 7.0 version is a different beast it seems.
@george1421 memtest 5.01 comes up from the BIOS boot menu. Memtest site latest version is 7.0.
http://www.memtest86.com/technical.htm#network
Perhaps their “Site Edition” is needed for this?
With REFIND_EFI as the exit type I can boot to the hard diskand successfully run the other options, but when the MEMTEST option is chosen I get the chainloading error. The exit type does not have an effect on the Memtest behavior, it gives the same error regardless of the exit type set in the PXE Boot Menu settings within the web gui.
Sorry, should have mentioned that I am using 1.3.0 RC1.
UEFI clients need to be set with the REFIND_EFI exit option to boot to the hard disk.
From the FOG menu I can run Memtest from the legacy BIOS boot clients, but it fails to start from UEFI clients’ FOG menu.
2e008081
exec format error
chainloading failed
Any idea what is causing this?
thanks, -kurt
@Sebastian-Roth I had to reinstall node.js, but I followed a different set of directions than before, and wouldn’t you know, node-dhcproxy functions as it should. I’m guessing that I did not have node.js setup properly the last time I ran it. I’ve attached the dump file anyway.
Thanks for your help on this, it is nice to have another option for our network environment should dnsmasq becomes unusable. -kurt