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:
can you add that info to the bugreport? thanks!
cheers pete
--
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.
