silvanmelchior / RPi_Cam_Web_Interface

A web interface for the RPi Cam
MIT License
1.54k stars 493 forks source link

DEBUG 3 message appearing #466

Closed Pi-DD closed 5 years ago

Pi-DD commented 5 years ago

I was looking at the logs because motion capture had not happened when I would have expected some. (This is running on a remote device 90km away, how I deduce some captures have been missed does not matter!)

I found that DEBUG 3 appears in the logs, usually after reference to the motion mask file.

example....(this follows re-start after update to 6.4.36)

2019/01/02 10:16:01} SIGINT/SIGTERM received, stopping {2019/01/02 10:16:35} RaspiMJPEG Version 5.8.11 {2019/01/02 10:16:35} h264 search /var/www/html/media/vi_0236_20190102_101635.mp4 {2019/01/02 10:16:36} recommended video buffer size 65536 {2019/01/02 10:16:36} h264 size set to 131072 {2019/01/02 10:16:36} recommended video buffers 1 {2019/01/02 10:16:36} h264 buffers set to recommended 1 {2019/01/02 10:16:36} Set up internal detect width=82 height=61 {2019/01/02 10:16:36} Motion mask /var/www/html/motionmask.pgm loaded {2019/01/02 10:16:36} Opening FIFO 0 /var/www/html/FIFO 7 {2019/01/02 10:16:36} Opening FIFO 1 /var/www/html/FIFO11 8 {2019/01/02 10:16:36} MJPEG streaming, ready to receive commands {2019/01/02 10:16:36} send smd 9 {2019/01/02 10:16:36} DEBUG 3 [2019/01/02 10:16:38] RaspiCam support started [2019/01/02 10:16:38] Capture Pipe already exists /var/www/html/FIFO1 {2019/01/02 10:16:38} Starting command loop [2019/01/02 10:16:38] Scheduler loop is started [2019/01/02 10:16:38] Reload parameters command requested [2019/01/02 10:16:38] Scheduler loop is started [2019/01/02 10:16:39] New period detected 0 [2019/01/02 10:16:39] Send md 1 {2019/01/02 10:16:39} Internal motion detection started {2019/01/02 10:16:39} h264 search /var/www/html/media/vi_0236_20190102_101639.mp4 {2019/01/02 10:16:39} recommended video buffer size 65536 {2019/01/02 10:16:39} h264 size set to 131072 {2019/01/02 10:16:39} recommended video buffers 1 {2019/01/02 10:16:39} h264 buffers set to recommended 1 {2019/01/02 10:16:39} Set up internal detect width=82 height=61 {2019/01/02 10:16:39} Motion mask /var/www/html/motionmask.pgm loaded {2019/01/02 10:16:39} DEBUG 3 [2019/01/02 10:16:41] Scheduled management tasks. Next at 1546427799 [2019/01/02 10:16:41] Purged 3 Files

It first appeared about 10 days ago after change of buffer

2018/12/19 20:22:29} Change: video_buffer = 3000 {2018/12/19 20:22:29} DEBUG 3 {2018/12/19 20:23:49} Change: video_buffer = 4000 {2018/12/19 20:23:49} DEBUG 3 [2018/12/19 21:11:36] Scheduled management tasks. Next at 1545257496 [2018/12/19 21:11:36] Purged 1 Files [2018/12/19 22:11:37] Scheduled management tasks. Next at 1545261097 [2018/12/19 22:11:37] Purged 1 Files [2018/12/19 23:11:38] Scheduled management tasks. Next at 1545264698 [2018/12/19 23:11:38] Purged 1 Files [2018/12/20 00:00:10] New period detected 0 [2018/12/20 00:00:10] Send md 1 {2018/12/20 00:00:10} Internal motion detection started {2018/12/20 00:00:10} h264 search /var/www/html/media/vi_0217_20181220_000010.mp4 {2018/12/20 00:00:10} recommended video buffer size 65536 {2018/12/20 00:00:10} h264 size set to 131072 {2018/12/20 00:00:10} recommended video buffers 1 {2018/12/20 00:00:10} h264 buffers set to recommended 1 {2018/12/20 00:00:10} Set up internal detect width=82 height=61 {2018/12/20 00:00:10} Motion mask /var/www/html/motion-mask.pgm loaded {2018/12/20 00:00:11} DEBUG 3

The only other clue is that yesterday this string of errors appeared....

[2019/01/01 21:41:56] Scheduled management tasks. Next at 1546382516 [2019/01/01 21:41:56] Purged 3 Files {2019/01/01 22:05:54} DEBUG 2: 17194, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17195, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17196, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17197, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17198, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17199, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17200, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17201, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17202, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17203, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17204, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17205, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17206, 17215 {2019/01/01 22:05:54} Error: Error in iframe list {2019/01/01 22:05:54} DEBUG 2: 17207, 17215 {2019/01/01 22:05:55} Error: Error in iframe list {2019/01/01 22:05:55} DEBUG 2: 17208, 17215 {2019/01/01 22:05:55} Error: Error in iframe list {2019/01/01 22:05:55} DEBUG 2: 17209, 17215 {2019/01/01 22:05:55} Error: Error in iframe list {2019/01/01 22:05:55} DEBUG 2: 17210, 17215 {2019/01/01 22:05:55} Error: Error in iframe list {2019/01/01 22:05:55} DEBUG 2: 17211, 17215 {2019/01/01 22:05:55} Error: Error in iframe list {2019/01/01 22:05:55} DEBUG 2: 17212, 17216 {2019/01/01 22:05:55} Error: Error in iframe list {2019/01/01 22:05:55} DEBUG 2: 17213, 17216 {2019/01/01 22:05:55} Error: Error in iframe list {2019/01/01 22:05:55} DEBUG 2: 17214, 17216 {2019/01/01 22:05:55} Error: Error in iframe list [2019/01/01 22:12:03] Logged in user:ghill:

roberttidey commented 5 years ago

Error in iframe list occur when it loses sync with the stream of data from the camera. It will normally recover after a burst of these. I am not sure what can trigger them (maybe cpu gets diverted onto other stuff for a short while) but they should be pretty rare.

DEBUG 3 occurs when it is lining up the buffer. You get one of these when the buffer is being used and the settings are changed or when a capture completes. They are quite normal.

Pi-DD commented 5 years ago

Robert, once again, thanks for your swift response.

The iframe explanation makes sense. There is another process running on the Pi and at about that time it went a bit berserk, probably overloading the CPU (it’s only a Pi Zero!). I’ve turned that off whilst I exchange ideas with the developers of the other software.