Unable to locate configuration File

Man, what an odd turn of events. I came back from a 2 week vacation at work, only to find that my server:
(1) Was “unable to connect to TFTP server”. Fixed that by a couple of reinstalls of FOG until I got it right.
(2) Attempted to UPLOAD an image, and recieved an “Unable to locate configuration file” message.

I boot off of CDROM using iPXE, which worked from August until now. Here’s basically what my boot looks like. This is not my actual, but an example copied from elsewhere that is the same…

Well, it only took 3 months, but I’ve solved this one… or at least I know what the problem is.

REVIEW:
I was using iPxe CDROMs for the machines that connect to the FOG server. I do this because my school district isn’t “friendly” towards my FOG server, and won’t let me make any sort of changes to the network, or have my own DHCP server.

iPxe worked great until December/January. I went away for two weeks, then came back to a non-working FOG server. Specifically, I could not UPLOAD images to the FOG server any more.

TODAY:
Today, after playing with iPxe for a few hours, I noticed that the config utility was showing a “second” TFTP server on the network with a different IP and a different default “filename” setting than mine. Basically, while I was setting iPxe correctly, some of the config settings from the “other” TFTP server on the network were being mixed in with my iPxe settings.

BOTTOM LINE:
I was logging into my FOG server OK, TFTP was working OK, the FOG server is configured OK, but when it came time to grab “config.cfg”, everything fell apart. Unknown to me, I was trying to grab config.cfg from the OTHER TFTP SERVERS directory structure somehow.

SOLUTION: I will have to add additional iPXE “set” or “clear” commands to make sure the settings from the other TFTP server are not in place before booting the pxelinux.0 image.

Yea, I have considered rebuilding the server. I may have to if I can’t solve this soon.

I’ll comb the configs one last time, and 777 everything and see if that helps. If not, I have an old backup that dates to WAY before the issues started, so I may have to spend a day and rebuild everything. The sad part is that it worked great, I left for two weeks, and now it’s hosed.

Another concerns is that the district I work for controls the network infrastructure, and they may have changed the switches or DHCP server or something.

Your issue is definitely a strange one that I have not encountered… much as I hate suggesting it, have you tried rebuilding the server from scratch?

A terribly not secure test would be to blast away all permissions on /tftpboot/ with something like chown -R fog.root /tftpboo/ && chmod -R 777 /tftpboot/

Another thing to consider would be to check the following configs:
tftpconfig="/etc/xinetd.d/tftp";
tftpconfigupstartconf="/etc/init/tftpd-hpa.conf" (Ubuntu only)
tftpconfigupstartdefaults="/etc/default/tftpd-hpa" (Ubuntu only)

Ok, I’ve been messing with this for a couple of months now, and I still can’t get it to work. I’ve put off imaging my lab multiple times. I’m getting a bit desperate here :-)

I’ve reinstalled FOG multiple times, deleting anything that even remotely has FOG written anywhere on it.

I’ve tested TFTP from a Windows box with the FOG user, it works fine, pxelinux.0 is visible, etc.

I’ve tested FTP from a Windows box with the FOG user, it works fine, the “default” config file is visible, etc.

The Fog server is installed fine, all is well. I can create tasks and they show up in the tftpboot folder with the proper MAC address associated with them.

And yet, I still get the “unable to locate configuration file” error, over and over.

ANY suggestions, any stab in the dark, anything… I’m getting to the point where I will have to revert to Clonezilla to get this lab imaged. Is there a listing of what the file permissions should be that I can compare to?

However, I only came here after reinstalling FOG 3 times, tweaking the FOG user passwords multiple times, changing paths many times, and changing permissions on multiple folders multiple times. So I’ve been trying pretty hard to solve this issue on my own :-)

Thanks for the reply. I already have a task in place, and it is showing up properly as a file named with the MAC Address of the machine. The config file is in place also. I guess I’m going to have to go over the permissions with a fine toothed comb and try different things. Attached is a screen shot showing the folder/files/permissions for default on my Ubuntu machine.
[ATTACH=full]12[/ATTACH]

Check /tftpboot/pxelinux.cfg/default on the FOG server. Make sure the file is there and correct. It sounds like it’s accessing the TFTP server but cannot find or read the default config file, either because it doesn’t exist or maybe a permissions issue. A quick test would be to create a debug task for one of your hosts. Whenever the FOG server creates a task it writes a host specific config file, so when the client boots it wouldn’t need to look for the default config because it would have it’s own. If that doesn’t work then check the permissions higher up on the directory structure to make sure that it’s not locked down in some way that prevents access to the /tftpboot/pxelinux.cfg/ directory.