- From: Peter Norton <
>
- To:
- Subject: [chef] Re: Re: Troubleshooting report/error handlers not appearing to send reports?
- Date: Fri, 27 Jan 2012 13:17:17 -0500
I have confirmed that if I use graypy I can send messages from the
client to the graylog2 server, so I've eliminated the network as being
the problem.
I'm now down to the question of why the same role/config that will
send a gelf message locally will not send it out to a server (still
confirmed with tcpdump not seeing an outbound datagram).
Any help is apreciated. I'll be looking at this a bit more today.
-Peter
On Fri, Jan 27, 2012 at 12:44 AM, Peter Norton
<
>
wrote:
>
Thank, I'll try that. I've confirmed that I can use nc to send udp
>
between source and destination (AWS only implements inbound filters).
>
As I said, the weirdest part was that I didn't see any port 12201
>
(udp) traffic leaving the system after the chef runs. I guess for
>
that part I'll start adding prints to the installed chef-gelf gem.
>
I'll use your server, too.
>
>
Thanks again,
>
>
-Peter
>
>
On Fri, Jan 27, 2012 at 12:36 AM, John E. Vincent (lusis)
>
<
>
>
wrote:
>
> On Thu, Jan 26, 2012 at 10:50 PM, Peter Norton
>
> <
>
>
> wrote:
>
>> I've enabled the gelf report handler per the instructions in the
>
>> chef_handler cookbook and the chef-gelf cookbook.
>
>>
>
>> I've got an odd situation. I'm putting in our syslog server
>
>> explicitly, so a host is set. The run starts like this:
>
>>
>
> <snip>
>
> If you're absolutely sure that there are no firewall rules on AWS
>
> blocking traffic (remember GELF is UDP), you can try an alternate
>
> debug method on another host (or on each instance if it matters)
>
>
>
> There's a gem I wrote (originally for logstash) called gelfd
>
> (https://github.com/lusis/gelfd)
>
>
>
> It comes with a bin script that starts a basic UDP server to catch and
>
> decode all gelf messages. It's easier to move around than your
>
> logstash server and easier than tcpdump machinations (imho).
>
>
>
> Again, I'd quadruple check your EC2 rules. Make sure that split
>
> horizon DNS is working properly on ec2 but you can use gelfd to help
>
> debug.
>
>
>
>>
>
>> Thanks,
>
>>
>
>> -Peter
Archive powered by MHonArc 2.6.16.