I have no idea why this was triggered, but it looks like that vnstat is not updating on some systems any more since around October time. It is looking for a backup database of "tag" which is not an interface and fails to open the "tag" database which simply is an empty file. Removing that file has fixed the graph on various systems. Could we please remove /var/log/vnstat/tag on all systems that have it with the next update? I do not think that it is necessary to delete this file at every boot.
Being curious, I did a quick research. Creating this file was triggered here (2019-05-21): https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;f=lfs/vnstat;h=b0d31edbd6268e32fe7ab7649c581d20686e8ced Reasons? Would reverting this commit be sufficient?
Yes, that commit needs to be reverted at least. We will have to ship the directory in the root file. We should also consider updating vnstat because there are some new release available. Would you work on this, so we can ship this in Core Update 143?
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5562f26f6979c2d60202eafe32469989c0878f20
https://blog.ipfire.org/post/ipfire-2-25-core-update-143-is-available-for-testing
Update to 2.6, introducing the new 'vnstad'-daemon. Is running here since a few weeks - right now on Core 142. Patchwork: Patch 1/4 => https://patchwork.ipfire.org/patch/2926/ Patch 2/4 => https://patchwork.ipfire.org/patch/2923/ Patch 3/4 => https://patchwork.ipfire.org/patch/2924/ Patch 4/4 => https://patchwork.ipfire.org/patch/2925/ GIT: https://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=shortlog;h=refs/heads/vnstat
I am setting this back to MODIFIED as the vnstat 2.6 patches just made it into next and will most likely be shipped with Core Update 145.
https://blog.ipfire.org/post/ipfire-2-25-core-update-145-is-available-for-testing
https://blog.ipfire.org/post/ipfire-2-25-core-update-145-released