@wntr said in FOG DHCP server not working:
What network settings do you need on Ubuntu regarding DHCP? Normally the IPv4 settings are set to DHCP in the Networkmanager GUI.
We suggest to use a static IP for your FOG server!
You can find out the IP the server had when FOG was installed by running the following command on your FOG server console: grep ipaddress /opt/fog/.fogsettings
@Alan-Lim @jfernandz The message Starting sshd: touch: cannot touch '/var/lock/sshd' : No such file or directory is normal with the buildroot version currently used for the FOS inits. While it’s not nice it’s not causing any kind of issue and can be ignored.
The mount error seen after that is probably caused due to a router or firewall now allowing all the traffic needed to mount an NFS share.
@DBCountMan I don’t think FOG has this type of group function you want to use. Probably looking into using the FOG API to script this kind of thing or figure out why schedules don’t work will get you the quickest results. Have you checked the FOG scheduler logs on the server yet?
By the way, which version of FOG are we talking?
@Manny-Both-Hanz Did you put the files needed for this onto your USB? /boot/ipxe.krn and /boot/ipxe.efi
Both errors mentioned sound like those files are either missing or might be corrupt.
@af-pw said in multiple sites:
limited bandwidth and long distances between sites.
This is a major limiting factor that you can’t get around with a FOG server at site B unless you do a manual transfer of the image files via an external disk.
@sopinv Well there is a limit on parallel unicast deployments.
@Mehditne That’s interesting. Searching the forums I found someone having a similar sounding speed issue with a different type of hardware stating that it’s going fast on the Dell 5420: https://forums.fogproject.org/topic/16878/hp-probook-450-g9-slow-to-image-kernel-6-1-22
I suggest you check all the components (network, RAM, disk) in that device and also test other machines as well.
@Mightmar This happens because the newer Apache version on latest Ubuntu does not allow TLS1.0/1.1 anymore. You need to update your fog-client software. See my post here: https://forums.fogproject.org/topic/16160/fog-client-unable-to-connect-via-https
@robert70569 This is interesting. I think it would fail earlier when trying to NFS mount the images share on the FOG server in that case. Strange.
@skyborne98 Sorry for the long delay. Not too many people know the ins and outs of the fog-client, especially when it comes to the Linux part of it.
In the log we see ProtocolError which I have not seen before I think. Do you have a customized httpd/apache configuration or default created by the FOG server installer?
@MikeAbbages I am not sure the field for IP address is being populated in the database anymore. As clients will get an IP from the DHCP this is changing every so often anyway. The topic linked is many years old and things have changed a fair bit since. I don’t have access to a server at the moment as I am on travels. You can check your own database or ask @Tom-Elliott or @george1421 to have a look at it.
In general you can export a CSV style list from the hosts view in the FOG web UI but I doubt this will have the IPs in it.
@jouni-jokelainen said in Fog and Pfsense 2.7:
Adjusted Pfsense settings for fog (Thanks for these george) :
I guess this topic is solved then. Please open a new issue if you have more questions (not related to pfSense).
@davidgoncalves Also please run the following commands on your FOG server shell and post output here:
mount
df -h
ls -al /images/dev
@robert70569 Do you have clients that proceed beyond that point? As far as I can remember we did not have reports about this since 1.5.10 was released.
To further debug this issue I suggest you schedule a capture in debug mode, then boot up the machine, set a root password (command passwd) when you get to the shell, check the IP it got from the DHCP (command ip a s) and make sure you can connect via SSH. Then start the capture (command fog) and step through the process. When it hangs you wanna try the SSH connection again. See if you can login and see what it is working on (commands top and ps ax).
@plegrand I have not had the time to test this myself but I can do so in about three weeks. The PHP issues with the LDAP plugin should be fixed in the dev-branch version (1.5.10.11).
@totoro said in JLT 6012 rev 2023 - restor boot:
Because I try de load the compatibility checking, with 6-1-22 it’s working, and after a reboot, no anymore,
Can you explain what exactly you mean?
@robert70569 How long have you been waiting for it to proceed at this stage?
@astrugatch If that doesn’t work then search the web for “msiexec uninstall” to find some more possible solutions.
@Sebastian-Roth said in Client hangs at EFI stub::
Yes it could be as “simple” as switching a kernel config setting on or off but I rather think the Ubuntu kernel might boot on the machine due to some patch Ubuntu applies to it’s kernels. That would make it a bit harder but not impossible to figure out and fix in FOS.
The more I read the more I think I was wrong with assuming Ubuntu patches making it work. The Wikipedia article on this CPU says:
Not all accelerators are available in all processor models. Some accelerators are available under the Intel On Demand program, also known as Software Defined Silicon (SDSi), where a license is required to activate a given accelerator that is physically present in the processor. The license can be obtained as a one-time purchase or as a paid subscription. Activating the license requires support in the operating system. A driver with the necessary support was added in Linux 6.2.
So it’s not likely you still need special patches to even just boot up.
@george1421 @sgilbe Great you guys have narrowed this down to this point. I have followed this thread but have not had the time to help you out and won’t be of much help in the next two weeks with just a little more time but no computer at hand but only the mobile phone to post and do research. Anyhow, I will try my best.
Yes it could be as “simple” as switching a kernel config setting on or off but I rather think the Ubuntu kernel might boot on the machine due to some patch Ubuntu applies to it’s kernels. That would make it a bit harder but not impossible to figure out and fix in FOS.
@sgilbe On a system with Ubuntu installed you should find the kernel config in /boot/config-*.