[syslog-ng] restart vs reload

Antal Nemes (anemes) Antal.Nemes at oneidentity.com
Mon Mar 9 07:36:30 UTC 2020


You need to set keep-alive(no):

For example:

@version: 3.26

log {
  source { example-msg-generator(num(1)); };
#  destination { network(localhost port(5555) transport(udp) keep-alive(no)); };
  destination { syslog(localhost port(5555) transport(udp) keep-alive(no)); };

From: syslog-ng <syslog-ng-bounces at lists.balabit.hu> on behalf of Alexandre Santos <alexandre.rosas.santos at gmail.com>
Sent: Friday, March 6, 2020 21:02
To: Syslog-ng users' and developers' mailing list <syslog-ng at lists.balabit.hu>
Subject: [syslog-ng] restart vs reload

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

I am trying to dynamically change the output message format between RFC3164 and RFC5424.

root at localhost:~# diff /etc/syslog-ng/syslog-ng.conf /root/syslog-ng.conf.bak
<     network("" transport("udp") ip-protocol(4) port(514)
>     syslog("" transport("udp") ip-protocol(4) port(514)

If I use: "/usr/sbin/service syslog-ng restart" it works fine, but if I use "/usr/sbin/syslog-ng-ctl reload", the message format does not change.

I am using syslog-ng version 3.19

Any thoughts?

Thanks & Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20200309/34cf9464/attachment.html>

More information about the syslog-ng mailing list