Upgraded from 1.34.16 to 1.34.18 no motion events
Upgraded from 1.34.16 to 1.34.18 no motion events
I upgraded from .16 to .18 and after that I cant se any motion events
Not in watch view, not in montage review..
All cameras are in mocord
All I did vas "apt update, apt apgrade" on my pc (Ubuntu)
were do I start to troubleshoot?
Not in watch view, not in montage review..
All cameras are in mocord
All I did vas "apt update, apt apgrade" on my pc (Ubuntu)
were do I start to troubleshoot?
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Start by posting some logs.
This would be a big problem if it affects more than 1 person. The devs have had no problems with motion events.
Please everyone check your systems and report in.
This would be a big problem if it affects more than 1 person. The devs have had no problems with motion events.
Please everyone check your systems and report in.
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Have a test setup running with just one FFMPEG cam. Seems to be working OK except for setting up a USB cam. Ubuntu 20.04 LAMP
Productiion system, 19 cams, in warehouse was upgraded yesterday afternoon. It too gets motion after it was upgraded. Ubuntu 18.04 LEMP
bb
Productiion system, 19 cams, in warehouse was upgraded yesterday afternoon. It too gets motion after it was upgraded. Ubuntu 18.04 LEMP
bb
- bkjaya1952
- Posts: 282
- Joined: Sat Aug 25, 2018 3:24 pm
- Location: Sri Lanka
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
I have tested with fresh installation of Zoneminder 1.34.18 for a Hikvision IP camera and found views ,motion events , and montage review are working correctly .
Only problem that I have noticed is inability in adding usb camera monitors ( This problem has already been informed by a post )
Only problem that I have noticed is inability in adding usb camera monitors ( This problem has already been informed by a post )
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Hi, I think I might be having the same issue as the OP.
I'm using an old laptop with Ubuntu 18.04 and I recently updated to 1.34.18. My cameras that are on mocord records video properly but do not register any motion events. I noticed that if I switch them to modect, everything works perfectly. Motion is detected and I also receive notifications via zmNinja and MQTT.
I restarted ZoneMinder with one of my cameras set to mocord and I see a couple errors show up in the logs for my FrontDoor camera when I step in front of it:
Any assistance would be great.
Thanks!
I'm using an old laptop with Ubuntu 18.04 and I recently updated to 1.34.18. My cameras that are on mocord records video properly but do not register any motion events. I noticed that if I switch them to modect, everything works perfectly. Motion is detected and I also receive notifications via zmNinja and MQTT.
I restarted ZoneMinder with one of my cameras set to mocord and I see a couple errors show up in the logs for my FrontDoor camera when I step in front of it:
Code: Select all
2020-08-09 17:48:16 zmc_m2 16594 INF FrontDoor: images:600 - Capturing at 7.14 fps, capturing bandwidth 304160bytes/sec zm_monitor.cpp 2534
2020-08-09 17:48:15 zma_m1 16597 INF Driveway: 500 - Analysing at 6.25 fps zm_monitor.cpp 1303
2020-08-09 17:48:14 zmc_m1 16586 INF Driveway: images:500 - Capturing at 6.25 fps, capturing bandwidth 669701bytes/sec zm_monitor.cpp 2534
2020-08-09 17:48:12 zma_m2 16803 INF In mode 5/1, warming up zma.cpp 136
2020-08-09 17:48:12 zma_m2 16803 INF FrontDoor: 001 - Opening new event 78424, section start zm_monitor.cpp 1525
2020-08-09 17:48:12 zmc_m2 16594 INF Re-starting video storage module zm_ffmpeg_camera.cpp 806
2020-08-09 17:48:12 zmc_m2 16594 INF Opening video storage stream /var/cache/zoneminder/events/2/2020-08-09/78424/78424-video.mp4 format: mp4 zm_videostore.cpp 63
2020-08-09 17:48:12 zmc_m2 16594 INF some options not used, turn on debugging for a list. zm_videostore.cpp 440
2020-08-09 17:48:12 zmc_m2 16594 INF Didn't find a frame before event starttime. keeping all zm_packetqueue.cpp 321
2020-08-09 17:48:12 zmc_m2 16594 INF Event video offset is 73.673 sec (<0 means video starts early) zm_ffmpeg_camera.cpp 883
2020-08-09 17:48:11 zmdc 16556 INF 'zma -m 2' starting at 20/08/09 17:48:11, pid = 16803 zmdc.pl
2020-08-09 17:48:11 zmdc 16803 INF 'zma -m 2' started at 20/08/09 17:48:11 zmdc.pl
2020-08-09 17:48:11 zmdc 16556 INF Starting pending process, zma -m 2 zmdc.pl
2020-08-09 17:48:11 zms_m2 16799 INF Authenticated user 'hassio' zm_user.cpp 141
2020-08-09 17:48:11 zmc_m2 16594 WAR Buffer overrun at index 1, image 561, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 2497
2020-08-09 17:48:11 zms_m3 16800 INF Authenticated user 'hassio' zm_user.cpp 141
2020-08-09 17:48:11 zms_m1 16801 INF Authenticated user 'hassio' zm_user.cpp 141
2020-08-09 17:48:10 zmdc 16556 ERR 'zma -m 2' exited abnormally, exit status 11 zmdc.pl
2020-08-09 17:48:09 zma_m2 16599 ERR Signal address is 0x47075cf0, from 0x4a2841 zm_signal.cpp 83
2020-08-09 17:48:09 zma_m2 16599 ERR Backtrace 0: /usr/bin/zma(_Z14zm_die_handleriP9siginfo_tPv+0x7c) [0x4e491c] zm_signal.cpp 104
2020-08-09 17:48:09 zma_m2 16599 ERR Backtrace 1: linux-gate.so.1(__kernel_rt_sigreturn+0) [0xb7fd5bcc] zm_signal.cpp 104
2020-08-09 17:48:09 zma_m2 16599 ERR Backtrace 2: /usr/bin/zma(_ZN5Event16AddPreAlarmFrameEP5Image7timevaliS1_+0x91) [0x4a2841] zm_signal.cpp 104
2020-08-09 17:48:09 zma_m2 16599 ERR Backtrace 3: /usr/bin/zma(_ZN7Monitor7AnalyseEv+0x25a6) [0x4a1c76] zm_signal.cpp 104
2020-08-09 17:48:09 zma_m2 16599 ERR Backtrace 4: /usr/bin/zma(main+0x46c) [0x4704ec] zm_signal.cpp 104
2020-08-09 17:48:09 zma_m2 16599 ERR Backtrace 5: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0xb56a0e91] zm_signal.cpp 104
2020-08-09 17:48:09 zma_m2 16599 ERR Backtrace 6: /usr/bin/zma(+0x1c6b9) [0x4716b9] zm_signal.cpp 104
2020-08-09 17:48:09 zma_m2 16599 INF addr2line -e /usr/bin/zma 0x4e491c 0xb7fd5bcc 0x4a2841 0x4a1c76 0x4704ec 0xb56a0e91 0x4716b9 zm_signal.cpp 112
2020-08-09 17:48:09 zma_m2 16599 INF Backtrace complete, please execute the following command for more information zm_signal.cpp 111
2020-08-09 17:48:08 zma_m2 16599 INF FrontDoor: 484 - Gone into alarm state PreAlarmCount: 13 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:08 zma_m2 16599 INF FrontDoor: 485 - Gone into alarm state PreAlarmCount: 14 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:08 zma_m2 16599 INF FrontDoor: 486 - Gone into alarm state PreAlarmCount: 15 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:08 zma_m2 16599 INF FrontDoor: 487 - Gone into alarm state PreAlarmCount: 16 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:08 zma_m2 16599 ERR Got signal 11 (Segmentation fault), crashing zm_signal.cpp 52
2020-08-09 17:48:07 zma_m2 16599 INF FrontDoor: 481 - Gone into alarm state PreAlarmCount: 10 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:07 zma_m2 16599 INF FrontDoor: 482 - Gone into alarm state PreAlarmCount: 11 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:07 zma_m2 16599 INF FrontDoor: 483 - Gone into alarm state PreAlarmCount: 12 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:07 zma_m2 16599 INF FrontDoor: 480 - Gone into alarm state PreAlarmCount: 9 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:07 zma_m2 16599 INF FrontDoor: 479 - Gone into alarm state PreAlarmCount: 8 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:06 zma_m2 16599 INF FrontDoor: 478 - Gone into alarm state PreAlarmCount: 7 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:06 zma_m2 16599 INF FrontDoor: 477 - Gone into alarm state PreAlarmCount: 6 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:06 zma_m2 16599 INF FrontDoor: 476 - Gone into alarm state PreAlarmCount: 5 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:06 zma_m2 16599 INF FrontDoor: 475 - Gone into alarm state PreAlarmCount: 4 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:06 zma_m2 16599 INF FrontDoor: 474 - Gone into alarm state PreAlarmCount: 3 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:05 zma_m2 16599 INF FrontDoor: 473 - Gone into alarm state PreAlarmCount: 2 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:05 zma_m2 16599 INF FrontDoor: 471 - Gone into prealarm state zm_monitor.cpp 1640
2020-08-09 17:48:05 zma_m2 16599 INF FrontDoor: 468 - Gone into alarm state PreAlarmCount: 14 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:04 zma_m2 16599 INF FrontDoor: 464 - Gone into alarm state PreAlarmCount: 10 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:04 zma_m3 16607 INF DCS: 500 - Analysing at 6.67 fps zm_monitor.cpp 1303
2020-08-09 17:48:04 zma_m2 16599 INF FrontDoor: 465 - Gone into alarm state PreAlarmCount: 11 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:04 zma_m2 16599 INF FrontDoor: 466 - Gone into alarm state PreAlarmCount: 12 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:04 zma_m2 16599 INF FrontDoor: 467 - Gone into alarm state PreAlarmCount: 13 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:03 zma_m2 16599 INF FrontDoor: 459 - Gone into alarm state PreAlarmCount: 5 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:03 zma_m2 16599 INF FrontDoor: 460 - Gone into alarm state PreAlarmCount: 6 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:03 zma_m2 16599 INF FrontDoor: 461 - Gone into alarm state PreAlarmCount: 7 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:03 zmc_m3 16603 INF DCS: images:500 - Capturing at 6.67 fps, capturing bandwidth 293760bytes/sec zm_monitor.cpp 2534
2020-08-09 17:48:03 zma_m2 16599 INF FrontDoor: 462 - Gone into alarm state PreAlarmCount: 8 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:03 zma_m2 16599 INF FrontDoor: 463 - Gone into alarm state PreAlarmCount: 9 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:02 zma_m2 16599 INF FrontDoor: 457 - Gone into alarm state PreAlarmCount: 3 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:02 zma_m2 16599 INF FrontDoor: 458 - Gone into alarm state PreAlarmCount: 4 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:02 zma_m2 16599 INF FrontDoor: 456 - Gone into alarm state PreAlarmCount: 2 > AlarmFrameCount:3 Cause: All zm_monitor.cpp 1565
2020-08-09 17:48:02 zmc_m2 16594 INF FrontDoor: images:500 - Capturing at 7.14 fps, capturing bandwidth 328829bytes/sec zm_monitor.cpp 2534
2020-08-09 17:48:02 zma_m2 16599 INF FrontDoor: 454 - Gone into prealarm state zm_monitor.cpp 1640
2020-08-09 17:48:01 zma_m2 16599 INF ExtendAlarm count: 0, ExtendAlarm frames: 0 zm_zone.cpp 188
Thanks!
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Same issue as w00tl00ps
Ubuntu 1804, when change to modect there are alarms in live watch and it works.
change back to mocord, no alarm
Ubuntu 1804, when change to modect there are alarms in live watch and it works.
change back to mocord, no alarm
Code: Select all
2020-08-10 01:23:33.911015 zma_m4[13845].INF-zm_monitor.cpp/1303 [Bullet: 400 - Analysing at 11.11 fps]
2020-08-10 01:23:24.044850 zma_m4[13845].INF-zm_monitor.cpp/1303 [Bullet: 300 - Analysing at 9.09 fps]
2020-08-10 01:23:13.690208 zma_m4[13845].INF-zm_monitor.cpp/1303 [Bullet: 200 - Analysing at 10.00 fps]
2020-08-10 01:23:03.688982 zma_m4[13845].INF-zm_monitor.cpp/1303 [Bullet: 100 - Analysing at 8.33 fps]
2020-08-10 01:22:55.042767 zma_m4[13845].INF-zm_monitor.cpp/1525 [Bullet: 001 - Opening new event 46710, section start]
2020-08-10 01:22:54.948125 zma_m4[13845].INF-zma.cpp/136 [In mode 5/1, warming up]
2020-08-10 01:22:50.694376 zma_m4[13843].ERR-zm_monitor.cpp/580 [Got empty memory map file size 0, is the zmc process for this monitor running?]
2020-08-10 01:22:49.551621 zma_m4[13831].ERR-zm_monitor.cpp/499 [Shared data not initialised by capture daemon for monitor Bullet]
2020-08-10 01:22:41.833476 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 800 - Analysing at 10.00 fps]
2020-08-10 01:22:31.835520 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 700 - Analysing at 10.00 fps]
2020-08-10 01:22:21.785762 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 600 - Analysing at 10.00 fps]
2020-08-10 01:22:11.810197 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 500 - Analysing at 10.00 fps]
2020-08-10 01:22:01.770381 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 400 - Analysing at 10.00 fps]
2020-08-10 01:21:51.783194 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 300 - Analysing at 10.00 fps]
2020-08-10 01:21:41.779673 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 200 - Analysing at 10.00 fps]
2020-08-10 01:21:31.730145 zma_m4[13800].INF-zm_monitor.cpp/1303 [Bullet: 100 - Analysing at 5.00 fps]
2020-08-10 01:21:23.287703 zma_m4[13800].INF-zma.cpp/136 [In mode 3/1, warming up]
2020-08-10 01:21:05.937495 zma_m4[13798].ERR-zm_monitor.cpp/580 [Got empty memory map file size 0, is the zmc process for this monitor running?]
2020-08-10 01:20:59.665702 zma_m4[13796].INF-zma.cpp/136 [In mode 3/1, warming up]
2020-08-10 01:20:06.008530 zma_m4[13778].INF-zm_monitor.cpp/1303 [Bullet: 300 - Analysing at 10.00 fps]
2020-08-10 01:19:56.018426 zma_m4[13778].INF-zm_monitor.cpp/1303 [Bullet: 200 - Analysing at 9.09 fps]
2020-08-10 01:19:45.971072 zma_m4[13778].INF-zm_monitor.cpp/1303 [Bullet: 100 - Analysing at 11.11 fps]
2020-08-10 01:19:38.040937 zma_m4[13778].INF-zma.cpp/136 [In mode 3/1, warming up]
2020-08-10 01:19:34.643202 zma_m4[13772].ERR-zm_monitor.cpp/499 [Shared data not initialised by capture daemon for monitor Bullet]
2020-08-10 01:19:33.978685 zma_m4[13720].INF-zm_event.cpp/593 [Updating frames delta by -0.24 sec to match video file]
2020-08-10 01:19:33.903943 zma_m4[13720].INF-zm_monitor.cpp/692 [Bullet: image_count:2722 - Closing event 46707, shutting down]
2020-08-10 01:19:31.740048 zma_m4[13720].INF-zm_monitor.cpp/1303 [Bullet: 2700 - Analysing at 10.00 fps]
2020-08-10 01:19:21.743673 zma_m4[13720].INF-zm_monitor.cpp/1303 [Bullet: 2600 - Analysing at 10.00 fps]
2020-08-10 01:19:11.728719 zma_m4[13720].INF-zm_monitor.cpp/1303 [Bullet: 2500 - Analysing at 10.00 fps]
Code: Select all
2020-08-10 01:23:41.509876 zmc_m4[13844].INF-zm_monitor.cpp/2534 [Bullet: images:500 - Capturing at 10.00 fps, capturing bandwidth 228264bytes/sec]
2020-08-10 01:23:31.489113 zmc_m4[13844].INF-zm_monitor.cpp/2534 [Bullet: images:400 - Capturing at 12.50 fps, capturing bandwidth 283928bytes/sec]
2020-08-10 01:23:23.333653 zmc_m4[13844].INF-zm_monitor.cpp/2534 [Bullet: images:300 - Capturing at 8.33 fps, capturing bandwidth 191234bytes/sec]
2020-08-10 01:23:11.466931 zmc_m4[13844].INF-zm_monitor.cpp/2534 [Bullet: images:200 - Capturing at 10.00 fps, capturing bandwidth 228663bytes/sec]
2020-08-10 01:23:01.448478 zmc_m4[13844].INF-zm_monitor.cpp/2534 [Bullet: images:100 - Capturing at 14.29 fps, capturing bandwidth 309685bytes/sec]
2020-08-10 01:22:55.210537 zmc_m4[13844].INF-zm_ffmpeg_camera.cpp/883 [Event video offset is -0.129 sec (<0 means video starts early)]
2020-08-10 01:22:55.185561 zmc_m4[13844].INF-zm_videostore.cpp/440 [some options not used, turn on debugging for a list.]
2020-08-10 01:22:55.106190 zmc_m4[13844].INF-zm_videostore.cpp/63 [Opening video storage stream /mnt/sdb/sdb_zm/events/4/2020-08-10/46710/46710-video.mp4 format: mp4]
2020-08-10 01:22:54.248544 zmc_m4[13844].INF-zm_monitor.cpp/2534 [Bullet: images:1 - Capturing at 0.33 fps, capturing bandwidth 35111bytes/sec]
2020-08-10 01:22:51.023613 zmc_m4[13844].INF-zmc.cpp/223 [Starting Capture version 1.34.18]
2020-08-10 01:22:50.748056 zmc_m4[13844].INF-zm_ffmpeg.cpp/84 [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets]
2020-08-10 01:22:50.024802 zmc_m4[13827].ERR-zm_ffmpeg_camera.cpp/630 [swscale does not support the codec format for input: (null)]
2020-08-10 01:22:49.662761 zmc_m4[13827].INF-zmc.cpp/223 [Starting Capture version 1.34.18]
2020-08-10 01:22:49.384253 zmc_m4[13827].INF-zm_ffmpeg.cpp/84 [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets]
2020-08-10 01:22:40.061753 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:800 - Capturing at 9.09 fps, capturing bandwidth 206101bytes/sec]
2020-08-10 01:22:29.888636 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:700 - Capturing at 10.00 fps, capturing bandwidth 228586bytes/sec]
2020-08-10 01:22:19.876407 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:600 - Capturing at 10.00 fps, capturing bandwidth 234757bytes/sec]
2020-08-10 01:22:09.855200 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:500 - Capturing at 11.11 fps, capturing bandwidth 253591bytes/sec]
2020-08-10 01:22:00.032729 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:400 - Capturing at 9.09 fps, capturing bandwidth 207153bytes/sec]
2020-08-10 01:21:49.816756 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:300 - Capturing at 10.00 fps, capturing bandwidth 228512bytes/sec]
2020-08-10 01:21:39.811617 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:200 - Capturing at 10.00 fps, capturing bandwidth 228308bytes/sec]
2020-08-10 01:21:29.801311 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:100 - Capturing at 14.29 fps, capturing bandwidth 309600bytes/sec]
2020-08-10 01:21:22.612082 zmc_m4[13799].INF-zm_monitor.cpp/2534 [Bullet: images:1 - Capturing at 0.06 fps, capturing bandwidth 7791bytes/sec]
2020-08-10 01:21:08.763713 zmc_m4[13799].ERR-zm_ffmpeg_camera.cpp/394 [Unable to open input rtsp://xxxxxxx@192.168.1.98:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: No route to host]
2020-08-10 01:21:06.409980 zmc_m4[13799].INF-zmc.cpp/223 [Starting Capture version 1.34.18]
2020-08-10 01:21:06.154074 zmc_m4[13799].INF-zm_ffmpeg.cpp/84 [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets]
2020-08-10 01:20:59.531116 zmc_m4[13768].INF-zmc.cpp/318 [Failed to capture image from monitor 4 Bullet (1/1)]
2020-08-10 01:20:59.504190 zmc_m4[13768].INF-zm_monitor.cpp/2448 [Return from Capture (-1), signal loss]
2020-08-10 01:20:59.479101 zmc_m4[13768].INF-zm_ffmpeg_camera.cpp/759 [Unable to read packet from stream 0: error -541478725 "End of file".]
2020-08-10 01:20:59.453997 zmc_m4[13768].WAR-zm_ffmpeg_camera.cpp/976 [Unable to receive frame 313: code -1094995529 Invalid data found when processing input. error count is 0]
2020-08-10 01:20:59.429023 zmc_m4[13768].ERR-zm_ffmpeg.cpp/548 [Unable to send packet Invalid data found when processing input, continuing]
2020-08-10 01:20:05.188199 zmc_m4[13768].INF-zm_monitor.cpp/2534 [Bullet: images:300 - Capturing at 10.00 fps, capturing bandwidth 228158bytes/sec]
2020-08-10 01:19:55.169262 zmc_m4[13768].INF-zm_monitor.cpp/2534 [Bullet: images:200 - Capturing at 10.00 fps, capturing bandwidth 228433bytes/sec]
2020-08-10 01:19:45.160826 zmc_m4[13768].INF-zm_monitor.cpp/2534 [Bullet: images:100 - Capturing at 14.29 fps, capturing bandwidth 311294bytes/sec]
2020-08-10 01:19:38.000490 zmc_m4[13768].INF-zm_monitor.cpp/2534 [Bullet: images:1 - Capturing at 0.25 fps, capturing bandwidth 26617bytes/sec]
2020-08-10 01:19:34.776362 zmc_m4[13768].INF-zmc.cpp/223 [Starting Capture version 1.34.18]
2020-08-10 01:19:34.465460 zmc_m4[13768].INF-zm_ffmpeg.cpp/84 [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets]
2020-08-10 01:19:29.330789 zmc_m4[13716].INF-zm_monitor.cpp/2534 [Bullet: images:2700 - Capturing at 10.00 fps, capturing bandwidth 228514bytes/sec]
2020-08-10 01:19:19.316436 zmc_m4[13716].INF-zm_monitor.cpp/2534 [Bullet: images:2600 - Capturing at 10.00 fps, capturing bandwidth 228229bytes/sec]
2020-08-10 01:19:09.308186 zmc_m4[13716].INF-zm_monitor.cpp/2534 [Bullet: images:2500 - Capturing at 10.00 fps, capturing bandwidth 228201bytes/sec]
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
I also have this issue with 1.34.18 as w00tl00ps and drkananga described, my cameras on Modect is working, but Mocord does not register any alerted frames.
Ubuntu 18.04.5 LTS
zoneminder 1.34.18-bionic1
zoneminder-doc 1.34.18-bionic1
Ubuntu 18.04.5 LTS
zoneminder 1.34.18-bionic1
zoneminder-doc 1.34.18-bionic1
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
I am seeing the same issue. After upgrading one of my machines to 1.34.18, all MOCORD event detection stopped. I have a few other ZM installs that are still at 1.34.16 and they are still working as expected. As mentioned above, I can switch to MODECT and it works like it is supposed to.
This particular ZM setup has 3 servers with 70 monitors. The CPU usage is down across the board on all of them.
This particular ZM setup has 3 servers with 70 monitors. The CPU usage is down across the board on all of them.
Chris
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Is it possible to downgrade to 1.34.16?
If so, how?
If so, how?
- bkjaya1952
- Posts: 282
- Joined: Sat Aug 25, 2018 3:24 pm
- Location: Sri Lanka
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Download the Zoneminder 1.34.16 deb file that suit to your Linux system from the following Isaac's web site and install .
Then On the terminal and run
zmupdate.pl
to downgrade the data base.
https://launchpad.net/~iconnor/+archive ... tate=built
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
I'll try to investigate and get a fix out today.
In the meantime yeah just install the deb for 1.34.16.
In the meantime yeah just install the deb for 1.34.16.
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
I'm running in dlandon/zoneminder Docker containers. His Dockerfile picks up whatever you have on your 1.34 PPA. I don't see an easy way to downgrade that so I'll just hang on for an update. Thanks for your work on this iconnor.
Chris
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
So far unable to reproduce this.
w00tl00ps appears to actually have a segfault occurring. Is anyone else having a segfault?
What do people have for their pre-alarm frames and other buffer settings?
w00tl00ps appears to actually have a segfault occurring. Is anyone else having a segfault?
What do people have for their pre-alarm frames and other buffer settings?
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Okay I think I found it.
- bkjaya1952
- Posts: 282
- Joined: Sat Aug 25, 2018 3:24 pm
- Location: Sri Lanka
Re: Upgraded from 1.34.16 to 1.34.18 no motion events
Download the Zoneminder 1.34.16 to the host computer
Start the container
sudo docker start Zoneminder
Copy the zoneminder deb file from the host to the container .
sudo docker cp zoneminder.deb Zoneminder:/
Go in to the container and install the copied deb
sudo docker exec -t -i Zoneminder /bin/bash
dpkg -i zoneminder .deb
zmupdate.pl
exit
sudo docker restart Zoneminder
Note:- replace zoneminder.deb with the actual name of the zoneminder 1.34.16 file
Last edited by bkjaya1952 on Fri Aug 14, 2020 10:55 am, edited 5 times in total.