KopiaUI: CLI logs using 250+ GBs?! #1561
Comments
|
Yeah, this is embarrasing - kopia will currently sweep logs on exit and since server never exists they keep lingering on. I'll prioritize fixing that. |
|
I'm just glad you've a clear idea of the cause. |
jkowalski
added a commit
to jkowalski/kopia
that referenced
this issue
Dec 3, 2021
With this change logs will be rotated every 50 MB, which prevents accumulation of giant files while server is running. This change will also guarantee that log sweep completes at least once before each invocation of Kopia finishes. Previously it was a goroutine that was not monitored for completion. Flags can be used to override default behaviors: * `--max-log-file-segment-size` * `--no-wait-for-log-sweep` - disables waiting for full log sweep Fixes kopia#1561
jkowalski
added a commit
that referenced
this issue
Dec 4, 2021
…1562) * logging: added log rotation and improved predictability of log sweep With this change logs will be rotated every 50 MB, which prevents accumulation of giant files while server is running. This change will also guarantee that log sweep completes at least once before each invocation of Kopia finishes. Previously it was a goroutine that was not monitored for completion. Flags can be used to override default behaviors: * `--max-log-file-segment-size` * `--no-wait-for-log-sweep` - disables waiting for full log sweep Fixes #1561 * logging: added --log-dir-max-total-size-mb flag This limits the total size of all logs in a directory to 1 GB.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
...
..?
.!?
No but seriously, what's going on?!
This is absolutely insane.
Anyway, worth to note is that I'd a sudden shutdown cause I was seemingly overloading my newly acquired UPS in the last few days - however - I only noticed kopia using all of that storage space just now, so I'm not definitely saying that there's a correlation, just think it's worth noting in case there could be a correlation.
Tell me what data you need to troubleshoot this.
EDIT: Just noticed the date for the logs... the kernel power event happened on the 30th of november, so there really shouldn't be a correlation, which makes it even weirder.
Something else to note is that I only use my Windows PC with sleep during the night etc., no clean boot till there's an update that requires it.
The text was updated successfully, but these errors were encountered: