Posts made by jjsplitter

@george1421 I am now able to get past the other error during the PXE boot and I can see the FOG menu screen (where you deploy images and or create host registrations).

You’re the best!

@george1421 Holy mother of everything. That worked. I can access the management console from my own computer now.

Now to test and see if the images will work now.

Thank you x1000!

That is the exact tutorial i followed when i was setting up CentOS and FOG. The only part i was not able to complete was:

for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service;
done

This kept giving me an error of: “Error: INVALID_SERVICE: " " not among existing services”.

My FOG server is also not responsible for DHCP so I am not sure if this is needed either way.

Thank you,
Justin

I will be as brief and detailed as I possibly can.

I am running CentOS 7 with Fog server version 1.4.4 SVN 6077.

The issue I am running into is that on the Fog server itself (10.10.0.65) I can open the management console. When i go any other computer I cannot access the console. I can ping the computer from everyone, just can’t access the console.

There is another issue which I believe is related and that is that when i attempt to do the PXE boot i get the error "http://10.10.0.65/fog/service/ipxe/boot.php/........Connection timed out (http://ipxe.org/4c0a6035). I already checked the “defualt.ipxe” folder and made sure the IP is correctly listed inside.

My assumption is that there is that there is something i missed or overlooked that is preventing other computers on this network from accessing the fog server.

Let me know if there is anything I may have overlooked, ideas, or if you need more info.
Thank you in advance.

@sebastian-roth No good news. I have given up on attempting to fix the issue. Ive spent way to many hours without any true fixes. It is random and only happens on 1 out of every 10 computers that are imaged. Figured I would just deal with it for now. I plan to re-do my entire FOG setup this holiday season. I plan to move the setup to be on an actual server machine instead of the PC it is currently on, hopefully fixing the issue for good.

Thank you for following up.
-Justin

Thank you for the response. And I apologize about the wait for my response. Probably should not put this in on a Friday.

@KnightRaven Basically all of the computers should be on the exact same level. All brand new and I am currently working with Dell Precision’s 7510. (happens with Latitudes 5570, 5580 as well).

I have a switch at my desk with 2 ports that I use for basically all of my deployments. I can have 2 brand new computers and run them simultaneous and they’ll work, then I could put two more when those are done and one of them will be slow (again this is an example, it be that I just grab one out of the box and it does not work). But the answer the question. I have moved the computer to different switches.

Have you tried rebooting when you notice it being slow?
Yeah, I have done about everything under then sun to the hardware. Replaced HDD or SSD, NIC Card, and the battery.

@george1421
It seems that once a computer goes slow, no matter how many times i image this (different ports or not) it will never change. As i mentioned above. I use the same two ports and patch cables for all of my deployments. It seems to be entirely random to the computer and not the ports.

For examples sake: I imaged 8 Dell Vostro 260’s last week, all using the same port and patch. These computers were not new out of the box and were using the same image. 7 of those computers completed the deployed image in under 30 minutes. One of those Vostro’s took overnight (3 hours at work and about 50%).

@Sebastian-Roth

I find it hard to believe that it is a network issue. Even after I know a computer is imaging slowly, I can start another one simultaneously and it will be imaging at a normal speed.

I did the tcpdump

Should be an image showing there were no packets lost. I left it running for about a minute while a had one of my computers that were imaging slow running.

I have a Fog Server running on Ubuntu version 1.4.4. SVN Revision 6077. I updated this about 3 or 4 months ago and this issue was happening before and after the update.

What happens while booting in PXE on a working computer is I will boot the computer using the “integrated NIC”, The computer will then begin to boot into the FOG menu. Normally this take 2-3 seconds. Once at the FOG menu I will then deploy and image and that takes around 20 minutes.

On a computer that does not work. I do the same steps except when I click on “integrated NIC”, the computer starts the sames steps then pauses on “TFTP…” for about 10 seconds then it will finish booting into the FOG menu. I will then deploy an image, but this time the image takes anywhere from 2 hours to 300 hours (just sat here and watched a computer get to 1.5% after 3 hours).

There is no correlation between what computers work and those that don’t. This has happened to me when I had 4 brand new computers straight of the box. Same model and everything, 3 worked fine 1 did not. I could keep going on this notion but i think the point is made that model does not matter nor does age.

I have tried lots of steps. Not sure if I should list every single one or not. Any ideas help I am really at a loss.

Also, let me know if you need more information or pictures.

Thank you.