My last effort was converting 1 of my 2 MotionEyeOS Pi's to a dedicated Raspbian fresh install. I have tried different setup's and gave feedback here on the issue tracker. Since another user stated problem also occured when recording his movies to dropbox/. OR MOTION module which is outdated in MotionEyeOS.We've cleary stated that it is a recording movie problem, since the video stream does not crash when no movies are recorded by motion. Jigsaw's and your reponse now is exact 45 days after initial problem reporting began. (Including soft & hardware (Pi) versions, setup, attached devices, motion settings, recording or not to movie/pictures, log files. These issues were reported since beginning december 2018. A config change or restart brings the camera back. It will run for a few hours, capture and upload to my Google Drive (capture on motion) then lose connection to the camera. Did a fresh install on the latest release (previously had a July dev release which gave me no issues) and have both restored a config and done a fresh setup and I'm having the same issues. I can confirm that I am having the same issue as listed here. The webinterfaces is still running and a simple config change and Save button restarts the thread with again a connected camera image. I got this problem on my 2 rescent upgraded Pi's (refresh installed latest image (20181210) and restored my old config) Log only shows that thread 1 has a watchdog timeout and could not be restarted. I do not believe it is a network issue, as per my above reply to I have an open SSH session and constant connection monitor running on my desktop and those are not erroring out.Įvery day, multiple times my Raspberry Pi3B+ loses connection with the attached raspberry pi camera module. I am disabling the notification now and see how that goes. So I have it emailing me when it detects motion, and it seems that either that, or the motion detection is causing an issue. main: Thread 1 - Watchdog timeout, did NOT restart graceful, killing it! main: Thread 1 - Watchdog timeout, trying to do a graceful restart Here are the log entries from that time:ĭec 4 09:37:41 Snake-Cam user.err motion: main: Thread 1 - Watchdog timeout, trying to do a graceful restartĭec 4 09:38:41 Snake-Cam user.err motion: main: Thread 1 - Watchdog timeout, did NOT restart graceful, killing it!ĭec 4 09:38:42 Snake-Cam user.err motion: main: cleaning Thread 1 One thing I noticed when I found it stopped is that the last image taken was at 09:37:10 local time. I also changed the still images to just save every 10 seconds, not on motion detection. I currently have it saving locally and not to SMB. With the new microSD card I was super hopeful as it went quite a bit longer than it had been. OK I think I may have made some progress. I have read the other similar posts but nothing that has been suggested there has worked. I disabled the "Connectivity check" option - no effect. I was getting some errors related to power in my logs so I ordered an official RPi 2.5a power source - the errors in the logs stopped but the camera still stops working. I started off saving motion images and videos to a network share, but have changed it to save local - no effect, I was previously using this device to run OctoPrint to control and monitor my 3D printer, and it would run for days, even months without issue. I can get it to restart by rebooting or by turning off/on the video source and applying but it's basically useless at this point is I have to do this as the point is to catch images and videos of my snake who often comes out when nobody is around. The camera will stop working several times a day to where it shows the broken camera image but the UI still loads. I have my RPi 3 B Running motionEyeOS dev20181126 / MotionEye 0.39.3 and USB Logitech C920 to monitor my snake.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |