mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
WARNING: Connect error on fd 16: ECONNREFUS causing many false alarms #710
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#710
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @homesmarty on GitHub (Jan 6, 2018).
I am struggling to get motion detection to work and suspect it's a technical problem... I see a lot of warnings in the motioneye.log:
WARNING: Connect error on fd 16: ECONNREFUS
They come in groups (~5-30) and always coincide with false alarms of motion detecion (video recorded, but nothing moving).
What does this warning mean? How can I dive deeper to fix the issue?
I get dozens of recordings of nothing, but when I walk though the picture, nothing is recorded :(
I'd love to use motionEye as a NVR (Wansview W2 ZIP camera, might get more of those), it's much slicker than Synology Disk station ;-) But right now, I can't get it to do the job at all...
Versions I use:
motionEye Version | 0.37.1
Motion Version | 4.0.1+git2a140fa
OS Version | motionEyeOS 20171008
On a RasPi3
PS: This might or might not be a motionEye issue, but I need help - is there a forum where I could seek help?
Edit: I am storing the videos in the default path on the microSD, didn't change the storage options.
Edit2: Is this Warning about camera connectivity (as I assume above), or maybe about writing the movie file? I saw some other issues indicating it might be the latter. As said in 1st edit, I use the microSD card (default path) to store the files. It's a class 10 Samsung and I reduced the video rate to ~1.5Mbps.
BTW: There is nothing in the motion.log except messages at boot time.
@Zortris commented on GitHub (Mar 31, 2018):
Same issue here
motion.log
motioneye.log
@Zortris commented on GitHub (Apr 27, 2018):
Push