Function "Record" captured only a single frame
Posted: Wed May 08, 2013 12:46 pm
I got ZoneMinder 1.24.2 on Ubuntu server 10.04 with 1 network camera (Instar 2905).
Everything works like expected for more than a year. Zoneminder captured from the camera ( /snapshot.cgi? ) in Record-Mode and records events of 600 sec. length and nearly 3000 frames (5fps).
Yesterday I tried to capture the mjpeg stream from the camera ( /videostream.cgi? ) which didnt work so I switched back to my previous config settings ( /snapshot.cgi? ) but now Zoneminder only capture exactly 1 frame per event (e.g. on disk: in /var/cache/zoneminder/events/1/98781 there is only 001-capture.jpg and .98781)
If I change Zoneminder Function to "Mocord" frames were captured as expected.
There aren't any errors in syslog or debug logs (debuglevel 5) except the difference for zma_m1 writing capture frame:
debug log (function "Mocord")
debug log (function "Record")
Maybe it has somthing to do with the state "prealarm" because of the difference between syslogs
before yesterday (working "Record"-Mode):
and current syslog ("Record"-Mode not working):
Also restarting camera or/and server didn't change that behavior.
Any help would be appreciated
(Sorry for my bad english)
Everything works like expected for more than a year. Zoneminder captured from the camera ( /snapshot.cgi? ) in Record-Mode and records events of 600 sec. length and nearly 3000 frames (5fps).
Yesterday I tried to capture the mjpeg stream from the camera ( /videostream.cgi? ) which didnt work so I switched back to my previous config settings ( /snapshot.cgi? ) but now Zoneminder only capture exactly 1 frame per event (e.g. on disk: in /var/cache/zoneminder/events/1/98781 there is only 001-capture.jpg and .98781)
If I change Zoneminder Function to "Mocord" frames were captured as expected.
There aren't any errors in syslog or debug logs (debuglevel 5) except the difference for zma_m1 writing capture frame:
debug log (function "Mocord")
Code: Select all
05/08/13 13:01:50.146716 zma_m1[20605].INF-zm_monitor.cpp/1272 [Instar2905-Outdoor: 026 - Opening new event 98780, section start]
05/08/13 13:01:50.147151 zma_m1[20605].DB1-zm_event.cpp/515 [Writing capture frame 1]
05/08/13 13:01:50.172141 zma_m1[20605].DB1-zm_event.cpp/527 [Adding frame 1 to DB]
05/08/13 13:01:50.319954 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:2, WI: 3, PF = 1, RM = 24, Step = 1]
05/08/13 13:01:50.320115 zma_m1[20605].INF-zm_monitor.cpp/1326 [Instar2905-Outdoor: 027 - Gone into prealarm state]
05/08/13 13:01:50.327922 zma_m1[20605].DB2-zm_event.cpp/409 [Updating notes for event 98780, 'Linked: Instar2905-Outdoor']
05/08/13 13:01:50.475915 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:3, WI: 4, PF = 1, RM = 24, Step = 1]
05/08/13 13:01:50.476255 zma_m1[20605].DB1-zm_event.cpp/515 [Writing capture frame 2]
05/08/13 13:01:50.513589 zma_m1[20605].DB1-zm_event.cpp/527 [Adding frame 2 to DB]
05/08/13 13:01:50.661560 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:4, WI: 5, PF = 1, RM = 24, Step = 1]
05/08/13 13:01:50.661654 zma_m1[20605].DB1-zm_event.cpp/515 [Writing capture frame 3]
05/08/13 13:01:50.686393 zma_m1[20605].DB1-zm_event.cpp/527 [Adding frame 3 to DB]
Code: Select all
05/08/13 13:02:48.875351 zma_m1[20605].INF-zm_monitor.cpp/1272 [Instar2905-Outdoor: 319 - Opening new event 98781, section start]
05/08/13 13:02:48.875837 zma_m1[20605].DB1-zm_event.cpp/515 [Writing capture frame 1]
05/08/13 13:02:48.900911 zma_m1[20605].DB1-zm_event.cpp/527 [Adding frame 1 to DB]
05/08/13 13:02:49.073019 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:20, WI: 21, PF = 1, RM = 24, Step = 1]
05/08/13 13:02:49.073133 zma_m1[20605].INF-zm_monitor.cpp/1326 [Instar2905-Outdoor: 320 - Gone into prealarm state]
05/08/13 13:02:49.081092 zma_m1[20605].DB2-zm_event.cpp/409 [Updating notes for event 98781, 'Linked: Instar2905-Outdoor']
05/08/13 13:02:49.248983 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:21, WI: 22, PF = 1, RM = 24, Step = 1]
05/08/13 13:02:49.449874 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:22, WI: 23, PF = 1, RM = 24, Step = 1]
05/08/13 13:02:49.650485 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:23, WI: 24, PF = 1, RM = 24, Step = 1]
05/08/13 13:02:49.884519 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:24, WI: 0, PF = 1, RM = 24, Step = 1]
05/08/13 13:02:50.085129 zma_m1[20605].DB4-zm_monitor.cpp/1055 [RI:0, WI: 1, PF = 1, RM = 24, Step = 1]
Maybe it has somthing to do with the state "prealarm" because of the difference between syslogs
before yesterday (working "Record"-Mode):
Code: Select all
May 5 06:40:00 linx2 zma_m1[8014]: INF [Instar2905-Outdoor: 703197 - Closing event 98308, section end]
May 5 06:40:00 linx2 zma_m1[8014]: INF [Instar2905-Outdoor: 703197 - Opening new event 98309, section start]
May 5 06:40:02 linx2 zmc_m1[31396]: INF [Instar2905-Outdoor: 170000 - Capturing at 4.98 fps]
May 5 06:42:41 linx2 zma_m1[8014]: INF [Instar2905-Outdoor: 704000 - Processing at 4.98 fps]
Code: Select all
May 8 13:02:43 linx2 zma_m1[20605]: INF [Instar2905-Outdoor: 293 - Closing event 98780, reloading]
May 8 13:02:48 linx2 zma_m1[20605]: INF [Instar2905-Outdoor: 319 - Opening new event 98781, section start]
May 8 13:02:49 linx2 zma_m1[20605]: INF [Instar2905-Outdoor: 320 - Gone into prealarm state]
May 8 13:05:05 linx2 zmc_m1[20603]: INF [Instar2905-Outdoor: 1000 - Capturing at 4.98 fps]
May 8 13:05:05 linx2 zma_m1[20605]: INF [Instar2905-Outdoor: 1000 - Processing at 4.98 fps]
Any help would be appreciated
(Sorry for my bad english)