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 (3,533 stars) (636 forks)batch import
help wantedquestiontroubleshooting

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

Tech stack
pythonshell
Domain
backenddevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic systemd knowledgenetwork dependencies
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The issue is about motioneye failing to start after reboot due to network not being ready. The fix involves modifying the systemd unit file at /etc/systemd/system/motioneye.service to add 'After=network online.target' and possibly 'Wants=network online.target'. The developer should also ensure that motioneye retries the mjpg connection on network failure. No linked PRs or assignees; the issue is from 2021 and has 2 comments.