1
answer

Route path branching

Hi,

please advise me how to configure the following setup:

  • several inputs (UDP, TCP, internal) joined into common path (i_udp, i_tcp, i_internal => p_pattern ...),
  • one global processor (pattern, filter)  module,
  • several outputs (file, UDP, TCP),
  • every message is delivered to one of outputs according to processor's decision.

I call it "route branching". The solutions I have come to so far:

AskedJanuary 10, 2016 - 7:17pm
1
answer

Source code of community edition for community

Hello,

will you, please, publish recent source code, the one the latest CE packages were built from? I made quite a few tests with 2.9.1504 on Debian and now would like to patch some minor problems of pm_pattern (and contributing back), but last published sources are 2.8.1248. And I can not get a changelog between theese two versions either (the changelog packaged in the binary package, as mentioned in the previous post, is too brief):

AskedJanuary 8, 2016 - 5:06pm
1
answer

NXLOG 2.9.1504 New Features, Bug Fixes, Etc

Where can I find the NXLOG code history for the various releases? I am currently on NXLOG 2.9.1347 and need to know what's new and fixed in 2.9.1504 but cannot locate where this information is.

Thank You,

AskedJanuary 7, 2016 - 9:40pm
1
answer

Gelf - TCP doesn't work with comunity edition

Hi all,

I tried to use the gelf extension with the tcp module, but it doesn't work.
I saw tht the commercial version includes a special tcp gelf enxtension. Supports the community edition the usage of GELF over TCP?

Kind regards

Michael

AskedJanuary 6, 2016 - 9:39am
2
answers

No connection could be made because the target machine actively refused it.

Hello,
nxlog was sending to nagios log server just fine for a few days and then all of a sudden we started seeing the below errors in the nxlog.log file that are preventing logs from being sent.

ERROR om_tcp send failed; An existing connection was forcibly closed by the remote host.

ERROR couldn't connect to tcp socket on xx.xx.xxx.xx:3515; No connection could be made because the target machine actively refused it.

AskedJanuary 4, 2016 - 10:33pm

Pages