Syslog Oddity

[Laxarus]

I am pushing RT-AC5300 asus merlin firmware (384.13_0) logs to the local syslog server. My settings are set to:
Default message log level: Warning
Log only messages more urgent than: Warning

But when I check the syslog server I got a flood of messeges like this:

11.10.2019
20:23:24
Info
192.168.1.195
daemon
lldpd
interface 12 does not have a name or an address, skip
11.10.2019
20:23:24
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:23:24
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:23:10
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:23:10
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:23:02
Info
192.168.1.195
daemon
lldpd
interface 12 does not have a name or an address, skip
11.10.2019
20:23:00
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:22:25
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:22:25
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:22:13
Info
192.168.1.195
daemon
lldpd
interface 12 does not have a name or an address, skip
11.10.2019
20:22:13
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip
11.10.2019
20:22:13
Info
192.168.1.195
daemon
lldpd
interface 13 does not have a name or an address, skip

When I go to this ip address, it is Lyra unit homepage which is just for information.
The lyras are set as aimesh nodes.

Anyway, the odd thing is why do I see those messeges on the syslog server even though the log level is "Warning"?

Is it a bug or some other issue?
Any help?

 

[Greg72]

It is a systemd-networkd oddity.

 

[Laxarus]

So is it a bug?

 

[ColinTaylor]

I believe @Greg72 was referring to the cause of the lldpd errors rather than the question that you actually asked.

No, it's not a bug. syslog messages of all priorities are sent to the syslog server (local and remote). The setting on each syslog server then determines which priority levels to display in its log.

 

[Greg72]

I believe @Greg72 was referring to the cause of the lldpd errors rather than the question that you actually asked.

No, it's not a bug. syslog messages of all priorities are sent to the syslog server (local and remote). The setting on each syslog server then determines which priority levels to display in its log.

No, the issue the OP is pointing out has to do with systems-networkd and has been around forever.

 

[ColinTaylor]

No, the issue the OP is pointing out has to do with systems-networkd and has been around forever.

I don't see how systems-networkd issues are relevant to his question '...why do I see those messages on the syslog server even though the log level is "Warning"?' (the messages having a log level of "Info"). systems-networkd has nothing to do with the syslog server.

 

[Laxarus]

Well, one issue is that why is router pushing info level messages to the syslog server @ColinTaylor pointed out that it is default behavior.
So, systems-networkd is also a separate issue of which it generates these flooding "info" messages.
AM I right?

 

[Greg72]

Yes, which has become normal with Mesh systems You have to remember that the code for systemd-networkd has not kept up with the way that wifi is moving and it is nothing to worry about with seeing that in the logs.

 

[Laxarus]

Ok, thanks for the clarification.

 

[ColinTaylor]

AFAIK the RT-AC5300 doesn't run systemd-networkd (maybe the Lyra does?) and we can see that the messages are in fact being generated by lldpd in response to a netlink message. Whether that's normal or not for your particular setup I have no idea.

It sounds like this is something that either needs to be fixed on the Lyra side or you need to reduce the logging level on your syslog server.

 

[Greg72]

Yes, lldp is one in the same. Both it and systemd-networkd have the same issue. You tend to find more out there on this error if you search under systemd-networkd.

 

[mr-nobody]

Hi Laxarus

I have the exact same issue.
Did you ever find a way to either have Lyra stop sending these log entry's or get your SysLog server to ignore them?

Cheers.

 

[ColinTaylor]

@mr-nobody If you just want to stop the messages appearing in the log of your remote syslog server then you need to create a filter on the remote syslog server.

The exact file and syntax will depend on what syslog server you are using. For example, for rsyslog you would add filters in either /etc/rsyslog.conf or /etc/rsyslog.d/filtername.conf