On 03/21/2011 03:10 PM, jcbollinger wrote:
On Mar 16, 10:27 am, Dennis Jacobfeuerborn<djacobfeuerb...@gmail.com>
wrote:
Wow, apparently running a "tcpdump -nn port 8140" un-wedges puppet and
brings things back to normal. Problem is that I have no clue how or why
running a tcpdump could possibly matter here even though it apparently does.
Does anyone have an idea what might be going on here?
Hmm. Port 8140 is the one that puppetd will listen on when you set
listen=true in puppet.conf.<speculation type="wild">It is
conceivable, though I would certainly account it a bug, that
unexpected packets queued up on port 8140 might confuse puppetd. In
that case, it might make sense that draining the queue via tcpdump
restores service.</speculation>
If you're just using puppet in ordinary client/server mode then you
shouldn't need any of that; in that case make sure it's switched off
(the default), and that your local firewall is blocking the port (both
TCP and UDP).
Doesn't puppetd listen on 8139?
-Cody Robertson
--
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.
