WARNING: mjpg client connection for camera 3 on port 8083 is closed #2296

Open
opened 2026-02-28 01:09:12 -05:00 by deekerman · 3 comments
Owner

Originally created by @pickonedev on GitHub (Sep 25, 2022).

Hi!

When I add the 3rd camera (does not care what kind of camera), I get multiple errors with this line "WARNING: mjpg client connection for camera 3 on port 8083 is closed". Any idea what can I do to solve this?
The camera feed it is not shown.

Edit: I saw one error for camera 1 as well, but the camera feed seems to work " WARNING: mjpg client connection for camera 1 on port 8081 is closed"

Edit2: I tried to change the Streaming port and still not working ( ERROR: mjpg client timed out receiving data for camera 3 on port 9003 "

If I add the 4th camera, the 4th camera it is working, but 3rd no chance...

Edit3: And I see this error very often "/bin/sh: lsb_release: not found", it if helps...

Thank you!

Originally created by @pickonedev on GitHub (Sep 25, 2022). Hi! When I add the 3rd camera (does not care what kind of camera), I get multiple errors with this line "`WARNING: mjpg client connection for camera 3 on port 8083 is closed`". Any idea what can I do to solve this? The camera feed it is not shown. Edit: I saw one error for camera 1 as well, but the camera feed seems to work " `WARNING: mjpg client connection for camera 1 on port 8081 is closed`" Edit2: I tried to change the Streaming port and still not working ( `ERROR: mjpg client timed out receiving data for camera 3 on port 9003` " If I add the 4th camera, the 4th camera it is working, but 3rd no chance... Edit3: And I see this error very often "`/bin/sh: lsb_release: not found`", it if helps... Thank you!
Author
Owner

@MichaIng commented on GitHub (Sep 25, 2022):

The lsb_release error is not related and can be ignored, but also solved by installing the lsb-release package, e.g. on Debian/Ubuntu:

apt install lsb-release

Which OS do you use, and which motionEye version? If 0.42.1, please try to use the new Python 3 based dev version, which has quite a bunch of bugs solved: https://github.com/motioneye-project/motioneye/tree/dev#installation

@MichaIng commented on GitHub (Sep 25, 2022): The `lsb_release` error is not related and can be ignored, but also solved by installing the `lsb-release` package, e.g. on Debian/Ubuntu: ```sh apt install lsb-release ``` Which OS do you use, and which motionEye version? If 0.42.1, please try to use the new Python 3 based dev version, which has quite a bunch of bugs solved: https://github.com/motioneye-project/motioneye/tree/dev#installation
Author
Owner

@pickonedev commented on GitHub (Sep 25, 2022):

I am using:

Home Assistant 2022.9.6
Operating System 9.0

With MotionEye Add-On 0.18.0

@pickonedev commented on GitHub (Sep 25, 2022): I am using: Home Assistant 2022.9.6 Operating System 9.0 With MotionEye Add-On 0.18.0
Author
Owner

@MichaIng commented on GitHub (Sep 25, 2022):

Ah okay, I have no experience or insights into the Home Assistant OS, but it uses the older motionEye for sure. We really need to get v0.43.0 released, so distros and other appliance developers can update theirs 🤔.

@MichaIng commented on GitHub (Sep 25, 2022): Ah okay, I have no experience or insights into the Home Assistant OS, but it uses the older motionEye for sure. We really need to get v0.43.0 released, so distros and other appliance developers can update theirs 🤔.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/motioneye#2296
No description provided.