Arch Linux User Repository

there seems to be another upstream error.

when zoneminder.install calles /usr/bin/zmupdate.pl it get's stuck in a loop with this error.

Please press 'y' for a backup or 'n' to continue only : Use of uninitialized value $response in scalar chomp at /usr/bin/zmupdate.pl line 376.
Use of uninitialized value $response in pattern match (m//) at /usr/bin/zmupdate.pl line 376.

changing this line from

376:       $response = <STDIN>;

to

376:       my $response = <STDIN>;

fixes this.

Totaly forgot... thanks for this aur. It would have been a realy hard way of installing zoneminder, just to figure out wich cat is using our couch instead of the cat litter -.-

@dimytch

If I'm not mistaken, this error must have happened after you'd already built the package. So did it build correctly after all, or not? If not, then since multiwatch is an AUR package, try adding armv7 to the list of supported architectures in the PKGBUILD and then try to build the package again.

If it will still not build, I will try to find an alternative for it.

And no, unfortunately I don't have a Pi or any other SBC on which to test this PKGBUILD.

After perl xs, there's no package 'multiwatch' for armv7. Nobody does not use zoneminder with raspberrypi?

(1/1) Arming ConditionNeedsUpdate...
==> ОШИБКА: Пакета 'multiwatch' нет для архитектуры 'armv7h'.
==> ОШИБКА: Makepkg не смог собрать multiwatch.

@dimytch

Hmm, bummer. I'd think all Perl modules can build properly under armv7, so maybe this is an omission by the package maintainer - but you'd have to contact them to know for sure.

There is something else you could do though: this package is only installed as a dependency for perl-json-maybexs, which is itself only installed because apparently it's needed for ZM's Telemetry module. The key word here is "apparently" - I still haven't managed to find enough time to compile ZM without it and test if it is indeed needed or not.

So: you could remove it from the dependencies list, build without it, enable Telemetry in ZM and report back here whether there are any errors in ZM's logs produced by zmtelemetry.pl.

The perfect solution! (at least for me :P)

Well, I'll be effing damned..! @chapatt, I don't know if you've read that comment I posted earlier (I've actually pinned it) about a nasty bug I was out hunting all morning? Well, turns out it's not a bug after all - the erroneous URL I've been seeing is just a useless Ajax call of no concern whose only downside is that it consumes CPU cycles for no good reason; I guess it's just a remnant from older ZoneMinder versions that no one ever bothered to remove.

That missing camera stream in the Edit Zone view though, which I thought was the result of this "bug"? Yeah, turns out that's because the camera stream used in the Edit Zone view is (obviously..!) the same as the one used in the View Zone view, which is still active while editing one of the zones; and it's also the same stream used in the Monitor view, which is why I had no image in the otherwise perfectly working Monitor view while viewing or editing the zones! And here I was, chasing bugs and butterflies, when it was simply a matter of that damn fcgiwrap process blocking requests when receiving more than one at the same time!

/facepalm

The good news is that spawn-fcgi + multiwatch solved the issue completely, and now I can have the camera feed streaming through all 3 views at the same time. So, many thanks for mentioning them ;)

The "bad" news is that now spawn-fcgi and multiwatch have been promoted to mandatory dependencies (when using nginx+fcgiwrap) because without them ZM cannot function properly, which means a simple note at the end of the install procedure or an edit in the Arch wiki entry will simply not cut it. I will add them in the next update, and will also add a new systemd service that will be used instead of the fcgiwrap one.

Thanks again!

@Nocifer, yes, that's the one--you need at least as many fcgiwrap threads as you want to view streams. Well, the wiki is mostly just a guide on how to configure the aur package, so it seems apt to at least augment it with a mention of the other optional dependencies, etc. available. I'll try to get around to it too, once the package and my system are stable.

The 1.32.2-1 update broke ZoneMinder's cgi scripts because my "elegant" dirty fix for the hardcoded links, mentioned in the other pinned comment, turned out to not be a fix after all. I instead tried the hack that @Kubax described (creating a /zm/ link inside the /www/ folder that points back to /www/) and that one managed to fix pretty much all errors with hardcoded links, to the point that upstream may not even have to bother.

The 1.32.2-2 update I just pushed contains that fix.

Besides that, I've been trying to eliminate a particularly nasty bug that results in a specific request constructing a false URL like http://localhost/index.php/index.php?view=request&request=stream&connkey=752041&command=99, which fails for obvious reasons. This URL is the one that loads the camera image when editing zones, so I'd say it's important enough to warranty immediate attention.

As soon as I manage to find a solution I'll push a final, third update.

@chapatt

Hey, and thanks. Regarding fcgiwrap, I guess you mean this tweak in particular?

https://wiki.archlinux.org/index.php/nginx#Multiple_worker_threads

I don't know if I'll ever get to edit the Arch wiki itself (you think I should?) but at the very least we could have the install script print a note about this at the end of the install procedure, alongside the "ZoneMinder is listening at localhost:8095" message.

@Nocifer thanks again for keeping up the effort with this! I got around to actually using the installation and had to go through a little fcgiwrap configuration in order to view multiple streams simultaneously (or on multiple clients). See https://wiki.archlinux.org/index.php/nginx#CGI_implementation. If you overhaul the wiki page for your package you might want to reference it in a section regarding nginx.