I am trying to use Nxlog on Windows to send events to syslog-ng. I have
configured Nxlog to use TLS, and both Nxlog and syslog-ng seem to report
a successful TLS negotiation. Yet when I actually generate an event using:
eventcreate /ID 1 /L APPLICATION /T INFORMATION /SO MYEVENTSOURCE /D
"Hello, world!"
I see the following logged by syslog-ng on the receiving side:
[...] invalid frame header; header = '' [...]
I have configured syslog-ng to use the syslog input, so it expects
syslog-IETF messages. I have a number of other non-Nxlog clients working.
My Nxlog configuration is this:
define ROOT C:\Program Files (x86)\nxlog
ModuleDir %ROOT%\modules
CacheDir %ROOT%\data
Pidfile %ROOT%\data\nxlog.pid
SpoolDir %ROOT%\data
LogFile %ROOT%\data\nxlog.log
<Extension syslog>
Module xm_syslog
</Extension>
<Input in>
Module im_msvistalog
</Input>
<Output out>
Module om_ssl
Host logserver.example.com
Port 6514
CAFile %ROOT%\cert\ca.pem
CertFile %ROOT%\cert\logserver.example.com.pem
CertKeyFile %ROOT%\cert\logserver.example.com.key
AllowUntrusted FALSE
Exec to_syslog_ietf();
</Output>
<Route 1>
Path in => out
</Route>
I have configured Nxlog to also write the syslog-IETF-encoded log to a
file. There I see something like:
<n>1 [DATE] [HOST] ...
which appears to be a valid syslog-IETF-format message.
I am at a loss as to what the problem might be. Does anyone have
experience with Nxlog to syslog-ng over TLS?
--
Mike
:wq
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
nxlog-ce-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
