Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If InfluxDB has a full disk, plugin writes hundreds of MB of log files to octoprint.log per day #23

Closed
ventilator opened this issue May 1, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@ventilator
Copy link

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:
image

image

@agrif
Copy link
Owner

agrif commented May 6, 2021

wohba, yeah that's not good. This should be easy, and it's sort of important, so I'll try to do this fast.

@agrif agrif added the bug Something isn't working label May 6, 2021
@agrif agrif closed this as completed in c74d40c Aug 18, 2023
@agrif
Copy link
Owner

agrif commented Aug 18, 2023

"Fast" I said.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants