Closed elisiano closed 10 years ago
You don't seem to be doing anything obviously wrong. For some reason the remote log config is referencing f_puppet-agent
with a dash rather than using an underscore as defined in the filter config.
As far as I can tell it should work if you define the puppet-agent-a
logpath as follows.
'puppet-agent-a' => { logpath => 'puppet_agent' } ,
Thanks @hairmare, that fixed that specific case and the same hint applied for other 3 log paths.
'puppet-agent-a' => { logpath => 'puppet_agent' } ,
'puppet-master-a' => { logpath => 'puppet_master' } ,
[...]
'ulogd-a' => { logpath => 'netfilter' } ,
'uwsgi-a' => { logpath => 'uwsgi-common' } ,
Just as a remark, once the log paths were fixed, this errore came up:
Execution of '/sbin/service syslog-ng start' returned 1: Starting syslog-ng: Error resolving reference; content='destination', name='d_messages', location='/etc/syslo
g-ng/syslog-ng.conf.d/log.d/99_catch-all.conf:2:40'
I just needed to explicitly add the messages destination along of the remote one:
"messages" => {},
is that the intended behavior?
Now I just need to figure out why the remote is not listening for incoming network messages, but since it's a separate issue, I'm gonna report it separately.
Thanks again for your help.
So never mind my previous question about destinations, the defaults (messages, console, kernel) are overwritten by the remotes so they need to be specifically added.
Thanks for your help.
Hi, first of all thanks for this module. I'm pretty new at this so I might be overlooking something obvious.
So I compiled syslog-ng 3.5.6 for CentOS 6, I enabled all the log paths. On the server, the daemon starts without any issues, but on the other hand, the client fails with the following message:
And here's the generated config file:
Checking the config, f_puppet_agent is defined:
Am I doing something obviously wrong?
This is how the class is declared on the client ( $syslog_remote_host contains the remote server):