Cool, glad you got it going Sent from a phone
On Feb 8, 2012, at 11:26 AM, Peter Norton <
">
> wrote: Working. I've changed it to adding the node[:graylog2][:gelf_udp_server] property for myself.
-Peter On Wed, Feb 8, 2012 at 11:48 AM, Chris <
">
> wrote:
i ended up setting :rsyslog_server => true on my graylog server as well.
On Wed, Feb 8, 2012 at 8:29 AM, Peter Norton <
" target="_blank">
> wrote:
OK, I see the error that I made. The search returns the node, and the node is dereferenced via loghost['fqdn'] as you saw. It will send to the local host, I think, because that probably evaluates to 0 if you pass in a string. I'm passing in a safeguard value of loghost={'fqdn' => 'loghost.mycompany.com'} now to see if that works better.
Let me try logging from a remote host now ;)
-PeterOn Wed, Feb 8, 2012 at 11:07 AM, Chris <
" target="_blank">
> wrote:
exactly.
On Wed, Feb 8, 2012 at 8:02 AM, Peter Norton <
" target="_blank">
> wrote:
So you'd set the log server as a string, e.g. 'loghost.mycompany.com' and it didn't work, but using log_server['fqdn'] returned a workable value, and even though presumably the resulting string would still be 'loghost.mycompany.com' either way, the latter worked and the former didn't?
-Peter On Wed, Feb 8, 2012 at 10:54 AM, Chris <
" target="_blank">
> wrote:
I was able to get a remote host to work this morning (although it was a VM on the same host as the graylog server). so the handler doesn't seem to be broken. my problem was that i'd changed :server from the code given on the handler wiki to the name of the graylog server. changing it back to :server => log_server['fqdn'] did the trick.
On Tue, Feb 7, 2012 at 8:53 PM, Chris <
" target="_blank">
> wrote:
Thanks Peter,
I just started testing this handler this afternoon, for a total of 3 hrs. I'm going to have time tomorrow to work on it and will post if i find anything. But it seems like you've pretty much covered everything.
On Tue, Feb 7, 2012 at 8:48 PM, Peter Norton <
" target="_blank">
> wrote:
No updates or leads. I'm going to look harder now that it's not just me. Any help from opscode on how to best troubleshoot this would be appreciated. Maybe shef is the best way to look at this.
-Peter
On Tue, Feb 7, 2012 at 8:40 PM, chris <
" target="_blank">
> wrote:
I just started playing around with this, but I'm running into the same problem.
Have you had any progress since the last update on this thread?
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
-- Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law.
-- Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law.
-- Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law.
|