Hello,

You need to set keep-alive(no):
https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.24/administration-guide/keep-alive

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)); };
};

Br,
  Antal

From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of Alexandre Santos <alexandre.rosas.santos@gmail.com>
Sent: Friday, March 6, 2020 21:02
To: Syslog-ng users' and developers' mailing list <syslog-ng@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.

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

root@localhost:~# diff /etc/syslog-ng/syslog-ng.conf /root/syslog-ng.conf.bak
365c365
<     network("192.168.122.1" transport("udp") ip-protocol(4) port(514)
---
>     syslog("192.168.122.1" 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,
Alex