Arch Linux User Repository

Well, this smells like bad configuration to me, since everything here on my end works almost flawlessly so far (minus some minor buggy hiccups that's upstream's job to fix).

I googled "Unable to send packet at frame resource temporarily unavailable" and what do you know, this turned up:

https://forums.zoneminder.com/viewtopic.php?f=37&t=27065

Someone had the exact same error as you back in March and they fixed it by changing their configuration. Your case might be slightly different than theirs but still, I'm willing to bet there is a 99% chance it's a configuration issue. Did you configure your cameras by following a guide or all by yourself? If the latter, then maybe you should try to find a guide :P

FYI, most IP cameras need to have those FPS limits empty or set to 0 in order to work, ZoneMinder even warns the user when trying to tweak that setting.

Did not fix, it same issue will not display monitor of camera, I have the following errors now. Vlc still streams zms.

zmc_m1      2925    INF Monitor-1: images:1600 - Capturing at 12.50 fps, capturing bandwidth 456609bytes/sec    zm_monitor.cpp  2473

2018-10-02 17:42:45 zmc_m1 2925 ERR Unable to send packet at frame 1551: Resource temporarily unavailable, continuing zm_ffmpeg_camera.cpp 240 2018-10-02 17:42:45 zmc_m1 2925 ERR Unable to send packet at frame 1551: Resource temporarily unavailable, continuing zm_ffmpeg_camera.cpp 240 2018-10-02 17:42:42 zmc_m1 2925 ERR Unable to send packet at frame 1528: Resource temporarily unavailable, continuing zm_ffmpeg_camera.cpp 240 2018-10-02 17:42:42 zmc_m1 2925 ERR Unable to send packet at frame 1528: Resource temporarily unavailable, continuing zm_ffmpeg_camera.cpp 240 2018-10-02 17:42:40 zmc_m1 2925 INF Monitor-1: images:1500 - Capturing at 14.29 fps, capturing bandwidth 522278bytes/sec zm_monitor.cpp 2473 2018-10-02 17:42:39 zms_m1 3063 WAR Unable to send stream frame: Broken pipe zm_monitorstream.cpp 410 2018-10-02 17:42:33 zmc_m1 2925 INF Monitor-1: images:1400 - Capturing at 12.50 fps, capturing bandwidth 451363bytes/sec

Unpinning this because back when I first adopted this package, in the 1.32.x days, a new release usually meant quite a few changes in the PKGBUILD and so this changelog was (hopefully) useful for people to stay informed; but nowadays it's more or less useless and it probably comes across as obnoxious.

Any and all feedback will be much appreciated. Thanks!

CHANGELOG

Update: 1.32.3-1 -> 1.34.0-1

THIS UPDATE CAN BREAK EXISTING SETUPS. For more info check the pinned comment above or the notes in the PKGBUILD.

• Removed hard dependency on Apache, Nginx and MariaDB.
• Moved install logic to a separate script (zmsetup.sh) that can be run manually by the user.
• ZoneMinder's webroot moved from /srv/zoneminder to /usr/share/webapps/zoneminder, as per web application standards.
• Fixes:
  • Changed /var/log/zoneminder permissions from 775 to 755, now logrotate should stop complaining.
  • Changed supported architectures to 'any' for ARM compatibility; if any issues arise, please let me know.
  • Added pod2man as an optional dependency, to support building the package in Docker.

Update: 1.32.2-3 -> 1.32.3-1

• Changed Nginx's configuration so that now it listens on all interfaces instead of only on localhost. This fixes remote access and also prevents some potential conflicts with other conf files that may be present.
• Added proper support for multiserver setups in the install script during updates: now it will properly check whether we're running a local database server or not and will run the updater accordingly. Also added a new function for updating the PTZ control presets.
• Enabled PHP's disabled-by-default semaphore support. This fixes issues like camera playback controls not working and camera device info (e.g. current state, fps, zoom level, et al) not being shown.
• Gave 'zmuser' some new privileges on database 'zm' that are needed to perform the 1.32.3 update.

Update: 1.32.2-2 -> 1.32.2-3

