On Feb 6, 2009, at 5:28 PM, 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.
>
> I'm running puppet-0.24.6-1.el5 on Centos 5.2.
>
> [...@prcapp02 ~]$ sudo service puppet start
> Starting puppet:
> /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:735:in `use':
> Got 16
> failure(s) while initializing: change from absent to system_u failed:
> Execution of '/usr/bin/chcon -h -u system_u /var/log/puppet'
> returned 1:
> /usr/bin/chcon: can't apply partial context to unlabeled file
> /var/log/puppet (RuntimeError)
> ; change from absent to object_r failed: Execution of '/usr/bin/
> chcon -h
> -r object_r /var/log/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/log/puppet
> ; change from absent to var_log_t failed: Execution of '/usr/bin/
> chcon -h
> -t var_log_t /var/log/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/log/puppet
> ; change from absent to s0 failed: Execution of '/usr/bin/chcon -h -
> l s0
> /var/log/puppet' returned 1: /usr/bin/chcon: can't apply partial
> context
> to unlabeled file /var/log/puppet
> ; change from absent to system_u failed: Execution of '/usr/bin/
> chcon -h
> -u system_u /var/run/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/run/puppet
> ; change from absent to object_r failed: Execution of '/usr/bin/
> chcon -h
> -r object_r /var/run/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/run/puppet
> ; change from absent to var_run_t failed: Execution of '/usr/bin/
> chcon -h
> -t var_run_t /var/run/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/run/puppet
> ; change from absent to s0 failed: Execution of '/usr/bin/chcon -h -
> l s0
> /var/run/puppet' returned 1: /usr/bin/chcon: can't apply partial
> context
> to unlabeled file /var/run/puppet
> ; change from absent to system_u failed: Execution of '/usr/bin/
> chcon -h
> -u system_u /etc/puppet' returned 1: /usr/bin/chcon: can't apply
> partial
> context to unlabeled file /etc/puppet
> ; change from absent to object_r failed: Execution of '/usr/bin/
> chcon -h
> -r object_r /etc/puppet' returned 1: /usr/bin/chcon: can't apply
> partial
> context to unlabeled file /etc/puppet
> ; change from absent to etc_t failed: Execution of '/usr/bin/chcon -
> h -t
> etc_t /etc/puppet' returned 1: /usr/bin/chcon: can't apply partial
> context
> to unlabeled file /etc/puppet
> ; change from absent to s0 failed: Execution of '/usr/bin/chcon -h -
> l s0
> /etc/puppet' returned 1: /usr/bin/chcon: can't apply partial context
> to
> unlabeled file /etc/puppet
> ; change from absent to system_u failed: Execution of '/usr/bin/
> chcon -h
> -u system_u /var/lib/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/lib/puppet
> ; change from absent to object_r failed: Execution of '/usr/bin/
> chcon -h
> -r object_r /var/lib/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/lib/puppet
> ; change from absent to var_lib_t failed: Execution of '/usr/bin/
> chcon -h
> -t var_lib_t /var/lib/puppet' returned 1: /usr/bin/chcon: can't apply
> partial context to unlabeled file /var/lib/puppet
> ; change from absent to s0 failed: Execution of '/usr/bin/chcon -h -
> l s0
> /var/lib/puppet' returned 1: /usr/bin/chcon: can't apply partial
> context
> to unlabeled file /var/lib/puppet
> from /usr/lib/ruby/site_ruby/1.8/puppet/node/catalog.rb:136:in
> `apply'
> from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
> 731:in `use'
> from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
> from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
> 711:in `use'
> from
> /usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:197:in
> `initialize'
> from /usr/sbin/puppetd:328:in `new'
> from /usr/sbin/puppetd:328
> [FAILED]
This sounds a bit silly, but how confident are you that the install of
0.24.6 restarted puppetd?
It sounds like these selinux commands were never working on your
machine, so it could be that you were running an older version in
memory, and the restart started up that new version.
Otherwise... I think 0.24.7 will be better here, because it fixes
most of the SELinux problems, as long as you don't try to manage
selinux values without having access to the selinux libs (yes, sounds
silly, but people do it).
--
To be pleased with one's limits is a wretched state.
-- Johann Wolfgang von Goethe
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
