motioneye-project/motioneye

motioneye service fails to start properly after reboot with mjpg on raspbian buster

Open

#2,183 opened on Sep 2, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (636 forks)batch import
help wantedquestiontroubleshooting

Repository metrics

Stars
 (3,533 stars)
PR merge metrics
 (Avg merge 16d 14h) (33 merged PRs in 30d)

Description

Hi,

I'm using motioneye on a rasbian pi4 as a frontend for motioneyeos pi zero cameras on fast camera mode.

Using systemd service file provided in the doc, when rebooting the main raspberry I have: "ERROR: mjpg client timed out receiving data for camera 1 on port 8081" and no videos.

Works fine after a manual ssh "systemctl restart motioneye"

After searching, for /usr/local/share/motioneye/extra/motioneye.systemd-unit-local and then /etc/systemd/system/motioneye.service : [Unit] needs: After=network-online.target

[Install] would probably need: After=network-online.target

Strange mjpg is not retrying properly when network fails or not ready...

Contributor guide

Research direction
Examine the systemd unit file and add `After=network online.target` to ensure network is ready before starting motioneye. Also investigate mjpg retry logic to handle network failures gracefully.
Tech stack
python
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
systemdLinux
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60