hassio-addons / addon-motioneye

motionEye - Home Assistant Community Add-ons
https://addons.community
MIT License
267 stars 43 forks source link

unable to start Motion eye addon after HA OS Upgrade 9.4 #379

Closed HSMarzio closed 1 year ago

HSMarzio commented 1 year ago

when i try to start addon....nothing (apparently happens). i see a red light on top-right corner inside motion eye addon page....why ?

Motioneye_error

looking to the log, instead, everything seems to be good:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-banner.sh: executing...

Add-on: motionEye Simple, elegant and feature-rich CCTV/NVR for your cameras

Add-on version: 0.18.0 You are running the latest version of this add-on. System: Home Assistant OS 9.4 (armv7 / raspberrypi4) Home Assistant Core: 2021.12.2 Home Assistant Supervisor: 2022.11.2

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0. [cont-init.d] 01-log-level.sh: executing... Log level is set to DEBUG [cont-init.d] 01-log-level.sh: exited 0. [cont-init.d] motioneye.sh: executing... [12:12:05] DEBUG: Running startup migrations backing up /data/motioneye/motioneye.conf [cont-init.d] motioneye.sh: exited 0. [cont-init.d] nginx.sh: executing... [cont-init.d] nginx.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [12:12:06] INFO: Starting motionEye... INFO: hello! this is motionEye server 0.42.1 DEBUG: using motion version 4.3.2 DEBUG: using ffmpeg version 4.4.1 DEBUG: reading main config from file /data/motioneye/motion.conf... DEBUG: loading additional config structure for main, without separators DEBUG: additional config section: network DEBUG: listing config dir /data/motioneye... DEBUG: listing smb mounts... INFO: cleanup started INFO: wsswitch started INFO: tasks started INFO: mjpg client garbage collector started INFO: smb mounts started INFO: server started [12:12:08] DEBUG: Requested API resource: http://supervisor/discovery [12:12:08] DEBUG: Request method: POST [12:12:08] DEBUG: Request data: {"service":"motioneye","config":{"url":"http://127.0.0.1:28765"}} [12:12:08] DEBUG: API HTTP Response code: 200 [12:12:08] DEBUG: API Response: {"result": "ok", "data": {"uuid": "243aff51f7b74688837e2140d1c028c3"}} [12:12:08] DEBUG: Filtering response using: .uuid [12:12:09] INFO: Starting NGinx... [12:12:09] INFO: Successfully send discovery information to Home Assistant. DEBUG: running cleanup process... DEBUG: cleaning up pictures... DEBUG: cleaning up movies... DEBUG: cleanup done DEBUG: checking SMB mounts... DEBUG: listing smb mounts... DEBUG: checking SMB mounts...

frenck commented 1 year ago

Hi there @HSMarzio πŸ‘‹

This is, unfortunately, an issue with the Home Assistant Supervisor. Sometimes, it loses track of the state of the add-on and reports the add-on not running (while it is).

The workaround for this is rebooting your system. From an add-on perspective, there is unfortunately not much I can do. If the problem persists, please report it to the Home Assistant Supervisor project.

Thanks πŸ‘

../Frenck