David Dyer-Bennet wrote:
> Darned thing is suddenly failing. We had a reboot last night, and I
> changed a couple of files today too, so either one could somehow be
> responsible. But I can't figure out how from this crash. First I noticed
> that my changes weren't updating. Then I noticed that puppet wasn't
> running. Then I found that it won't, in fact, run.
>
> /selinux contains only a single file, enable, which contains the character
> 0. Selinux is in fact disabled.
Normally, /selinux is a proc-like filesystem which contains information about
the state of selinux. If you have selinux completely disabled, though, it
shouldn't be mounted at all, and so should be completely empty. This sounds
like something tried to unconditionally write out to the enable file without
seeing if it was actually mounted first, and the existence of this file in
turn confused the selinux code of the file type.
So, in short, try deleting /selinux/enable and see if that fixes things.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
