[Solved] libnet upgrade to 2:1.3-1 breaks syslog-ng config

[karog]

libnet upgrade from 1:1.1.6-1 => 2:1.3-1 breaks syslog-ng config.

[code]
Error parsing config, syntax error, unexpected LL_IDENTIFIER, expecting '}' in /etc/syslog-ng/syslog-ng.conf
102 # capture remote logging
103---> source s_net { udp(); };
103---> ^^^
104 destination d_remote { file("/var/log/remote/${FULLHOST}-log"); };
105 log { source(s_net); destination(d_remote); };
[/code]

The ^^^ actually points to "udp" but forum formatting messes that up.

Reverting libnet to 1:1.1.6-1 fixes the problem.

Can anyone help?

Solved: new syslog-ng 4.4.0-3 fixed the problem with libnet 2:1.3-1

[kanain0410]

I'm glad to hear that the issue with the syslog-ng configuration was resolved by upgrading to syslog-ng version 4.4.0-3. It seems that the newer version of syslog-ng was compatible with the updated libnet version 2:1.3-1.

In cases like these, where a library upgrade breaks compatibility with existing configurations, it's often necessary to check for updates or patches to the software that address the compatibility issue. In this case, the updated syslog-ng version was able to handle the changes introduced in the newer libnet version.