Is this normal? "home-assistant.log.fault" and "home-assistant.log.1" created after each bootup

1

Every single time my Home Assistant VM boots up, a zero byte “home-assistant.log.fault” and “home-assistant.log.1” and "“home-assistant.log” are immediately created. This even happens even after building a brand new clean install. If I restart Home Assistant Core, after Core restarts, home-assistant.log.1 has nothing in it with zero bytes.

If I restart Home Assistant Host, the home-assistant.log.1 has only the below startup components listed, which is usually the same thing I see in the normal home-assistant.log:

Is this normal, if not, how do I fix this?

home-assistant.log.1

2023-08-27 15:20:53.209 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:20:53.210 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration roblox which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:20:53.211 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration sonarr_upcoming_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:20:53.212 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration plex_recently_added which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:20:53.212 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:21:03.673 WARNING (MainThread) [homeassistant.config_entries] Config entry '[email protected]' for litterrobot integration not ready yet: Unable to connect to Litter-Robot API; Retrying in background

home-assistant.log

2023-08-27 15:28:04.728 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:28:04.730 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration roblox which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:28:04.731 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration sonarr_upcoming_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:28:04.732 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration plex_recently_added which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:28:04.733 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-27 15:28:14.886 WARNING (MainThread) [homeassistant.config_entries] Config entry '[email protected] ' for litterrobot integration not ready yet: Unable to connect to Litter-Robot API; Retrying in background
2023-08-27 15:29:00.858 ERROR (Thread-6) [pychromecast.socket_client] [Living Room speaker(192.168.1.148):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Nest-Mini-4f239ed534738cdff77cb602a08e1e78._googlecast._tcp.local.'), retrying in 5.0s
2

I can’t tell you if it’s normal for the fault log to be created every time (tho I expect that it is normal too) I can tell you that the “log.1” log will always be created.

It contains the data of your .log file at the time that HA is restarted.

It was added so that users who restarted HA due to an error didn’t lose the data contained in the “.log” file as it’s cleared out on every restart.

3

Thanks for the quick reply back. I just installed a virgin brand-new VM image with Home Assistant OS 10.5. The ONLY configuration change I did was create my user account during onboarding and give the Instance a name. I also installed the Samba Add-on in order to access the /config directory to access the log files.

After each HA Core restart, I see a home-assistant.log.fault file created when the home-assistant.log.1 is created.

The name home-assistant.log.fault implies to me that it was created after an HA Core crash.

4

Just checked, seems I have a home-assistant.log.fault too. I would not worry about it.

5

Thanks for the heads up. The thing that botters me is that the word “fault” suggests something didn’t go as expected. If the file has no purpose, it would be better just not to include it.