• Added spawn-fcgi & multiwatch as dependencies. Now fcgiwrap will spawn in multiple instances, so ZoneMinder will be able to utilize more than one CGI threads at the same time and thus show concurrent camera streams, which solves issues like having no image while editing zones, etc. The default number of instances is 10, which should be enough for 2 or 3 cameras, but you can of course edit the provided service file and change the number as you see fit. Big thanks to @chapatt for bringing this to my attention!

Update: 1.32.2-1 -> 1.32.2-2

• Included a /zm/ link inside the /www/ folder that points back to /www/. This fixes pretty much every instance of sloppy hardcoded links within ZM's codebase. Big thanks to @Kubax for the idea!

Update: 1.32.1-3 -> 1.32.2-1

NOTE: There's a bunch of small-ish errors in ZM's operation due to some parts of it having the localhost/zm/ link hardcoded and thus breaking when ZM is run from anywhere else, e.g. localhost:8095. I'm in the process of locating these errors and either reporting them upstream or fixing them myself, but I can't know for sure when or even if they'll be fixed. Big thanks to @Kubax for reporting this.

• Changed temp folder location: /var/lib/zoneminder/temp -> /var/tmp/zoneminder
• Fixed /api/app/tmp to correctly point to the temp folder
• Overhauled how the install script makes the choice between Nginx and Apache, as follows:
  • If Nginx is installed and active, regardless of whether Apache is also installed or active or both, we choose Nginx.
  • If Nginx is installed but inactive, and Apache is not installed, we choose Nginx.
  • If Nginx is installed but inactive, and Apache is installed, we choose Apache.
  • If Nginx is not installed, and Apache is installed, we choose Apache.
  • If neither of them is installed, we simply inform the user about it and do nothing.

It's a fairly simple script and I have tested it as much as I can, but things usually find a way to break apart after introducing such... uhm... breaking changes. If things do break for you, please blame me and not the script itself; and also report here what exactly is broken so I can fix it ;)

Update: 1.32.1-2 -> 1.32.1-3

• MariaDB no longer required (for use with remote databases)
• Apache added as an optional dependency and preferred over Nginx if both are installed

Update: 1.32.1-1 -> 1.32.1-2

• Fixed update process (it erroneously required zoneminder.service to be active while updating its database, when it should rather be the opposite)
• Fixed desktop launcher
• Added logrotate support
• Removed 'perl-module-load-conditional' from dependencies as it is already included in core Perl package
• Other minor fixes (e.g. the license file was being installed in the wrong place)

@Nocifer Hey I am the Onion on the Zoneminder forum as you know reinstalling the lib fixed the dev/shm error.

But I still cant see any stream on the monitor in Zonmeinder the ffmeg fix did not help.

I can see the stream from ZMS in VLC but nothing in Zoneminder.

Did you have to change the nginx config file or the zoneminder file in /etc/nginx/sites-enabled?

Turns out it is indeed a bug due to the new ffmpeg (oh what a surprise). The good news is, it's already been fixed upstream and will be included in the upcoming 1.32.1 maintenance release. See here:

https://github.com/ZoneMinder/zoneminder/issues/2184

I already tested it and it works perfectly, no more weird errors and the camera tracks, monitors and records properly.

@whata-mess, would you be willing to try the fix and verify it works for you? I could provide this as a patch in the PKGBUILD but it's a really trivial change, so the fastest way would be for you to do it on your own with a text editor as described in the link above. But if you're not comfortable with editing files tell me and I'll provide a new PKGBUILD.

As for that "something more reliable" you've been asking for: no, as far as I know ZoneMinder is the solution for CCTV on Linux. Why do you think we've all been clamoring and begging for an update for so long? :P

EDIT: Note that this is basically a somewhat hacky workaround and not a proper fix on ZoneMinder's side, so things are still not perfect yet. For example, when adding a brand new camera I got that same error again but only once, then everything worked smoothly with no more errors. So don't be alarmed if you see it just that one time, it's probably during camera initialization that ZoneMinder goes bonkers because the real cause of the bug still exists somewhere in there.

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.