1.34.22 (and .20 and .21) MODECT woes

Forum for questions and support relating to the 1.34.x releases only.
sideband
Posts: 14
Joined: Sat Oct 24, 2020 2:19 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by sideband » Mon Oct 26, 2020 10:08 pm

Correction: Red areas have the first frame as a still shot through the whole alarm, not black. No .jpgs are written during the alarm, either (when turned on to see why there was no video).

sideband
Posts: 14
Joined: Sat Oct 24, 2020 2:19 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by sideband » Wed Oct 28, 2020 11:36 pm

Update:

I removed all references to CUDA from ZoneMinder and restarted it, then set for X264Encode.

All the video before and after the trigger event played as normal (with increased CPU usage), but the trigger time (during the red outlined portion) had no video. No .jpgs were generated during the trigger/alert.

The problem does not seem to be cuda. The problem isn't video encoding at all. If it was, then the video before and after the trigger alert time wouldn't be generated at all, and the whole video would be blank.

I'm still at a loss as to why ONLY the trigger events aren't saviing on X264Encode. The H264passthrough records all the video (because nothing's being processed to record the video).. I'd like to get ZM's timestamps back into the recordings, if possible.

I'd hate to have to wipe the whole setup and start over.

Any further thoughts?

Thanks.

User avatar
Bluemax
Posts: 105
Joined: Wed Jun 12, 2019 5:15 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by Bluemax » Thu Oct 29, 2020 12:27 am

I already told you to check for the missing min analysis fps value. Its unusual that default values are missing but possible if its a long standing config. I experienced some values out of bounds as well over time. If you're not familiar with setting up the database manually you probably have to re-setup all i guess. No one ever saw this problem. Hard to tell what it is.

sideband
Posts: 14
Joined: Sat Oct 24, 2020 2:19 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by sideband » Thu Oct 29, 2020 1:45 am

Bluemax wrote:
Thu Oct 29, 2020 12:27 am
I already told you to check for the missing min analysis fps value. Its unusual that default values are missing but possible if its a long standing config.
When I create a new monitor, no values are in the box for min analysis fps, so no entry *is* the default.

I'm curious why the analysis fps would matter to the video being recorded? Analysis is used to detect an event, but why would the analysis fps be necessary to record one? I am, apparently, missing something.

Again: events are being detected. The few seconds before and after the events are being recorded and saved just fine. The event itself is missing from the recordings.

Like this:

videovideovideovideo[frozenfirstframeofevent]videovideovideo
-----------------------------redredredredredredredr-----------------------

"First frame of event" could also be the last frame just before the event.. in any case, it's looking like a removal and reinstallation (and the subsequent loss of the databases and videos) is in order...

I hate to have to do that.

User avatar
Bluemax
Posts: 105
Joined: Wed Jun 12, 2019 5:15 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by Bluemax » Thu Oct 29, 2020 4:34 am

Maybe check the zones first for sanity. Or delete/recreate them.

User avatar
iconnor
Posts: 1388
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by iconnor » Thu Oct 29, 2020 10:58 pm

I'm stumped. We will need debug level logs from zma.

sideband
Posts: 14
Joined: Sat Oct 24, 2020 2:19 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by sideband » Fri Oct 30, 2020 11:10 am

iconnor wrote:
Thu Oct 29, 2020 10:58 pm
I'm stumped. We will need debug level logs from zma.
I can work on getting those for you this weekend.

I appreciate you looking into this.

sideband
Posts: 14
Joined: Sat Oct 24, 2020 2:19 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by sideband » Fri Oct 30, 2020 7:38 pm

Problem:

When I turn on debug mode and put a monitor into X264encode (rather than H264passthrough), that monitor refuses to initialize or capture. No video comes from the monitor at all. If I switch back to passthrough with debug mode on, the monitor acts as it should.

I'm at a loss, but maybe that information might trigger a thought?

Thanks in advance.

User avatar
iconnor
Posts: 1388
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by iconnor » Fri Oct 30, 2020 7:46 pm

Nope no thoughts, need logs.

sideband
Posts: 14
Joined: Sat Oct 24, 2020 2:19 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by sideband » Fri Oct 30, 2020 11:07 pm

Oct 30 14:37:50 maximilian zma_m7[93858]: ERR [zma_m7] [Got empty memory map file size 0, is the zmc process for this monitor running?]
Oct 30 14:37:51 maximilian zma_m7[93861]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:37:54 maximilian zmc_m7[93855]: INF [zmc_m7] [Starting Capture version 1.34.22]
Oct 30 14:37:57 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1 - Capturing at 0.33 fps, capturing bandwidth 225765bytes/sec]
Oct 30 14:37:57 maximilian zma_m7[93882]: INF [zma_m7] [In mode 3/1, warming up]
Oct 30 14:38:01 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:100 - Capturing at 25.00 fps, capturing bandwidth 1662450bytes/sec]
Oct 30 14:38:04 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 100 - Analysing at 12.50 fps]
Oct 30 14:38:08 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:200 - Capturing at 14.29 fps, capturing bandwidth 960397bytes/sec]
Oct 30 14:38:12 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 200 - Analysing at 12.50 fps]
Oct 30 14:38:15 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:300 - Capturing at 14.29 fps, capturing bandwidth 939718bytes/sec]
Oct 30 14:38:20 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 300 - Analysing at 12.50 fps]
Oct 30 14:38:22 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:400 - Capturing at 14.29 fps, capturing bandwidth 1057579bytes/sec]
Oct 30 14:38:28 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 400 - Analysing at 12.50 fps]
Oct 30 14:38:28 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:500 - Capturing at 16.67 fps, capturing bandwidth 1103824bytes/sec]
Oct 30 14:38:35 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:600 - Capturing at 14.29 fps, capturing bandwidth 954333bytes/sec]
Oct 30 14:38:36 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 500 - Analysing at 12.50 fps]
Oct 30 14:38:42 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:700 - Capturing at 14.29 fps, capturing bandwidth 1049920bytes/sec]
Oct 30 14:38:44 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 600 - Analysing at 12.50 fps]
Oct 30 14:38:48 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:800 - Capturing at 16.67 fps, capturing bandwidth 1104390bytes/sec]
Oct 30 14:38:52 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 700 - Analysing at 12.50 fps]
Oct 30 14:38:55 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:900 - Capturing at 14.29 fps, capturing bandwidth 955566bytes/sec]
Oct 30 14:39:00 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 800 - Analysing at 12.50 fps]
Oct 30 14:39:02 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1000 - Capturing at 14.29 fps, capturing bandwidth 1049361bytes/sec]
Oct 30 14:39:08 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 900 - Analysing at 12.50 fps]
Oct 30 14:39:09 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1100 - Capturing at 14.29 fps, capturing bandwidth 946132bytes/sec]
Oct 30 14:39:15 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1200 - Capturing at 16.67 fps, capturing bandwidth 1113951bytes/sec]
Oct 30 14:39:16 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1000 - Analysing at 12.50 fps]
Oct 30 14:39:22 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1300 - Capturing at 14.29 fps, capturing bandwidth 1050027bytes/sec]
Oct 30 14:39:24 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1100 - Analysing at 12.50 fps]
Oct 30 14:39:29 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1400 - Capturing at 14.29 fps, capturing bandwidth 951078bytes/sec]
Oct 30 14:39:33 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1200 - Analysing at 12.50 fps]
Oct 30 14:39:36 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1500 - Capturing at 14.29 fps, capturing bandwidth 944510bytes/sec]
Oct 30 14:39:40 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1300 - Analysing at 12.50 fps]
Oct 30 14:39:42 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1600 - Capturing at 16.67 fps, capturing bandwidth 1223648bytes/sec]
Oct 30 14:39:48 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1400 - Analysing at 12.50 fps]
Oct 30 14:39:49 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1700 - Capturing at 14.29 fps, capturing bandwidth 957623bytes/sec]
Oct 30 14:39:56 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1800 - Capturing at 14.29 fps, capturing bandwidth 945243bytes/sec]
Oct 30 14:39:56 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1500 - Analysing at 12.50 fps]
Oct 30 14:40:03 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:1900 - Capturing at 14.29 fps, capturing bandwidth 1047894bytes/sec]
Oct 30 14:40:04 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1600 - Analysing at 12.50 fps]
Oct 30 14:40:09 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:2000 - Capturing at 16.67 fps, capturing bandwidth 1117151bytes/sec]
Oct 30 14:40:11 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1700 - Analysing at 14.29 fps]
Oct 30 14:40:16 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:2100 - Capturing at 14.29 fps, capturing bandwidth 945749bytes/sec]
Oct 30 14:40:21 maximilian zma_m7[93882]: INF [zma_m7] [CAR-SE: 1800 - Analysing at 10.00 fps]
Oct 30 14:40:23 maximilian zmc_m7[93855]: INF [zmc_m7] [CAR-SE: images:2200 - Capturing at 14.29 fps, capturing bandwidth 1048369bytes/sec]
Oct 30 14:40:27 maximilian zma_m7[94707]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:40:28 maximilian zma_m7[94717]: ERR [zma_m7] [Got empty memory map file size 0, is the zmc process for this monitor running?]
Oct 30 14:40:30 maximilian zma_m7[94732]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:40:32 maximilian zma_m7[94738]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:40:41 maximilian zms_m7[94746]: ERR [zms_m7] [No diff between time_diff = 0.000000 (0:1604083241.373844 - 0:1604083241.373844), ibc: 300]
Oct 30 14:41:45 maximilian zmc_m7[94729]: ERR [zmc_m7] [Unable to open input rtsp://user:pass@10.42.2.27:554/stream0 due to: Invalid data found when processing input]
Oct 30 14:41:47 maximilian zma_m7[95135]: ERR [zma_m7] [Got empty memory map file size 0, is the zmc process for this monitor running?]
Oct 30 14:41:51 maximilian zma_m7[95160]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:42:16 maximilian zma_m7[95335]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:42:17 maximilian zma_m7[95338]: ERR [zma_m7] [Got empty memory map file size 0, is the zmc process for this monitor running?]
Oct 30 14:42:24 maximilian zma_m7[95371]: ERR [zma_m7] [Got empty memory map file size 0, is the zmc process for this monitor running?]
Oct 30 14:42:26 maximilian zma_m7[95385]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:42:28 maximilian zma_m7[95398]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:42:30 maximilian zma_m7[95422]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:42:32 maximilian zma_m7[95432]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:42:58 maximilian zms_m7[95514]: WAR [zms_m7] [Impossible situation. No timestamp on captured image index was 0, image-buffer_count was (300)]
Oct 30 14:42:59 maximilian zms_m7[95514]: message repeated 2 times: [ WAR [zms_m7] [Impossible situation. No timestamp on captured image index was 0, image-buffer_count was (300)]]
Oct 30 14:42:59 maximilian zma_m7[95575]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE]
Oct 30 14:43:01 maximilian zma_m7[95578]: ERR [zma_m7] [Got empty memory map file size 0, is the zmc process for this monitor running?]
Oct 30 14:43:05 maximilian zms_m7[95538]: WAR [zms_m7] [Impossible situation. No timestamp on captured image index was 0, image-buffer_count was (300)]
Oct 30 14:43:05 maximilian zms_m7[95538]: message repeated 2 times: [ WAR [zms_m7] [Impossible situation. No timestamp on captured image index was 0, image-buffer_count was (300)]]


