Hi
On Mar 11, 12:02 am, Peter Meier <[email protected]> wrote:
> > 2) puppetd had successfully connected to puppetmasterd before. When on
> > a following scheduled connection attempt puppetmasterd cannot be
> > reached (host down or network broken), puppetd terminates silently
> > instead of retrying later.
>
> this might be the cause for:http://projects.reductivelabs.com/issues/2888if
> you can provide any
> further details or even reproduce this problem with --trace --debug it
> would be very helpfull.
This one can be most easily reproduced.
Platform is Debian Lenny, puppetd is 0.25.1-2~bpo50+1_all.deb (from
backports)
On the puppetd host stop the daemon, then run:
puppetd --no-daemonize -v -d --trace
On the same host add a filter rule to drop the reply packets, thus
simulating a network or master failure because puppetd will not get
EPERM or so.
iptables -t filter -A INPUT -p tcp --sport 8140 --source
<puppetmaster ip-addr> -j DROP
wait...
the last messages are for me:
notice: Finished catalog run in 1.11 seconds
debug: Loaded state in 0.01 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for whiskey.domain.com
debug: Using cached certificate_revocation_list for ca
debug: Format s not supported for Puppet::Resource::Catalog; has not
implemented method 'from_s'
/usr/lib/ruby/1.8/timeout.rb:60:in `open': execution expired
(Timeout::Error)
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
from /usr/lib/ruby/1.8/net/http.rb:542:in `start'
from /usr/lib/ruby/1.8/net/http.rb:1035:in `request'
from /usr/lib/ruby/1.8/net/http.rb:772:in `get'
from /usr/lib/ruby/1.8/puppet/indirector/rest.rb:69:in `find'
from /usr/lib/ruby/1.8/puppet/indirector/indirection.rb:198:in
`find'
from /usr/lib/ruby/1.8/puppet/indirector.rb:51:in `find'
from /usr/lib/ruby/1.8/puppet/configurer.rb:94:in
`retrieve_catalog'
from /usr/lib/ruby/1.8/puppet/util.rb:417:in `thinmark'
from /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
from /usr/lib/ruby/1.8/puppet/util.rb:416:in `thinmark'
from /usr/lib/ruby/1.8/puppet/configurer.rb:93:in
`retrieve_catalog'
from /usr/lib/ruby/1.8/puppet/configurer.rb:145:in `run'
from /usr/lib/ruby/1.8/puppet/agent.rb:53:in `run'
from /usr/lib/ruby/1.8/puppet/agent/locker.rb:21:in `lock'
from /usr/lib/ruby/1.8/puppet/agent.rb:53:in `run'
from /usr/lib/ruby/1.8/sync.rb:230:in `synchronize'
from /usr/lib/ruby/1.8/puppet/agent.rb:53:in `run'
from /usr/lib/ruby/1.8/puppet/agent.rb:130:in `with_client'
from /usr/lib/ruby/1.8/puppet/agent.rb:51:in `run'
from /usr/lib/ruby/1.8/puppet/agent.rb:104:in `start'
from /usr/lib/ruby/1.8/puppet/external/event-loop/signal-
system.rb:97:in `call'
from /usr/lib/ruby/1.8/puppet/external/event-loop/signal-
system.rb:97:in `__signal__'
from /usr/lib/ruby/1.8/puppet/external/event-loop/signal-
system.rb:97:in `each'
from /usr/lib/ruby/1.8/puppet/external/event-loop/signal-
system.rb:97:in `__signal__'
from (eval):2:in `signal'
from /usr/lib/ruby/1.8/puppet/external/event-loop/event-
loop.rb:321:in `sound_alarm'
from /usr/lib/ruby/1.8/puppet/external/event-loop/event-
loop.rb:130:in `select'
from /usr/lib/ruby/1.8/puppet/external/event-loop/event-
loop.rb:130:in `each'
from /usr/lib/ruby/1.8/puppet/external/event-loop/event-
loop.rb:130:in `select'
from /usr/lib/ruby/1.8/puppet/external/event-loop/event-
loop.rb:116:in `iterate'
from /usr/lib/ruby/1.8/puppet/external/event-loop/event-
loop.rb:107:in `run'
from /usr/lib/ruby/1.8/puppet/daemon.rb:130:in `start'
from /usr/lib/ruby/1.8/puppet/application/puppetd.rb:116: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/lib/ruby/1.8/puppet/application.rb:306:in
`exit_on_fail'
from /usr/lib/ruby/1.8/puppet/application.rb:217:in `run'
from /usr/sbin/puppetd:159
No lock file problems occur.
dont forget to remove the filter:
iptables -t filter -D INPUT -p tcp --sport 8140 --source
<puppetmaster ip-addr> -j DROP
-gr
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" 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-users?hl=en.
