I had the same problem yesterday. My HA server ran out of space. I tracked the problem to extremely large logfiles (5+ gb); the home-assistant.log, the syslog.log and the daemon.log. The HA debug events were being recorded in the above files. I never had the issue before and haven’t tracked down the cause yet. As a temporary measure I changed my HA configuration.yaml…
logger:
…default: warn (ignore the periods, showing indents)
to keep the logs from growing to several gigabytes.
I will try to find the cause when I get some time.
Also, there were a couple of very large rotated log files, I just removed them. Don’t delete the active log files, but you can zero them out or truncate them, just google to find the proper procedure.
I use webmin on my linux servers. Makes it easy to manage the server.
You can ssh in and use the terminal commands to work with the files also…
Looks like you can already do this. Check /var/log for syslog, daemon logs & your home assistant directory for the home-assistant logs.
it seems i cant get into the docker instance due to space issues docker doesnt start and i wasnt sure how to get to /var/log in the HASSIO from outside of the container not that familiar with docker / containerization
I could be wrong, but I believe the .db file is for the HA recorder database, not a log file. Although that could be a problem too if it is bloated. That can be corrected by turning off history recording for components you don’t need to have history info for. I always check the history after installing new sensors to make sure they are not recording if I don’t need the history.
Seems to me the system log files should be in the standard locations, /var/log.