[SOLVED] ifupdown2 looping every ~10 seconds

[BobC]

Proxmox v8.4.17

It appears ifupdown2 has been running every ~10 seconds in debug mode and writing to /var/log/ifupdown2. Granted only 43 logs are kept at a time, but the sequence number in the file name is well over 6.5 million... meaning at every 10 seconds (give or take), that's over 2 years of constant writes.

See attached for a "current" example.

I have read (some of) the logs and from what I can tell, it doesn't seem to justify that frequency. (or does it? - see below)

In /etc/network/ifupdown2/ifupdown2.conf, I was able to set enable_persistent_debug_logging=no to stop the logging.

But that doesn't mean the process has stopped running that frequently.

I have had no networking problems and the only real change made is I recently removed OVS, but only because I was not using it.

I just checked a newer Proxmox 9.1.6 box and the enable_persistent_debug_logging variable seems to default to yes out of the box. Questions please:

- Are there any repercussions to disabling debug logging like this?
- Is the frequency seen considered expected "behavior"? If so, it seems..... "excessive".
- Assuming it is ifupdown2 (or ifreload, ifquery, etc) can I stop it from running at this frequency?
- Am I missing something in the attached debug log that would cause ifupdown2 to run like this?
- If not, would this be a "bug" ?

I did see one reference to link_master_slave variable in this post, I do see that in my logs, but am unsure if it's relevant.

Any help or pointers would be appreciated.

Thanks,
Bob

 

[shanreich]

pvestatd uses ifquery to check for the status of network interfaces - which is ran approximately every ~10 seconds. You can turn off logging via the variable, but that would also include any other run of ifupdown2 CLI tools. We already have a tracking issue on Bugzilla for this [1].

[1] https://bugzilla.proxmox.com/show_bug.cgi?id=5242

 

[BobC]

Yup, that seems to be it... just subscribed to the bug.

Thank you @shanreich!