Fog was working fine until a power outage
-
Lol, no!
Can you verify that SELINUX is enabled/disabled? To do so, what’s the output of:
[code]cat /etc/sysconfig/selinux[/code]It should, hopefully, look like this:
[code]# This file controls the state of SELinux on the system.SELINUX= can take one of these three values:
enforcing - SELinux security policy is enforced.
permissive - SELinux prints warnings instead of enforcing.
disabled - No SELinux policy is loaded.
SELINUX=disabled
SELINUXTYPE= can take one of these two values:
targeted - Targeted processes are protected,
mls - Multi Level Security protection.
SELINUXTYPE=targeted[/code]
Especially with the SELINUX=disabled line!
-
Ah ha!
Does your system need SELINUX running?
-
[quote=“Tom Elliott, post: 18140, member: 7271”]Ah ha!
Does your system need SELINUX running?[/quote]
Not that I am aware. This machine is an old dell Optiplex 740 and only used for FOG -
Okay,
Run this command:
[code]sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/’ /etc/sysconfig/selinux[/code]Then reboot and try again!
-
[quote=“Tom Elliott, post: 18142, member: 7271”]Okay,
Run this command:
[code]sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/’ /etc/sysconfig/selinux[/code]Then reboot and try again![/quote]
I rebooted and tried again… and… Sucess!
tftp -4 localhost
tftp> get
(files) pxelinux.0
tftp>BUT… When I try from another machine I am still getting the can’t write to local file error.
-
what does the /var/log/messages say when this happens?
-
[quote=“Tom Elliott, post: 18144, member: 7271”]what does the /var/log/messages say when this happens?[/quote]
HOLY MOTHER OF GOD! I just rebooted my laptop to try the tftp command from another machine and I forgot it is set to boot from network. And guess what!? It booted up into FOG! WOOOT! Many Thanks! If you are ever in Jackson, TN I’ll owe you a beer!
-
Glad I could be of some help.
-
Now I can head home! Thanks again!
-
Based on the results, my guess is somebody already had this same type of issue but disabled it with:[code]setenforce 0[/code] on the server, which is why it was working. On the next reboot, because it wasn’t disabled before, it just reset to enforcing.
