I am fighting through the setup of hass.io running in docker on a linux system and am frustrated with finding the logs. Is there a standard list of locations on where the logs can be found or even better a place where they are sourced from and could be redirected to a standard location? I know in the Gui each addon has a log and it appears there are two locations for the system logs but those are unmanageable to view while actively troubleshooting so I am pulling them from the CLI. These are the locations I am viewing, any additional locations you can provide could be helpful for me to find the errors related to the problems I am having.
I am not troubleshooting a specific problem with this question and I really appreciate your response. This was prompted because, while I cannot claim to know what I am doing, I have been able to make a lot of progress by searching the logs for clues when a problem is triggered. What I find though is the log messages do not always show up in the log I expect them to so I am trying to gather a full list of where they may occur. Using your method of tail direct from Docker looks very promising as I can just use ādocker container lsā to see each container and then tail each container in a console session for a complete live feed.
Hello, Iām digging up this old thread because it deals precisely with what Iām currently after. I hope this is not a big of a problem.
Iām experiencing random problems currently and my guessing it that they are hw related. Could you help me figure out where the host will store the logs? Iāve logged into port 22222 over ssh and I donāt see any relevant file in /var/log. I suspect that is not the right place to check. Thank you so much!
Not true. That is only the Home Assistant core log. There is (when running Home Assistant OS, which is where this question is being asked!), among few, at least:
Supervisor logs
Host logs
DNS logs
Audio logs
Multicast logs
They are logging around 500mb/day and is NOT configured by the āloggerā integration and is NOT the same as the homeassistant log and is NOT in the config folder. Likewise; their logging level is NOT affected by the log level set in the"logger" integration. Also, they are not rotated, so they are filling upp the SD card with need for manual deletion.
Clarifications of where those logs are located, and how to manage then, is nowhere to be seen in the docs however.
Yes, they are. I agree. But for someone that isnāt a linux/unix/whatever expert, and therefore prefer a supervised standard installation that is 100% managed, running on Home Assistant OS rather than fiddling with a standard OS, docker containers, crontabs, log rotations and what not, simply wants the thing working with reasonable defaults.
Someone like that does not want home assistant to spam those logs with 500mb+/day, without limits and without automated log rotation. My SD card looses 500mb/day -ish due to these logs. And it also causes premature wear of the SD card.
Even if those are standard journald logs, the output that is in fact logged comes from Home Assistant 99.9% of the cases. If running on a completely managed install on a Home Assistant OS, I think they should either have reasonable default log rotations, and also not spam the logs with pointless debug messages. At least make us able to select the log level of those logs in the GUI, without having to install addons for terminal access and then do terminal commands that also tend not to work as Home Assistant OS appears to have removed almost all possible standard linux commands (e.g. neither journalctl or its config file is accessible via the provided terminal addon, so I cannot do any changes to them).