Fog was working fine until a power outage

[To_Tha_Cloud]

Good Morning All!

This is my first post here. I hope I provided enough information.

We had a power outage over last weekend and when I tried to image a machine after turning the FOG server back on I could not connect it. I found the problem to be the firewall. So I turned it off. Then the next issue was -

PXE-T00: Permission Denied
DASH-E36: Error received from TFTP server
DASH-M0F: Exiting Option ROM

After some googling I though I should chmod 666 the /tftpboot directory and all the contents. Once I did that I am now getting the following:

DASH-E32: TFTP open timeout
TFTP…

What have I managed to hose up?

I am running CentOS release 6.4 (Final) with latest version of FOG. The machine I am trying to image is a Lenovo M88 Desktop. I have imaged several of these before the power outage.

Thanks in advance for any help.

[Tom Elliott]

make sure the folder is also accessible to the fog user:

[code]chown -R fog:root /tftpboot[/code]

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18029, member: 7271”]make sure the folder is also accessible to the fog user:

[code]chown -R fog:root /tftpboot[/code][/quote]

I did that and am still getting the same messages.

I found a site that showed me how to test it from inside windows with command line when I set the server up, but I didnt write it down and my google fu is failing me.

[Tom Elliott]

Try tftp command line windows lookup.

[Tom Elliott]

Also,

Please try service xinetd restart as that should control tftp for Centos 6.4

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18094, member: 7271”]Also,

Please try service xinetd restart as that should control tftp for Centos 6.4[/quote]

I tried the following command in Windows:
[CODE]tftp x.x.x.x get pxelinux.0[/CODE]
and I get:
[CODE]tftp: can’t write to local file ‘pxelinux.0’[/CODE]

Seems like a permission issue. But I’m somewhat of a newb.

[To_Tha_Cloud]

forgot to mention I also restarted the service you mentioned as well.

[Tom Elliott]

Well,

One way to be ensure it’s a permissions issue is to make sure all permissions are out of the question. Most Directories follow a 755 rule, and many of the files follow that as well. It sounds like it can’t write any request data to the filesystem, which means when you’re accessing it, it can’t modify the last access time. One way to verify if it’s permissions is to put the whole directory as rwx all the way through with:[code]chmod -R 777 /tftpboot[/code]

Then try your ftp command. if that allows it to work, then try [code]chmod -R 755 /tftpboot[/code]

It should still work. I can’t fully remember, though, if you have to specify the full path either, in reference to the command you’re writing in windows…

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18110, member: 7271”]Well,

One way to be ensure it’s a permissions issue is to make sure all permissions are out of the question. Most Directories follow a 755 rule, and many of the files follow that as well. It sounds like it can’t write any request data to the filesystem, which means when you’re accessing it, it can’t modify the last access time. One way to verify if it’s permissions is to put the whole directory as rwx all the way through with:[code]chmod -R 777 /tftpboot[/code]

Then try your ftp command. if that allows it to work, then try [code]chmod -R 755 /tftpboot[/code]

It should still work. I can’t fully remember, though, if you have to specify the full path either, in reference to the command you’re writing in windows…[/quote]

Changed the permissions to 777 and tried to rerun the command. I still get the same error. I even made up a filename to make sure I didnt have to enter the full path and it came back with a file not found. So I know my command should work. Scratches head

[Tom Elliott]

This is starting to make some sense.

The files that you’re working with are all currently 666, or rw-rw-rw- try chmoding all folders as 755 with:
[code]chmod -R 755[/code]

Then perform:
[code]find /tftpboot -type f -exec chmod 744 {} ;[/code]

This should put all files as rwxr–r-- which is what my system looks like. It will also place all the directories as their natural state of rwxr-xr-x

[Tom Elliott]

This may sound really odd, but can you try tftp from your fogserver with:

[code]cd
yum -y install tftp
tftp -4 localhost
get
pxelinux.0
exit[/code]

Does this work?

[Tom Elliott]

This is also going to sound a bit odd, I think, but is there a firewall running on the FOG Server? Is iptables disabled?

To find out run:
[code]iptables -L -n[/code]

If you get the text such as:
[code]Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination[/code]

Then chances are it’s already disabled. If you get anything more than that run:

[code]chkconfig iptables off; service iptables stop[/code]

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18113, member: 7271”]This is starting to make some sense.

The files that you’re working with are all currently 666, or rw-rw-rw- try chmoding all folders as 755 with:
[code]chmod -R 755[/code]

Then perform:
[code]find /tftpboot -type f -exec chmod 744 {} ;[/code]

This should put all files as rwxr–r-- which is what my system looks like. It will also place all the directories as their natural state of rwxr-xr-x[/quote]

Do I need to restart any services?

[Tom Elliott]

No, you shouldn’t have to restart any services that I’m aware of, is there a reason you ask?

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18114, member: 7271”]This may sound really odd, but can you try tftp from your fogserver with:

[code]cd
yum -y install tftp
tftp -4 localhost
get
pxelinux.0
exit[/code]

Does this work?[/quote]
I get the following:

]# tftp -4 localhost
tftp> get
(files) pxelinux.0
Error code 0: Permission denied

I am running as root.

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18116, member: 7271”]This is also going to sound a bit odd, I think, but is there a firewall running on the FOG Server? Is iptables disabled?

To find out run:
[code]iptables -L -n[/code]

If you get the text such as:
[code]Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination[/code]

Then chances are it’s already disabled. If you get anything more than that run:

[code]chkconfig iptables off; service iptables stop[/code][/quote]

The firewall is off.

[Tom Elliott]

what is the output of the command:
[code]umask[/code]

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18122, member: 7271”]what is the output of the command:
[code]umask[/code][/quote]

0022

[Tom Elliott]

Okay,

When you performed the install, did you have any special parameters involved. Such as:

[LIST]
[]Is your tftpboot folder in a location other than /tftpboot?
[]Is your tftpboot folder hosted on another filesystem?
[/LIST]
Has your system performed a filesystem check and/or is your filesystem on a RAID setup? Is it possible one of the drives has failed?

[To_Tha_Cloud]

[quote=“Tom Elliott, post: 18124, member: 7271”]Okay,

When you performed the install, did you have any special parameters involved. Such as:

[LIST]
[]Is your tftpboot folder in a location other than /tftpboot?
[]Is your tftpboot folder hosted on another filesystem?
[/LIST]
Has your system performed a filesystem check and/or is your filesystem on a RAID setup? Is it possible one of the drives has failed?[/quote]

The only special perameter was /images is mounted on a seperate drive. I just checked it and it appears to be mounted properly and I can navigate to it.
The system as far as I know has not performed a filesystem check and I am not on a RAID setup.