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
my InfluxDB refused to accept new data (which is my fault and ignored for a couple of days), and then octoprint complaints about no disk space left. As it turn out, the error logging kind of stuffed my octoprint installation.
A suggestion: Maybe just log once a day the error instead every second or so, resulting in millions of lines of log file:
The text was updated successfully, but these errors were encountered:
I've changed the code to only output the full exception when it changes, and then added some exponential backoff to the reconnection. Now it'll try after 1 second, then 2, then so on, although it'll never wait longer than 10 minutes. This should shave a few orders of magnitude off those log sizes, at least.
This change is in version 1.4.0, which is now available.
Hi,
my InfluxDB refused to accept new data (which is my fault and ignored for a couple of days), and then octoprint complaints about no disk space left. As it turn out, the error logging kind of stuffed my octoprint installation.
A suggestion: Maybe just log once a day the error instead every second or so, resulting in millions of lines of log file:
The text was updated successfully, but these errors were encountered: