Arch Linux User Repository

Thing is it was quite happy running before I did the latest update, so it cant be the camera or Ram, as they did not change. But yer I dont think its your PKGBUILD file, I think Zoneminder is extremely prone to breaking and is sucking up my time.

Can anyone recommend something more reliable?

@chapatt

Yeah, I wanted to make a 1-click-install type of PKGBUILD for personal convenience, so package testing would be easier. Now that I know everything works fine, If and when I adopt this package (I've filed an orphan request since a couple weeks ago) I aim to change the install procedure into a saner (and safer) one, i.e. provide the needed files and detailed instructions and leave it to the user to setup Nginx, Apache, MariaDB et al as they see fit. And I also want to include a conf file for Apache besides Nginx, and make both of them into optional dependencies with separate instructions for each.

It goes without saying that I could use any and all feedback on proper packaging when the time comes.

@whata-mess

Yup, I got that same error myself. Doing a little research (the issue has been mentioned at /r/zoneminder and also at the official forums) I've concluded that it's either a bug in ZoneMinder itself, an incompatibility with some specific camera models, or a misconfiguration on the user's part. In my case it was the tracking module that produced the error (zmtrack.pl) while in your case it's the capture and analysis module (zmdc.pl) so it seems that this is more of a symptom than an issue: whenever something breaks for whatever reason, the responsible module crashes, its assigned mmap is deleted and consequently ZoneMinder throws a "/dev/shm/zm.mmap does not exist" error, which in plain English simply means "sorry guys there was an error somewhere and something crashed".

That means we're probably talking about two different issues here, so we're probably not talking about a specific bug but rather something that has to do either with the specific cameras we're using or with some error in our configuration. So as a first step you can try messing with your settings or, even better, try to use a different camera (preferably from a different vendor) if you have access to one, and see if you get the same error. But really, as I've already said before, ZoneMinder under the hood is really not a "beautiful" software so this could very well be a bug.

As far as I am concerned though, as a packager, this has nothing to do with my PKGBUILD. Since you've managed to run the software, then I can safely assume that you've built it and installed it without issues, just as I and a couple of others have also done. So that's "mission accomplished" on my part :)

EDIT: As an aside, since memory maps obviously have to do with RAM, and since as far as I know ZoneMinder is a RAM hungry beast, this could simply be the result of running out of RAM. Never occurred to me before, for some reason. I'll check if that's the cause of the issue next time I build and install ZoneMinder (which will probably be when my orphan request finally gets accepted).

I get the same error with your new version aswell,

2018-09-30 21:20:31 zmwatch 21857 ERR Memory map file '/dev/shm/zm.mmap.1' does not exist. zmc might not be running. zmwatch.pl
2018-09-30 21:20:27 zmdc 21797 ERR 'zmc -m 1' exited abnormally, exit status 127 zmdc.pl

Hey, thanks for this @Nocifer. It's super hacky (by your own admission), but it installed without issue. Maiming the default nginx config and auto-enabling the systemd unit are the bits that would probably normally scare me, but in this case it's on a machine I don't care about.

@whata-mess

Is this with the updated PKGBUILD I've posted a few comments below, or with the current "official" PKGBUILD?

If the former, then these issues might have to do with you trying to perform the upgrade on an old and largely incompatible ZoneMinder installation (too many things have changed in my PKGBUILD, from different perl modules to the switching out of Apache in favor of Nginx). Do a clean install and see if that fixes your issues. For what it's worth, so far on a current Arch installation it's been running almost flawlessly, and it builds fine without any need for "symbolic links to old libs" or blacklisting packages or any such wizardry.

If the latter, then do use my PKGBUILD, but once again as a precaution try to do a clean install and NOT an upgrade. Less potential headaches that way.

Jesus this thing sucks! Every time I update it breaks, I have so many symbolic links to old libs and blacklisted package updates and it still breaks every time I update.

I have no idea what is wrong with this time

Sep 28 12:44:06 arch zmwatch[1541]: ERR [Can't open memory map file '/dev/shm/zm.mmap.1': Permission denied] Sep 28 12:44:06 arch zmwatch[1541]: INF [Restarting capture daemon for Monitor-1, shared data not valid] Sep 28 12:44:06 arch zmdc[952]: INF ['zmc -m 1' starting at 18/09/28 12:44:06, pid = 3240] Sep 28 12:44:06 arch zmdc[3240]: INF ['zmc -m 1' started at 18/09/28 12:44:06] Sep 28 12:44:06 arch zmdc[952]: ERR ['zmc -m 1' exited abnormally, exit status 127] Sep 28 12:44:16 arch zmwatch[1541]: ERR [Can't open memory map file '/dev/shm/zm.mmap.1': Permission denied] Sep 28 12:44:16 arch zmwatch[1541]: INF [Restarting capture daemon for Monitor-1, shared data not valid] Sep 28 12:44:16 arch zmdc[3251]: INF ['zmc -m 1' started at 18/09/28 12:44:16] Sep 28 12:44:16 arch zmdc[952]: INF ['zmc -m 1' starting at 18/09/28 12:44:16, pid = 3251] Sep 28 12:44:16 arch zmdc[952]: ERR ['zmc -m 1' exited abnormally, exit status 127]

@alanking

• I should have mentioned that when I said libvlc, I really meant the vlc package (which is already listed as an optional dependency in my PKGBUILD). Arch does not officially provide separate packages for the VLC GUI and its internal mechanics, like some other distros do, and I can't be sure if the two libvlc packages in the AUR are good or not (if you say you already tried them and ZoneMinder kept complaining, well... there you have it). So if you want to experiment with the libvlc backend you'll have to install the VLC player itself, along with all its bells and whistles.

• But I think I found a much better solution: there is an AUR package called ffmpeg-full which provides an ffmpeg build with every possible feature enabled, which means that yes, it also includes libavresample (and likely will continue to do so in the future - I of course wouldn't hold my breath, since libavresample has been flagged as deprecated in upstream, but you can at least buy yourself some time until ZoneMinder hopefully updates itself to not require that library). So you can install that package instead of the official ffmpeg and be done with it.

As for your camera issues, the first thing you should do is check the various logs (/var/log/zoneminder/*.log and the systemd journal, or the 'Logs' screen from within ZoneMinder itself) and see if there are any errors reported. I also encountered some issues, as I mentioned in my first comment, which in my case had mostly to do with the tracking module (zmtrack.pl) constantly crashing, something I found out about by reading the logs. These kinds of issues are most probably incompatibility issues with old(ish) or cheap(ish) cameras, but I'm not knowledgeable enough about ZoneMinder to say for certain.

EDIT: Something just occurred to me. Since you installed zoneminder while on ffmpeg 4.0.2, which includes libavresample, then, as it is a library dependency zoneminder is built against, you will have to rebuild zoneminder so it knows the library is no longer available. Only updating ffmpeg to 4.0.3, which silently removes libavresample, would result in the current situation: zoneminder thinking libavresample is there, trying to use it, and failing.

The same goes for libvlc as well - did you rebuild zoneminder after installing it? If not, then it could be that the libvlc packages in the AUR are perfectly working, and you would still have a problem: zoneminder only knows what libraries were available during install time, so any new or changed requirements would need a rebuild. Which in a perfect world would translate in this package getting a release number bump and getting rebuilt automatically, something I would do myself if I were the package maintainer but alas, I'm not (yet).

So, long story short, try rebuilding zoneminder AFTER updating ffmpeg to 4.0.3 and/or installing either libvlc or vlc, and see if that resolves your issues.

EDIT 2: Just ran a test with libvlc installed, and zoneminder failed to build, so that's a no-go. Judging by the state of that package (wrong version numbers, unused variables, missing sources, etc) I wouldn't recommend installing it even if it had somehow worked. But anyway, the good news is that everything worked a-okay with the official vlc package installed, so previous advice is still relevant: install either vlc or preferably ffmpeg-full, then rebuild zoneminder.

Hi Nocifer, Thanks for the time taken to reply. Yes it is a problem with AVResample that broke ffmpeg. I can not for the life of me get libvlc working. I installed libvlc from the AUR but zoneminder is saying i have to install required libraries to use libvlc, even after i have it installed. the problems i get a sometimes the cameras just stop responding when switching through them or just not allowing recordings to play back. Never had that issue on the previous build of zm. I do think its more likely to be a zm issue then an issue with your build. In the mean time i guess i can just freeze the build of ffmpeg i have installed to keep AAVResample installed.

@alanking

Would you care to elaborate on what kind of "a few problems here or there" you've been having? I'd like to fix them if I can (and if they're due to faulty packaging), that's the whole point of my updating this ancient PKGBUILD :)

Regarding ffmpeg 4.0.2-3: I just rebuilt and reinstalled zoneminder and it worked as before, without any errors or hick-ups. The only difference I could spot is at the end of CMake's configuration step, where in the "Optional libraries not found" list there is a new "AVResample" item added. I did a little digging though and I found that the entire reason for Arch updating the ffmpeg package was to drop support for libavresample. See here: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/ffmpeg&id=a0f9a95b804d34209c88122fe9941179ad584262

So this is probably our culprit. Seeing as it is designated "optional" in ZoneMinder's CMake file, it seems like it isn't an absolutely required component. So, if your setup is broken, I guess that unknowingly to you or not your camera(s) have been making use of video resampling through ffmpeg.

If that's what you really want or need (i.e. for some reason your camera(s) need that specific resampling library to work properly - which I doubt) then maybe you could consider using libvlc instead of ffmpeg, as it's there for precisely that reason - as an optional alternative in case ffmpeg doesn't cover your needs.

If that isn't the case, then maybe you could try fiddling with your camera(s)'s settings and find a way to either change the resampling method or disable the resampling altogether. Sorry for being so vague but as I said, I'm not exactly an expert on ZoneMinder :P

appreciate your work Nocifer, works pretty well mostly. I am having a few problems here or there but overall it is mostly working... just wanted to warn users the ffmpeg 1:4.0.2-3 update yesterday broke zm. so i needed to downgrade.