You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should consider /data/dbus-*/current.log. A simple rm might not work due to the file size, I like to use cat /dev/null > current.log for such cases.
mansr
added a commit
to victronenergy/meta-victronenergy
that referenced
this issue
Aug 8, 2024
Several third-party add-ons create ever-growing log files. To prevent
the data partition filling up, truncate any such files larger than
1 MB on startup.
victronenergy/venus#1284
Recently, I've had various systems that were stuck because the data partition is full.
Reason was 3rd party plugins.
this issue is about deleting the most common of them early at boot.
also, I'm in touch with a few of the maintainers to get them to change their ways, see here for the most detailed one: henne49/dbus-opendtu#173.
And we have an issue for Venus OS to add showing a warning when the disk of the GX is (getting) full.
But aside from that, and probably much less work, perhaps we should just at boot, before those services start, delete certain files if they exist.
This issue is to keep a list while I'm getting in touch with those projects.
/data/dbus-opendtu/current.log
, they solved it for new releases, including deleting the file when user re-runs their install script. issue/data/dbus-shelly-em-smartmeter/current.log
, root cause discussion started today commnity/data/dbus-shelly-3em-smartmeter/current.log
, root cause not fixed yet issue/data/dbus-shelly-1pm-pvinverter/current.log
, discussion: current.log is getting too big vikt0rm/dbus-shelly-1pm-pvinverter#4The text was updated successfully, but these errors were encountered: