Unable to update beyond the 0.18.0 release - keep having to restore back to that version

[mjc4513]

Problem/Motivation

Any of the recent updates have caused half of my cameras to not display any images or stream. I have a mix of reolink and samsumg cameras using rtsp feeds - they all work in the 0.18.0 release but not the newer ones.

Expected behavior

Not sure what is happening, I have two types of cameras and some of the same camera types work and others do not.

Actual behavior

No image or stream from some cameras

Steps to reproduce

Not sure how to make this happen.

Proposed changes

None

[frenck]

I need either logs and preferably reproduction. There is not much I can do with an report that just state "It doesn't work". Sorry!

../Frenck

[mjc4513]

Totally understand this is the log of the 0.18.0 release - it there are other options to turn on other logging to get more information that you need - please tell me what else is needed

[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
 There is an update available for this add-on!
 Latest add-on version: 0.19.1
 Please consider upgrading as soon as possible.
 System: Home Assistant OS 10.1  (aarch64 / odroid-n2)
 Home Assistant Core: 2023.5.2
 Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
 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... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] motioneye.sh: executing... 
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:13:23] INFO: Starting motionEye...
    INFO: hello! this is motionEye server 0.42.1
Terminated
[12:14:23] INFO: Starting NGinx...
Terminated
[12:14:24] INFO: Successfully send discovery information to Home Assistant.
    INFO: cleanup started
    INFO: wsswitch started
    INFO: tasks started
    INFO: mjpg client garbage collector started
    INFO: smb mounts started
    INFO: server started
/bin/sh: lsb_release: not found

This is the log of the 0.19.1 release - it's getting time outs from cameras where is was not getting them in the 0.18.0 release

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.19.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.1  (aarch64 / odroid-n2)
 Home Assistant Core: 2023.5.2
 Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
 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:50:57] INFO: Starting motionEye...
configure_logging cmd motioneye: False
configure logging to file: None
    INFO: hello! this is motionEye server 0.43.0
    INFO: cleanup started
    INFO: wsswitch started
    INFO: tasks started
    INFO: mjpg customer garbage collector has started
    INFO: smb mounts started
    INFO: server started
[12:51:01] INFO: Starting NGinx...
[12:51:02] 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
   ERROR: mjpg client timed out receiving data for camera 5 on port 8085
   ERROR: mjpg client timed out receiving data for camera 5 on port 8085

[frenck]

The only thing that is slightly odd about the log is:

   ERROR: mjpg client timed out receiving data for camera 5 on port 8085
   ERROR: mjpg client timed out receiving data for camera 5 on port 8085

But, that is just slightly, as it simply reports it isn't receiving data from the camera. There is not much to say about that 🤷

[mjc4513]

Yes, and the one that is has an issue works once I go back to the 0.18.0 release it always displays, but the 0.19.X releases it does not work and gets the time out. No problem on the 0.18.0 release. Not sure of the differences between the two releases. Thanks!

[frenck]

Not sure of the differences between the two releases.

About 3 years worth of upstream development difference (also known as: To huge to comprehend). You could try to take a look at the upstream project issue tracker (of the moitionEye project itself), you might find something similar there.

For me, I have no clue on how to help you further with this (I wish I had an suggestion or idea, but I don't).

[mjc4513]

Guess I will have to change to something else for the cameras or stay on the 0.18.0 release and hope it keeps working...

[github-actions[bot]]

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!