Issue #1873 has been updated by luke.

It seems like there's a bunch of stuff going on here.  You've got a log message 
that says the run is being skipped, which could be why puppetd is exiting:
<pre>
info: Ignoring running Puppet::Network::Client::Master
notice: No clients were run
</pre>

I'm not actually convinced those logs you see are the logs from the daemon that 
you've started.  Do you have another daemon running in the background but 
logging to stdout?

Certainly Puppet doesn't just die for lots of other people, so we need to 
figure out what else is going on in your environment.
----------------------------------------
Bug #1873: puppetd crashing with ruby error
http://projects.reductivelabs.com/issues/1873

Author: harisekhon
Status: Needs more information
Priority: High
Assigned to: 
Category: 
Target version: 
Complexity: Unknown
Affected version: 0.24.6
Keywords: 


puppetd often crashes with a ruby error.Otherwise puppet works, it pulls source 
files, sets permissions etc... when it is running, it often needs to be 
restarted so I started running it with --verbose --no-daemonize to see what was 
going on, looks like a code bug in the underlying ruby somewhere...

Seems to often be triggered when I am changing site.pp or classes files and 
then hitting "killall -USR1 puppetd", so possibly it is choking on 
configuration mistakes here and there, but other times it just says there is an 
errors on line x: blah blah and doesn't die. Either way configuration mistakes 
shouldn't cause the entire thing to die, shouldn't it just used the cached 
working version?

Here is the full output:
<pre>
notice: Caught USR1; triggering client run
info: Ignoring running Puppet::Network::Client::Master
notice: No clients were run
Jan 19 12:36:33 hostname puppetd[17759]: Caught USR1; triggering client run
Jan 19 12:36:33 hostname puppetd[17759]: Ignoring running 
Puppet::Network::Client::Master
Jan 19 12:36:33 hostname puppetd[17759]: No clients were run

[r...@hostname ~]# notice: Finished catalog run in 96.56 seconds
err: /File[/var/lib/puppet/ssl/private_keys/hostname.domain.com.pem]: Failed to 
retrieve current state of resource: can't convert nil into String
err: /File[/var/lib/puppet/ssl/csr_hostname.domain.com.pem]: Failed to retrieve 
current state of resource: can't convert nil into String
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:735:in `use': Got 2 
failure(s) while initializing: Failed to retrieve current state of resource: 
can't convert nil into String; Failed to retrieve current state of resource: 
can't convert nil into String (RuntimeError)
        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/util/settings.rb:517:in `reuse'
        from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:515:in `each'
        from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:515:in `reuse'
        from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
         ... 12 levels...
        from 
/usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:116:in 
`iterate'
        from 
/usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:107:in 
`run'
        from /usr/lib/ruby/site_ruby/1.8/puppet.rb:320:in `start'
        from /usr/sbin/puppetd:437
Jan 19 12:36:57 centostest64 puppetd[17759]: Finished catalog run in 96.56 
seconds
Jan 19 12:36:57 centostest64 puppetd[17759]: 
(/File[/var/lib/puppet/ssl/private_keys/hostname.domain.com.pem]) Failed to 
retrieve current state of resource: can't convert nil into String
Jan 19 12:36:57 centostest64 puppetd[17759]: 
(/File[/var/lib/puppet/ssl/csr_hostname.domain.com.pem]) Failed to retrieve 
current state of resource: can't convert nil into String

[2]+  Exit 1                  puppetd --verbose --no-daemonize


# puppetd --version
0.24.6

</pre>


----------------------------------------
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to