When I shutdown or restart home-assistant, it seems to be failing to terminate correctly. Does anybody know why this might be?
I’m running on a raspberry pi 3, on raspian, with a Z-stick 5 connected to two other z-wave components. Other major components are Chromecasts on WiFi, an MQTT link to owntracks, and then pi-hole, transmission, uber, and snmp modules loaded.
Dec 30 15:27:44 raspberrypi systemd[1]: Stopping Home Assistant...
Dec 30 15:27:44 raspberrypi hass[746]: INFO:homeassistant.core:Bus:Handling <Event homeassistant_stop[L]>
Dec 30 15:27:44 raspberrypi hass[746]: INFO:homeassistant.components.zwave:Stopping ZWave network.
Dec 30 15:27:44 raspberrypi hass[746]: INFO:openzwave:Stop Openzwave network.
Dec 30 15:27:44 raspberrypi hass[746]: INFO:openzwave:ZWave configuration written to user directory.
Dec 30 15:27:49 raspberrypi hass[746]: Config directory: /home/homeassistant/.homeassistant
Dec 30 15:28:11 raspberrypi hass[746]: INFO:netdisco.service:Scanning
Dec 30 15:29:14 raspberrypi systemd[1]: [email protected] stop-sigterm timed out. Killing.
Dec 30 15:29:14 raspberrypi systemd[1]: [email protected]: main process exited, code=killed, status=9/KILL
Dec 30 15:29:14 raspberrypi systemd[1]: Stopped Home Assistant.
Dec 30 15:29:14 raspberrypi systemd[1]: Unit [email protected] entered failed state.
The last few messages are systemd coming in and killing the process after a couple of minutes.
That looks very similar to what I’m getting. Certainly the second ^C gives the same trace-back. Prior to that it looks very much like the log file I gave in the original post.
Edit: I’m not at home at the moment, and I don’t want to remotely shut things down. When I’m back home I can capture a log if it’s useful.
I too seem to be having log restart/shutdown times due to Netdisco service still running after the restart service has been called (doing scans every 5 minutes). Doing a service restart via init.d also shows the same behaviour. Log below: