2.12: `AlwaysAddNewInterfaces 1` sometimes doesn't work

[opty77]

I use vnstat 2.12 on TP-Link TL-WDR3600 v1.2 running OpenWrt 24.10.1 with AlwaysAddNewInterfaces 1 in /etc/vnstat.conf but it sometimes doesn't work, today's boot:

2025-05-08T15:13:33.674299+02:00 tplink vnstatd 1862 - - No interfaces found in database, adding available interfaces...
2025-05-08T15:13:33.674381+02:00 tplink vnstatd 1862 - - Interface "eth0" added with 1000 Mbit bandwidth limit.
2025-05-08T15:13:33.674436+02:00 tplink vnstatd 1862 - - -> 1 new interface found.
2025-05-08T15:13:33.674491+02:00 tplink vnstatd 1862 - - Limits can be modified using the configuration file. See "man vnstat.conf".
2025-05-08T15:13:33.674547+02:00 tplink vnstatd 1862 - - Unwanted interfaces can be removed from monitoring with "vnstat --remove".
2025-05-08T15:13:33.824314+02:00 tplink vnstatd 1862 - - Info: vnStat daemon 2.12 (pid:1862 uid:0 gid:0 64-bit, SQLite 3.46.1)
2025-05-08T15:13:33.864256+02:00 tplink vnstatd 1862 - - Info: Data retention: 48 5MinuteHours, 4 HourlyDays, 62 DailyDays, 25 MonthlyMonths, -1 YearlyYears, 20 TopDayEntries
2025-05-08T15:13:33.864339+02:00 tplink vnstatd 1862 - - Info: Monitoring (1): eth0 (1000 Mbit)
[...]
2025-05-08T15:13:40.900995+02:00 tplink vnstatd 1862 - - Interface "br-lan" added with 1000 Mbit bandwidth limit.
2025-05-08T15:13:40.931323+02:00 tplink vnstatd 1862 - - Interface "eth0.1" added with 1000 Mbit bandwidth limit.
2025-05-08T15:13:40.941794+02:00 tplink vnstatd 1862 - - Interface "eth0.2" added with 1000 Mbit bandwidth limit.
2025-05-08T15:13:40.986082+02:00 tplink vnstatd 1862 - - Info: Monitoring (4): eth0.2 (1000 Mbit) eth0.1 (1000 Mbit) br-lan (1000 Mbit) eth0 (1000 Mbit)
[...]
2025-05-08T15:13:49.224151+02:00 tplink hostapd - - - phy1-ap0: AP-ENABLED
[...]
2025-05-08T15:15:06.714488+02:00 tplink chronyd 1182 - - Selected source 162.159.200.123 (cz.pool.ntp.org)
2025-05-08T15:15:06.715019+02:00 tplink chronyd 1182 - - System clock wrong by 654001.493305 seconds
2025-05-16T04:55:08.208628+02:00 tplink chronyd 1182 - - System clock was stepped by 654001.493305 seconds
[...]
2025-05-16T12:39:59.910063+02:00 tplink vnstatd 1862 - - Info: SIGTERM received, exiting.
2025-05-16T12:40:00.417901+02:00 tplink vnstatd 3084 - - Info: vnStat daemon 2.12 (pid:3084 uid:0 gid:0 64-bit, SQLite 3.46.1)
2025-05-16T12:40:00.427738+02:00 tplink vnstatd 3084 - - Info: Data retention: 48 5MinuteHours, 4 HourlyDays, 62 DailyDays, 25 MonthlyMonths, -1 YearlyYears, 20 TopDayEntries
2025-05-16T12:40:00.437581+02:00 tplink vnstatd 3084 - - Info: Monitoring (5): phy1-ap0 (1000 Mbit) eth0.2 (1000 Mbit) eth0.1 (1000 Mbit) eth0 (1000 Mbit) br-lan (1000 Mbit)

vnstatd didn't add phy1-ap0 automatically, I had to restart the daemon.

[vergoh]

Was something else also done in addition to just restarting the daemon? I don't see Interface "phy1-ap0" added in that log which should have become visible if the daemon added the interface after (or before) restart.

[opty77]

No and that missing message puzzled me too.

It worked on another device which uses DSA, could it make a difference?