Add-on won't start
roelvdwater opened this issue · comments
Problem/Motivation
I have installed this add-on yesterday along with the motionEye integration so that I can view the USB attached from Home Assistant. This was working fine until I noticed this morning that the camera viewer freezes the whole browser tab when opening the live stream. As I wasn't sure if it was related to Home Assistant, the motionEye integration or the add-on, I checked the Web UI of motionEye and this was working fine. In attempt to fix the live stream, I restarted the add-on, but this resulted in an error. I have tried restarting Home Assistant OS entirely and have re-plugged the USB camera, but the add-on refuses to start.
When starting the add-on, this is what I see in the logs:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: motionEye
Simple, elegant and feature-rich CCTV/NVR for your cameras
-----------------------------------------------------------
Add-on version: 0.20.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.1 (amd64 / generic-x86-64)
Home Assistant Core: 2024.3.1
Home Assistant Supervisor: 2024.03.0
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-motioneye: starting
backing up /data/motioneye/motioneye.conf
s6-rc: info: service init-nginx successfully started
s6-rc: info: service init-motioneye successfully started
s6-rc: info: service motioneye: starting
s6-rc: info: service motioneye successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service discovery: starting
[12:26:59] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:00] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:01] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:01] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:02] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:03] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:04] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:05] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:06] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:06] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:07] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:08] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:09] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:10] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:11] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:11] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:13] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:13] INFO: Service motionEye exited with code 255 (by signal 0)
[12:27:14] INFO: Starting motionEye...
Then, after a number of unsuccessful retries, I see these logs at the very end:
Terminated
[12:27:59] INFO: Starting NGinx...
Terminated
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b1
CRITICAL: pid directory "/run/motioneye" does not exist or is not writable
[12:27:59] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service discovery: stopping
s6-rc: info: service discovery successfully stopped
s6-rc: info: service nginx: stopping
[12:27:59] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service motioneye: stopping
s6-rc: info: service init-nginx successfully stopped
[12:27:59] INFO: Service motionEye exited with code 255 (by signal 0)
s6-rc: info: service motioneye successfully stopped
s6-rc: info: service init-motioneye: stopping
s6-rc: info: service init-motioneye successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
At this point, Home Assistant gives up retrying.
Expected behavior
I would expect the add-on to start successfully.
Actual behavior
The add-on does not start.
Steps to reproduce
I don't think there are any other steps to take other than starting the add-on.
Proposed changes
Not sure about this one.
I would like to add to this that re-installing the add-on “fixed” the problem.
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!