14:41 was when I switched over to X264Encode after turning on debug mode, and that's when the monitor refused to initialize. I let it run for a couple minutes like that before switching back to H264passthrough...

Turning on debug mode seems to break capture altogether.

These logs don't tell me anything, and I'm going to guess they don't tell you anything, either, so, It seems it's time to junk the databases, wipe the configs, and start from scratch.

Thanks for looking, and for your time.

User avatar
iconnor
Posts: 1388
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by iconnor » Sun Nov 01, 2020 9:44 pm

You didn't turn on debug.

Dumping your database will either waste all of our time because we won't be able to figure this out, OR not fix the problem at all. Either way a waste of time.

Last resort, you could give me access to your machine and I will figure it out.

sideband
Posts: 14
Joined: Sat Oct 24, 2020 2:19 pm

Re: 1.34.22 (and .20 and .21) MODECT woes

Post by sideband » Fri Nov 06, 2020 1:48 am

iconnor wrote:
Sun Nov 01, 2020 9:44 pm
You didn't turn on debug.
That was from syslog, with debug turned on.. believe it or don't.

I wasn't just going to blast out the database.. I was planning on removing all vestiges of ZM from the system and re-installing from scratch...

Then, if I still have the issue, it'll show.

This has only been happening since the upgrade from .19 to .20.

At any rate, I guess I've got a weekend project.

Thanks for looking, anyhow. If the problem persists after re-installation, I'll let you know.

Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests