On Mar 16, 11:27 am, Dennis Jacobfeuerborn
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
On 03/21/2011 03:10 PM, jcbollinger wrote:
On Mar 16, 10:27 am, Dennis Jacobfeuerborn
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
On Mar 16, 10:27 am, Dennis Jacobfeuerborn
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 a
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?
Regards,
Dennis
--