Motioneyeos Webserver,MJPEG server and SSH don't respond after one day, ping still works on Raspberry PI Zero W

Heinzelschelm commented 6 years ago

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue. [x]

I confirm that I have read the FAQ before opening this issue. [x]

motionEyeOS Version

I am running motionEyeOS version: motionEyeOS 20180627

Board Model

I am using the following board/model: Raspberry PI Zero W

Camera

I am using the following type of camera: PICAM NoIR connected via CSI

Network Connection

My motionEyeOS unit is connected to the network via: WIFI

Peripherals

I am using the following peripherals that I consider relevant to this issue:

Nothing except the camera is connected to the PI

Log Files

I consider the following log files relevant to this issue:

boot.log messages.log motion.log motioneye.log dmesg.log

Dear all,

I recently became a little frustrated with my MotionEyeOS installation on my PI Zero W. After approximately 1 day the webinterface and MJPEG Server becomes unresponsive and cannot be reached. SSH also doesn't work anymore, Because I am still able to ping the machine, it doesn't look like a WIFI reception issue. The webinterface didn't respond at 22.09.2018 around 12 o'clock.

I tried around in the configuration enabling connectivity watch and motion keep-alive, but it didn't help. Analyzing the logfiles I couldn't find anything suspicious. As the system is encapsuled, my only chance in case the PI becomes unreachable via SSH is to interrupt the power supply, reboot and check the logfiles then. As you can see in the logfiles, it has happened quite often in the past weeks :-( I also don't think it is related to high CPU load, because when I use top via ssh, there is always ~30% idle.

Does anybody have an idea what it could be?

Thanks and kind regards, Heinzelschelm

ccrisan commented 6 years ago

@Heinzelschelm you're not the only one to report responsiveness issues with motionEye lately. Unfortunately I simply have no idea what could cause them and what would be the best way to identify this problem.

One thing that I keep seeing in users' logs when they experience this issue is timeout when communicating with Motion:

2018-09-21 17:48:56: [motioneye]    ERROR: mjpg client timed out receiving data for camera 1 on port 8081

If you look closely in your motioneye.log, you'll see that whenever you have a hello! that is not preceded by a bye! (i.e. not a clean reboot), you'll always have a similar Motion timeout instead. This leads me to believe that Motion may be the one misbehaving.

One thing you could do is to enable debugging (in Expert Settings) and then you'll get more useful stuff in motion.log.

Dutchs commented 6 years ago

Having very similar symptoms on a rpi3b+ seemingly locking up SSH, webserver and FTP after about a day both with latest release 20180627 and dev20180730 Last time it hang was during a motion event i suspect, due to that clip being corrupted in the progress Here are logs, with MotionEyeOS set with debug logging turned on boot.log dmesg.log messages.log motion.log motioneye.log

xu4user commented 6 years ago

Where are all these log files located? I only see the /var/log/motion.log.

Rubberduck84 commented 6 years ago

I have the same problem with the raspberry pi 3b + i uploaded the images to google drive. This are my logs.

motioneye (4).log boot (6).log motion (4).log messages (4).log dmesg (4).log

Ik hope that anybody fix this problem.

Rubberduck84 commented 6 years ago

Where are all these log files located? I only see the /var/log/motion.log.

under the tap expert settings!

ccrisan commented 6 years ago

@Rubberduck84 I see " user.notice wifi: disconnected" in your log - check your wifi connectivity.

Rubberduck84 commented 6 years ago

Thanks Ccrisan,

I will try it with cable. Thanks for your quick response.

helmar74 commented 5 years ago

Same here. I also get this error message in motioneye.log: 2018-11-27 17:48:56: [motioneye] ERROR: mjpg client timed out receiving data for camera 1 on port 8081

A Few minutes later I got: 2018-11-27 17:50:04: [motioneye] ERROR: motion not running, starting it

After that the message

ERROR: mjpg client timed out receiving data for camera 1 on port 8081

is repeating every 10 seconds.

If I reboot the cam with webinterface, the cam doesn't come up. I have to power down and up, than the cam is working again

Rubberduck84 commented 5 years ago

Same here. I also get this error message in motioneye.log: 2018-11-27 17:48:56: [motioneye] ERROR: mjpg client timed out receiving data for camera 1 on port 8081

A Few minutes later I got: 2018-11-27 17:50:04: [motioneye] ERROR: motion not running, starting it

After that the message
ERROR: mjpg client timed out receiving data for camera 1 on port 8081
is repeating every 10 seconds.

If I reboot the cam with webinterface, the cam doesn't come up. I have to power down and up, than the cam is working again

Try it with a utp cable it works for me.

helmar74 commented 5 years ago

A other cam, which is also connected with wifi doesn't have this issue.

Rubberduck84 commented 5 years ago

A other cam, which is also connected with wifi doesn't have this issue.

Have the wifi connection the same distance?

helmar74 commented 5 years ago

yes, both cams are located in the sam room (garage) only 2 meters distance is between them

Rubberduck84 commented 5 years ago

I mean how far its the distance to your wifi router? And do you use motion detection?

helmar74 commented 5 years ago

The related access point is also in the garage. The cams are connected to the AP

Rubberduck84 commented 5 years ago

Please flash the software on a new sd card and try it agian. i use this type of card. Samsung EVO Plus Micro SDXC 64GB bis zu 100MB/s Class 10 U3

TexanScot commented 5 years ago

Has anyone come up with a solution for this issue. Motioneye running on my Pi Zero W seems to 'lock up' (can't find server and can't SSH to the Pi) after running perfectly for a while. I have to reboot the Pi in order to get Motioneye working again.

What seems strange is that system seems still to be working - when I reboot I can see pictures captured when the Pi was apparently unresponsive. I need to check further that this truly is the case however.

jasaw commented 5 years ago

@TexanScot Please check your wifi connectivity just to rule it out. Make sure your wifi AP is stable, and not too far from your Pi Zero W. The Pi Zero W wifi antenna is pretty bad.

marhau commented 5 years ago

Same behaviour here with a Pi Zero W and motionEye Version 0.39.2, Motion Version 4.1.1 and OS Version motionEyeOS 20180627. Pinging the Pi worked, but everything else timed out. Just got my hands on the powersupply, so its online until next freeze..

To me, it looks like the system hangs after getting "crng init done" in dmesg.log, but the timestamps aren't up to date, so I'm just guessing.

dmesg.log [Thu Jan 1 01:05:35 1970] random: crng init done ---- booting motionEyeOS 20180627 ----

motioneye.log: 2019-03-31 03:13:48: [motioneye] DEBUG: 200 HEAD / (127.0.0.1) 10.82ms 2019-03-31 03:13:53: [motioneye] DEBUG: 200 HEAD / (127.0.0.1) 11.53ms 2019-04-13 20:48:59: [motioneye] INFO: hello! this is motionEye server 0.39.2 2019-04-13 20:49:00: [motioneye] DEBUG: using motion version 4.1.1 2019-04-13 20:49:01: [motioneye] DEBUG: using ffmpeg version 3.3.5

The other logs doesn't reveal anything as far as I can see. Except for messages.log which is unavaiable for some reason.

Maybe the solution is a relay cutting the power once a day.

Edit: Updated to the latest version og MotionEyeOs now. Something went wrong. No contact with my camera in any way :(

Edit2: If we souldn't update to the newest versions via GUI, I wish for a message telling me that in MotionEyeOs.

motioneye-project / motioneyeos