the hint you sent me via chat has solved the problem great.

thank you very much.

@brechtvervaeke For DNSMASQ install I would follow this guide exactly: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

To the error, is the fog server on the same IP subnet as the target computer?

@fogbrain That message has 2 causes.

It can’t get an IP address It can’t make a http call to the fog server.

If you watch it boot you should see it get an IP address, if yes then that rules out #1. The second is the FOS Engine will attempt to reach the fog server (as you posted in the error above). If it can’t it will start the sequence over again of querying for dhcp then attempting to contact the fog server. It should do this 3 times then give up. You need to test from the same subnet as the pxe booting computer if you can reach the url you defined in your original post with a different computer on the same subnet as the pxe booting computer.

I don’t think its a spanning tree issue right now. That would usually (but not always) show up in the FOG iPXE menu not loading. You do need to have your switch ports in portfast mode. You can test to see if its spanning tree issue by placing a dumb (read cheap, unmanaged) switch between the building switch and the pxe booting computer. That cheap switch typically would not have spanning tree plus it keeps the building switch port from winking as the pxe booting computer starts up.

I was having the same problem and didn’t read all the way to the bottom. I was looking at the files in /tftpboot and found that the default.ipxe file had a string containing http://ip-address/service/ipxe/boot.php#params or something similar. I inserted fog and it booted up.

@wayne-workman It’s a Dell OptiPlex 3080. I am using FOG’s DHCP because I don’t have access to our company’s router. I have it working now. I’ve captured an image and going to try to deploy it tonight (I work second shift).

I’d love to get packets back and fourth between the wlan0 and eth0 devices so I can join systems to the domain without switching ethernet cables. Trying to work this out.

@207-tech said in Fog Service address is wrong:

/bin/fog.download it states it is unable to locate that directory

fog.download comes from the FOS Linux engine. When it throws that error it should printout the kernel parameters in the error message. Look to see if the old address is still displayed. If yes then look at the storage node configuration to make sure the default storage node has the proper IP address.

@george1421 I want to say thank you very much for your support and help.\It was very professional and fast, thanks again now I can continue enjoy a FOG solution in my environment

Best regards, Boris

@mashley With multcasting only one image is sent out from the server. So all the clients that participate in the multicast image work in lock step. So the speed of your image deployment is based on the slowest computer in the group. You do want to kind of group like systems (performance wise) together in a deployment group to get the best performance. If you have fast computers but one is behind a 100Mb/s link, that one behind the slow link will slow down the entire group.

@bsedash cross linking similar issue: https://forums.fogproject.org/topic/16244/fog-cannot-load-qlogic-network-driver-on-poweredge-r640/2

One solution two fixes. We might have a custom kernel soon to address this issue. I’m just waiting on feedback from the other thread.

@george1421 said in Database connection unavailable:

botched uploads

Nice thanks for the tips, worked

@george1421 Thanks. I’m going to debug a bit more next time I’m in the office.

@george1421 Thank you so much! That article helped immensely.

@chrisakak9
I think this is what you might need
https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/22

@flat4vw I found my answer got it updated.

@george1421 @Sebastian-Roth
hi guys,
the compression rate in the image caused the error
capturing and deploying works…
Thx 4 the support
thread closed … finally 😉

@juelson The output of the commands I asked you to run look normal except the directory listing of /images. There is a missing hidden file that FOG uses to know its connected to the correct image store.

There should be a file called .mntcheck in both /images and /images/dev This file is created by the fog installer so it should be there unless someone adjusted the contents of the /images directory.

So we can fix it with the following command. We will fix /images/dev so uploads work correctly while we are at it.

Key in these commands at the FOG Server’s linux console. You may need to use sudo if you are using a debian variant or do this as the root user.

touch /images/.mntcheck touch /images/dev/.mntcheck

This is a non destructive command so its OK to run them even if the file exists. Once the .mntcheck file is created you download should work better.