motioneye-project/motioneye

Network Failed Panic Rebooting

Open

#2,202 opened on Oct 9, 2021

View on GitHub
 (11 comments) (0 reactions) (0 assignees)Python (3,533 stars) (636 forks)batch import
help wantedmotionEyeOSquestiontroubleshooting

Description

Good day,

I have a Raspberry PI 4B 8G with a DSLR KIT Power Over Ethernet PoE HAT IEEE802.3af DC 5V 2.5A with 1.5KV Isolation for Raspberry Pi 4B 3B+ 3B Plus

If I try and boot MotionEye using POE I get the error "Network Failed Panic Rebooting", I have tried with DHCP and Static.

If I boot without POE I don't get the error.

Raspbian boots ok from POE so not certain what the issue is.

Contributor guide

Tech stack
pythonshell
Domain
devopsbackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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.
needs investigation
Prerequisites
Raspberry Pi 4B with PoE HATMotionEye installationbasic Linux command line
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The issue reports a network panic during boot when using PoE on a Raspberry Pi 4B. The root cause may be related to MotionEye's network initialization scripts, possibly in /etc/init.d/motioneye or systemd service files. Investigate differences in boot sequence between PoE and non PoE power, and check if the panic is caused by a timeout or missing interface. Review comments #2202 for any follow up diagnostics.
Network Failed Panic Rebooting · motioneye-project/motioneye#2202 | Good First Issue