ZoneMinder Forums

This is a RasPi we're talking about, so physical memory is pretty scarce - hence my 8GB swap pendrive.

I'll try extending the shared memory space, though, see if that gets me anywhere.

Good point, I checked it just now pi@observer:~ $ df -h /dev/shm Filesystem Size Used Avail Use% Mounted on tmpfs 2.0G 660M 1.4G 33% /dev/shm free shows that I still have 7GB of my 8GB swap file free, so memory should not be a concern. I think. Or does ffmpeg always require physical memory and wont ...

I recently swapped out a previous camera to a new one that is identical to the already-added two TP-Link NC450s. After a firmware upgrade, I found that the RTSP stream not requires the username, giving me a bit of a headache, but I got past that. Now , however, I'm finding that ffmpeg doesn't seem ...

I tested disabling compression from the Options screen, but that didn't help, I still got the exact same stacktrace...

Yes, that much I gathered. The thing is, I don't see anywhere on the UI where the compression level may be set...

Following Connor's suggestion to a previous issue, I built a copy of ZoneMinder from the master branch (commit 5a6e700c456176fe2eedc4065caaf9725caae00a ), which managed to fix the issue at hand, but also shed light on another one in which ZM cannot create the ZIP file for upload. On running the ...

Just ran the build with your fix from master, and it seems to have worked, I'm seeing images come up in the right place.

There still seems to be something off in how filters handle paths during compression-upload, but I don't have anything specific on that front yet.

Does anyone have any ideas on how I could debug this further? I'm kind of at a loss as to why ZM would be attempting to write to the root dir...

I've updated to 1.32.3, but writes were not fixed, although new log files now appeared. In particular, one of the analysis daemon logs had this line: 12/12/18 07:10:03.278685 zma_m6[1224].ERR-zm_event.cpp/180 [Can't mkdir /8127: Permission denied] which is both surprising and not: on the one hand ...

Tried that - at debug level 9, with no module restrictions, nothing mentioned any failures. The external drive itself was only referenced when the analysis daemon launched, and never again.

Well, kind of the obvious thing to do, though not sure why writing would be broken in the first place... Running the build will take some time, but once the server is back up, I'll see if it works. If it doesn't, any ideas on how I could try to get to the bottom of it? It doesn't look like a *nix ...

Hi, After a recent upgrade to 1.32.2 (built from source, via packpack, on Raspbian), I've found that ZoneMinder is no longer storing detected images to an external drive. Previously, on 1.31.1, storing worked perfectly well, and I can see the diagnostic images updating in real time, but event ...

Hi,

Yes, I'm using Ext4 on the external drive.

When executing ls -lah (which ll is an alias for, just to be clear), I can see the link pointing to the right directory.

I've been bugged by a persistent problem for a few days now, ever since I added an external drive to the Raspi running ZM: events would be created, JPGs saved, videos recorded, then a few minutes later, they would disappear from the drive without a trace, while remaining in the database. For ...

So it turns out that this line WAR [zmc_m4] [libjpeg-turbo is required for reading a JPEG directly into a RGB32 buffer, reading into a RGB24 buffer instead.] is not a warning. It seems to be, in fact a fatal error , and once I set the color space to 24-bit to get around this (despite libjpeg-turbo ...