-
Notifications
You must be signed in to change notification settings - Fork 84
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
Deal with issues when the disk is full #2328
Comments
I know it might be trickier to manage the installation, but another valid strategy is to put |
I installed one extension [Nortek Nucleus], that grew the docker log to 18GB in about a week, maybe kraken could add a limit in the size of the docker logs: https://docs.docker.com/config/containers/logging/configure/#configure-the-default-logging-driver
|
I've just freed ~12 gb here by doing: sudo docker system prune -a # ~9 gb
sudo journalctl --vacuum-time=2d # ~1 gb
sudo apt-get clean # ~1 gb |
@joaoantoniocardoso how we end up with 1GB of unnecessary stuff in our apt ? |
The docker prune is specially important, as there are A LOT of leftover overlays hanging there forever. |
Maybe I've installed many things on mine, but it'd be good to check how it is in a fresh install. |
We are discussing this subject a bit in our project, as we run robots 24/7, and they could be running for several days, maybe even weeks without restarting/power cycling. I've not done very thorough digging, but I think it would be very nice to have some kind of parameter (maybe even user facing), that would permit you to set a target age for tlog files. If I set 7 days, then any tlog files older than 7 days would be auto purged (no sure how often that should run). Maybe a bit out of scope for this issue, but should help nonetheless. I can make a separate issue if that is better. EDIT: |
Hi @goasChris, thanks for your input. Indeed the tlogs are also important for us to track. Adding on it, the tlogs are already in the list. Let us know if you have anything that is not being tracked at the moment. |
About tlogs: mavlink-router/mavlink-router#426 |
Some things that take a lot of space and can be removed:
|
Check: #2327, #2323, #2326, #1015
The docker is able to start, but everything after that just results in unstable behavior.
Some points that you suggested are already available as issues, others are relevant to recover the system.
Originally posted by @patrickelectric in #2325 (comment)
The text was updated successfully, but these errors were encountered: