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
{{ message }}
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
I acted before I could look at the 4.3gb log file, so I cannot tell you what was in it - but it caused my Octoprint instance to be unable to start up due to an out of space error on the filesystem. Perhaps someone trying to scan the wifi AP?
I didn't see any options to disable logging, or redirect logging to /dev/null, or delete old log files. But the pi has been up since OctoPrint 1.2.4 without a reboot. It just so happens that I rebooted because of a network issue and ran across this.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I acted before I could look at the 4.3gb log file, so I cannot tell you what was in it - but it caused my Octoprint instance to be unable to start up due to an out of space error on the filesystem. Perhaps someone trying to scan the wifi AP?
I didn't see any options to disable logging, or redirect logging to /dev/null, or delete old log files. But the pi has been up since OctoPrint 1.2.4 without a reboot. It just so happens that I rebooted because of a network issue and ran across this.
The text was updated successfully, but these errors were encountered: