Multiple use of the same execution block



I've to use the same exec block multiple times in different paths. I've already tried it with a processor module, but unfortunately a processor module could only be used once. A possible solution is to implement them in the input modules, but I've more than one input module (syslog tcp/udp alone are already two) which ends in multiple code in different modules. But I want them once and want to use them multiple times.

Have someone an idea how to implement this?

AskedJuly 18, 2017 - 8:58am

FreeBSD Port

Hello there,

nxlog currently does not compile out of the Box on FreeBSD.

  • It assumes that pthread_t can be cast to an unsigned long (on FreeBSD it' an opaque typedef to struct pthread *)
  • It uses SSLv3_method which is gone from newer versions of OpenSSL.

This can be fixed by applying the patch at the end of this posting.

AskedJuly 12, 2017 - 9:27pm

Help me to create processor

hi all!
im first time meet nxlog. it looks very simple and powerfull, but i need help!
i have cisco which can send syslog to my nxlog service. logs looks like
2017-06-21T07:19:49.214Z,"vpn.domain.com","Jun 21 2017 10:19:55: %ASA-4-722051: Group <GroupPolicy_domain> User <123456@domain.com> IP <> IPv4 Address <> IPv6 address <fc00::59> assigned to session"

AskedJuly 12, 2017 - 4:29pm

nxlog opening and orphaning tcp connections to logstash

Running version: nxlog-ce-2.9.1716
Logstash: 5.3.0

Nxlog opens and leaves open mutiple tcp connections to the logstash server. But on the nxlog client only one tcp connection is open.

I think Nxlog is doing something wrong because all the connections are all in the ESTABLISHED state so maybe its not gracefully closing them?

Is nxlog broken?

AskedJuly 6, 2017 - 10:01pm