I have a strange issue, I need to find the cause of.
My HA setup (pyton virt env) on RPi2 have been running for some months. But suddenly it stops about every second day. The Pi are responding to SSH, and I can reboot it to get everything up and running again. But I need to find a solution.
I have checked home-assistant.log, it contains just 3 entries of warnings:
2018-09-26 03:08:29 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=2 from 2018-09-24 00:17:18.547353)
2018-09-26 08:25:21 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 19002 seconds, continuing anyway
2018-09-26 23:06:25 WARNING (MainThread) [asyncio] socket.send() raised exception.
Is there another place to look?..
I have configured it to start up with:
when it fails, to see the exit code, but I expect, judging from the last message in the log, that it is a component not handling an error case correctly.
You might get more information if you increased the logging level in the logger component
SEGV is a memory access violation, but searching reported errors for something like this reveals this issue, which seems to have been fixed by replacing the SD card, so I think that should be your next step. https://github.com/home-assistant/home-assistant/issues/8079
pi@automator:~ $ systemctl status [email protected]
â—Ź [email protected] - Home Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Sun 2018-10-14 06:49:04 CEST; 10h ago
Process: 5463 ExecStart=/srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant (code=killed, signal=SEGV)
Main PID: 5463 (code=killed, signal=SEGV)
Oct 14 06:48:18 automator hass[5463]: File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_response.py", line 367, in _start
Oct 14 06:48:18 automator hass[5463]: await writer.write_headers(status_line, headers)
Oct 14 06:48:18 automator hass[5463]: File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/http_writer.py", line 110, in write_headers
Oct 14 06:48:18 automator hass[5463]: self._write(buf)
Oct 14 06:48:18 automator hass[5463]: File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/http_writer.py", line 67, in _write
Oct 14 06:48:18 automator hass[5463]: raise ConnectionResetError('Cannot write to closing transport')
Oct 14 06:48:18 automator hass[5463]: ConnectionResetError: Cannot write to closing transport
Oct 14 06:49:04 automator systemd[1]: [email protected]: Main process exited, code=killed, status=11/SEGV
Oct 14 06:49:04 automator systemd[1]: [email protected]: Unit entered failed state.
Oct 14 06:49:04 automator systemd[1]: [email protected]: Failed with result 'signal'.
Okay, it is happening again… I have moved to a new SD card.
Same message again.
When I moved, I cloned the card with Win32DiskImage. I did not get any errors during the process, but could I have copied also the corruption?
I have also tried to do some research on mu old SD card, have filled it up several times with data and I have been able to copy it back again without any errors (using H2testw)… So maybe SD card are not the issue.
Any more thoughts?
Also Im still able to SSH and start HA again.
â—Ź [email protected] - Home Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Wed 2018-10-17 22:56:06 CEST; 9min ago
Process: 395 ExecStart=/srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant (code=killed, signal=SEGV)
Main PID: 395 (code=killed, signal=SEGV)
Oct 17 21:53:07 automator hass[395]: 2018-10-17 21:53:07 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ios/identify to 192.168.55.198 (auth:
Oct 17 22:03:05 automator hass[395]: 2018-10-17 22:03:05 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ios/identify to 192.168.55.198 (auth:
Oct 17 22:07:39 automator hass[395]: 2018-10-17 22:07:39 INFO (MainThread) [homeassistant.components.updater] Submitted analytics to Home Assistant servers. Infor
Oct 17 22:07:39 automator hass[395]: 2018-10-17 22:07:39 INFO (MainThread) [homeassistant.components.updater] You are on the latest version (0.80.0) of Home Assis
Oct 17 22:14:33 automator hass[395]: 2018-10-17 22:14:33 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ios/identify to 192.168.55.198 (auth:
Oct 17 22:24:06 automator hass[395]: 2018-10-17 22:24:06 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ios/identify to 192.168.55.198 (auth:
Oct 17 22:31:38 automator hass[395]: 2018-10-17 22:31:38 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ios/identify to 192.168.55.198 (auth:
Oct 17 22:56:06 automator systemd[1]: [email protected]: Main process exited, code=killed, status=11/SEGV
Oct 17 22:56:06 automator systemd[1]: [email protected]: Unit entered failed state.
Oct 17 22:56:06 automator systemd[1]: [email protected]: Failed with result 'signal'.
