Hello,
I am using fog dev-branch version: 1.5.10. I noticed during a multicast session that when I go to check on the status in Active Task on the web GUI, I am unable to read the progress of the task. The data is all scrunched and unreadable. I noticed as the progress bar expands with the percentage increase, the data starts expanding and becoming more legible.
No modifications to the network or the computers. The computer is able to obtain an IP address in windows, link speed auto-negotiates to 1Gbps. I tested the network path and it had no issues, but just in case I switch to a different port. The issue still remains.
I Just noticed that the links to the screenshot on the original post are broken. Here are new links to the images:
This is the error I get when a computer is trying to execute a task from fog and it goes thru PXE:
This the error I get when I try to launch from the PXE menu the Computer Compatability:
HARDWARE
SERVER:
PRIMERGY RX2530 M1
2 x Intel
Xeon CPU E5-2620 v3 @ 2.40GHz
32GiB System Memory
Four Network Cards Bonded
NODE:
PRIMERGY RX2530 M1
2 x Intel Xeon CPU E5-2640 v3 @ 2.60GHz
32GiB System Memory
Storage 2TiB
Four Network Cards Bonded
DHCP
Infoblox
Using Unionly.kpxe
Clients BIOS
Mainly HP Computers
Configured to use Legacy Network Boot
Secure Boot Disabled
SOFTWARE
FOG Info:
dev-branch version: 1.5.9.111
bzImage Version: 5.10.50
bzImage32 Version: 5.10.50
Description of Problem:
After updating to the latest version, I noticed that the speed decreased. The image size being pushed to the computers is about 300GB, this used to take between 2 and 3 hours. Now it is taking about 8 hours. I also noticed that some of the computers fail to image. The computers get an IP address from PXE and continue to load but then give an error saying that it could not obtain an IP from the DHCP server or is unable to reach the FOG Server.
I canceled the task and tried to launch it from the client machine PXE menu, and got the same error. I launched the FOG compatibility from the PXE menu and noticed that it was unable to get an IP address. I loaded the computer back into windows and the computer was able to connect to the internet with no issues. I have 3 rooms of 24 computers in this particular area and about a third of them have this issue. The other computers were able to be imaged but noticed that the PXE loading was very slow and the time that it usually takes to the image was doubled. Here is a screenshot of when I tried loading the computer compatibility from the client PXE menu.
I tried Switching to older kernels and it did not work. I would appreciate any ideas that can help in figuring out this problem.
Sorry it took me so long to get back to you, I tried using the file you suggested and to no avail. The same problem occurs. I also used a different fog server and it had the same behavior. The computers randomly freeze loading pxe drivers.
I tried different version of the kernel and they all do the same. I am willing to try different version of the PXE files
@wayne-workman Hello, sorry it took me so long to get back to you, Here are the pictures you requested.
I tried the kernel you suggested and it did not solve the problem. I also tried changing the pxe boot in the DHCP to these:
undionly.kpxe
ipxe.pxe
ipxe.kkpxe
These did not work with the suggested kernel.
Thanks
Thanks for the quick reply I will try to play with the kernels.
Having issue when computers boot from pxe. They randomly freeze and do not continue to boot. They stop at different points when loading PXE. I am not sure how to proceed in troubleshooting this issue, any help will be appreciated. please see my configuration below, please let me know if you have additional questions.
Current Configuration:
Two server configuration, one acting as Storage Node, running Centos 7.4.1708. Both are running four NIC Bonded LACP. Firewall & SELinux are both disabled. Option 66 and 67 configured for infoblox appliance for my network segment. The PXE boot file currently configured is ipxe.pxe.
Clients:
All the Bios and NIC Firmwares are updated to the current versions. PXE are configured to legacy mode.
HP Elitedesk 800 G1 mini Tower & All in One
HP Elitedesk 800 G2 All in One
HP Elitedesk 8300 mini tower & All in One
HP Elitedesk 8200 mini tower
Hi Tom,
I tried the installation with the suggested switches:
./installfog.sh -yX
The installation took a bit of time but completed. Thanks!
I used GIT to download the latest FOG Version 1.3.5.RC10 and it quits during installation:
I rebooted the server and checked network connectivity and everything appears to be fine. Tried doing the upgrade several times but it continues to fail at that particular step.
Hi tom That fixed the problem, Thanks for all your help!!
Hi Joe,
I have tried the new client in our environment and it did not work. Sadly I ran out of time and kept the old client on our workstation since it seemed to work. Sadly I have not tried to troubleshoot it since, but I will be working on upgrading this summer since we are upgrading all of our workstations to Windows 10.
Thanks,
When I try to push a snapin to client machines, the snapins do not run. This was working correctly on version 1.3.4, but stopped working after I upgraded. I have attached the client log file to this thread. The most relevant line in the log file states:
“Snapinclient module is disabled globally on the Fog Server, exiting.”
I checked the web server setting and it showed that the snapinclient service is enabled.
Thanks!!
Hi Tom,
according to the client log file it says " snapinclient module is disabled globally on the FOG Server, exiting."
I will create a new issue, and post the log file from one of the clients.
Thanks!
Just installed Fog version 1.3.5 RC4 and it corrected the hostname changer problem under the legacy client. Unfortunately snapin deployment do not work.
Hi,
I updated to:
Thu Feb 09, 2017 13:15 pm
Running Version 1.3.5-RC-3
SVN Revision: 6066
I am still having the same problem. I attached the log from one of the clients.0_1486664368264_fog.log
Noticed that when pushing image the computer does not auto rename or join computer to domain. I notice that log file indicated that the hostnamechanger service has been disabled globally on the fog server. I checked and it is enabled.