[7.0.0-beta.2] ntpd spam

same for me

unraid-1-diagnostics-20240719-0743.zip

@alturismoplease post your diags as well, to see if there's something in common with sonic6, I don't see this issue with my servers.

8 minutes ago, JorgeB said:

please post your diags as well

well well ...

 

AlsServerII diags attached, thats the one where the screens are from my report

 

AlsServer diags attached, fired it up from sleep  same symptoms,

1/ before changing and

2/ right after changing timeserver there is again that log entry ...

alsserverii-diagnostics-20240719-1212.zip alsserver-diagnostics-20240719-1208.zip alsserver-diagnostics-20240719-1211.zip

Please post output of:

 

cat /etc/ntp.conf | grep interface

 

4 hours ago, JorgeB said:

Please post output of:

 

root@AlsServerII:~# cat /etc/ntp.conf | grep interface
interface ignore wildcard
interface listen 192.168.1.4 # br0
interface listen 192.168.1.9 # br0
interface listen 2a02:810b:5d40:2319:9e6b:ff:fe25:d46e # br0
root@AlsServerII:~# 

 

192.168.1.4 br0 device physical NIC in br mode

 

192.168.1.9 keepalived virtual device

18 minutes ago, alturismo said:

192.168.1.9 keepalived virtual device

Can you retest without this interface?

1 hour ago, JorgeB said:

Can you retest without this interface?

i will when i find some time (and motivation )

 

but afaik @sonic6 doesnt use keepalived on the host like me and he has the same issue, lets see when he returns.

1 minute ago, alturismo said:

but afaik @sonic6 doesnt use keepalived

Probably not, but also post output of

 

1 hour ago, alturismo said:

cat /etc/ntp.conf | grep interface

To see  if there's something else there

4 minutes ago, JorgeB said:

Probably not, but also post output of

 

1 hour ago, alturismo said:

cat /etc/ntp.conf | grep interface

To see  if there's something else there

 

root@Unraid-1:~# cat /etc/ntp.conf | grep interface
interface ignore wildcard
interface listen 192.168.0.50 # eth0
interface listen fd00::aaa1:59ff:fe2b:ccfd # eth0
interface listen 2003:c0:cf2c:cd00:aaa1:59ff:fe2b:ccfd # eth0
root@Unraid-1:~# 

 

no, there is only keepalived inside a LXC container on my server

 

6 minutes ago, sonic6 said:

no, there is only keepalived inside a LXC container on my server

Looks look you have two IPv6 addresses for the same interface, any idea where the second one is coming from?

1 minute ago, JorgeB said:

any idea where the second one is coming from?

2003:... is the public one from ISP

fd00::... is the internal one ULA (https://en.wikipedia.org/wiki/Unique_local_address)

there must be also a third one... (LLU)

I've got the same problem.

5 minutes ago, pkoci said:

I've got the same problem.

☝️please post diagnostics

12 minutes ago, sonic6 said:

2003:... is the public one from ISP

fd00::... is the internal one ULA

 

OK, not really familiar with IPv6, just enabled it in a test server because I saw that both you and Alturismo were using it, though me and him just have one address there, but not sure if that is relevant for this.

ipv6 is more and more common in germany. fd00:: addresses are static addresses for LAN communication. while the prefix on the ipv6-addresses you get from your ISP will change from time to time, the ULA address will stay static.

Attaching my diagnostics which also has the same message for a server with IPv4 only

 

Linking similar reports so we have a single discussions:

 

 

sam-diagnostics-20240719-2213.zip

Anyone affected please post together with the diags the output of:

 

cat /etc/ntp.conf | grep interface

 

 

Tower:

interface ignore wildcard
interface ignore ipv6
interface listen 192.168.192.8 # eth0

 

Sam:

interface ignore wildcard
interface ignore ipv6
interface listen 192.168.192.41 # eth0
interface listen 192.168.192.240 # eth0

 

Both having this issue

tower-diagnostics-20240720-1208.zip sam-diagnostics-20240719-2213.zip

Thanks, there goes my theory about multiple interfaces in ntp.conf, since tower only has one, I'll see if I can find something in common between all the diags, because I still cannot reproduce this.

12 minutes ago, JorgeB said:

Thanks, there goes my theory about multiple interfaces in ntp.conf, since tower only has one, I'll see if I can find something in common between all the diags, because I still cannot reproduce this.

 

Your comment made me realize I have another server that doesn't experience that issue so I can compare settings to it.

The first difference I found was that it had "Host access to custom networks" turned off while other servers (Tower & Sam) has this setting turned on.

 

Turning on this and rebooting the server started logging this message:

Jul 20 12:33:00 Fanta ntpd[1668]: 192.168.192.34 on 1 br0 -> *multiple*

 

@JorgeBdo you have "Host access to custom networks" turned off?

 

I am turning this setting off again and rebooting the server to see if it is the root cause

1 hour ago, thecode said:

@JorgeBdo you have "Host access to custom networks" turned off?

I do, let me see if I can reproduce with this enabled.

 

It was already enabled after all, but I do now see the same spam, so it's probably that.

1 hour ago, thecode said:

"Host access to custom networks"

It does look like this it the issue, can you confirm?

I do have host access enabled as well.

27 minutes ago, JorgeB said:

It does look like this it the issue, can you confirm?

I can confirm, tested twice, even without reboot.

 

Host access to custom networks enabled = "on 1 br0 -> *multiple*" by ntpd

Host access to custom networks disabled = not logged

3 minutes ago, thecode said:

I can confirm, tested twice, even without reboot

Thanks, I also see the same, I'll report it to LT.