Hello.  I think this is a bug, but I don't understand it well enough yet 
to proclaim it as such a the bug tracker.

A machine I am looking to run puppetmaster on, is having a reverse DNS 
problem at the moment (reverse DNS of its IP address fails).  Of course 
I know the answer is to fix that reverse DNS, and that is in progress.

In the meantime, it look some looking to figure out this failure.  When 
I run "puppetmasterd", it appears to succeed, and put a few non-error 
lines in its log file, then exits.  By running with --no-daemonize I got 
a stack trace:


# puppetmasterd --no-daemonize
/usr/lib/ruby/1.8/webrick/utils.rb:63:in `getaddrinfo': getaddrinfo: 
Name or service not known (SocketError)
         from /usr/lib/ruby/1.8/webrick/utils.rb:63:in `create_listeners'
         from /usr/lib/ruby/1.8/webrick/ssl.rb:87:in `listen'
         from /usr/lib/ruby/1.8/webrick/server.rb:63:in `initialize'
         from /usr/lib/ruby/1.8/webrick/httpserver.rb:24:in `initialize'
         from /usr/lib/ruby/1.8/puppet/network/http/webrick.rb:33:in `new'
         from /usr/lib/ruby/1.8/puppet/network/http/webrick.rb:33:in 
`listen'
         from /usr/lib/ruby/1.8/puppet/network/server.rb:128:in `listen'
         from /usr/lib/ruby/1.8/puppet/network/server.rb:143:in `start'
         from /usr/lib/ruby/1.8/puppet/daemon.rb:128:in `start'
         from 
/usr/lib/ruby/1.8/puppet/application/puppetmasterd.rb:87:in `main'
         from /usr/lib/ruby/1.8/puppet/application.rb:226:in `send'
         from /usr/lib/ruby/1.8/puppet/application.rb:226:in `run_command'
         from /usr/lib/ruby/1.8/puppet/application.rb:217:in `run'
         from /usr/sbin/puppetmasterd:66


I think it would be an improvement if:

* puppetmasterd didn't need getaddrinfo to work

* If it does need getaddrinfo to work, state in the error or logfile 
what it is trying to look up

* If it does need getaddrinfo to work, fail early, rather than appear to 
succeed then exit silently. (This would make it more straightforward to 
get proper behavior from an init.d script also - such scripts are 
supposed to only return success if the daemon really started.)


I'm using the super-fresh Puppet 0.24.8.

I'd be thrilled to find out that I've missed something obvious, of course.


-- 
Kyle Cordes
http://kylecordes.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
-~----------~----~----~----~------~----~------~--~---

Reply via email to