Package Details: zoneminder 1.36.35-1

Git Clone URL: https://aur.archlinux.org/zoneminder.git (read-only, click to copy)
Package Base: zoneminder
Description: A full-featured, open source, state-of-the-art video surveillance software system
Upstream URL: https://zoneminder.com/
Keywords: camera cctv monitor record security surveillance video zoneminder
Licenses: GPL-2.0-only
Submitter: None
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 72
Popularity: 0.24
First Submitted: 2008-03-21 00:09 (UTC)
Last Updated: 2024-10-22 17:14 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 63 Next › Last »

Nocifer commented on 2022-08-17 15:23 (UTC)

@cowboycraig Well, for starters you're actually trying to install zoneminder-git which is a different package. Also, the douche who saw fit to copy-paste my PKGBUILD failed to add the new source URL as HTTPS and thus the connection attempt fails because GitHub refuses plain HTTP connections, and that's why the setup fails for you.

@vectorspacexyz I don't see anything about perl-io-interface in upstream's dependency lists. Do you maybe have an error you could show me that you get when that package is not installed? Also, can anybody else please confirm this as an issue?

@eshep Hmm, weird. Since you said you hadn't bothered digging into this for the past few days, have you by any chance tried your luck with this latest version? The mime.types thing is indeed an issue with the Nginx package, I too was baffled by it having gone missing.

cowboycraig commented on 2022-08-15 02:51 (UTC)

My install fails with this error, any idea why?

╭─craig@cj in ~ took 3ms ╰─λ yay -S zoneminder :: Resolving dependencies... :: There are 2 providers available for zoneminder: :: Repository AUR: 1) zoneminder 2) zoneminder-git Enter a number (default=1): 2

:: Downloading PKGBUILDs... PKGBUILDs up to date nothing new to review fetching devel info... error: timed out looking for devel update: git://github.com/zoneminder/zoneminder.git error: failed to lookup: zoneminder-git: ==> Making package: zoneminder-git 1.33.16.r14355.fd633a217-2 (Sun 14 Aug 2022 07:19:10 PM MST) ==> Retrieving sources... -> Cloning zoneminder git repo... Cloning into bare repository '/home/craig/.cache/paru/clone/zoneminder-git/zoneminder'... fatal: unable to connect to github.com: github.com[0: 140.82.112.3]: errno=Connection timed out

==> ERROR: Failure while downloading zoneminder git repo Aborting... error: failed to download sources for 'zoneminder-git-1.33.16.r14355.fd633a217-2': error: packages failed to build: zoneminder-git-1.33.16.r14355.fd633a217-2

(SEEMS LIKE REPO ISN'T THERE?)

Thanks! cowboycraig

vectorspacexyz commented on 2022-08-11 15:35 (UTC)

perl-io-interface should be added as a dependency for zmonvif-probe.pl to work.

eshep commented on 2022-08-10 09:25 (UTC)

@Nocifer, I do still have this issue. Haven't bothered to continue digging for the past couple days though. I don't see any errors anywhere in the '/var/log/zoneminder/' directory. My nginx zm config is normal/unmodified. The only thing I really had any ""problem"" with post-upgrade was my '/etc/nginx/mime.types' file somehow went missing, added generic default one, nginx back up.

Nocifer commented on 2022-08-10 08:21 (UTC)

Well what do you know, turns out @void09 is absolutely right - reinstalling php-apcu restores access to the API. I'll re-add php-apcu to the package dependencies and report this upstream.

DaMadOne commented on 2022-08-09 23:59 (UTC) (edited on 2022-08-10 00:02 (UTC) by DaMadOne)

I'm also having issues with the API. I had other issues too but those boiled down to having out of date confs. Melding my confs with the .pacnew's got me back up and running. I for the life of me can't figure out the API though. Nothing popping up in journalctl, nginx, zoneminder or cakephp's logs. Could be something upstream but I'm not seeing a bug report on github nor do I know where to start to post one since I can't find anything complaining on my end other than it just not working and getting an http 500 error when trying to do anything with the API.

If anyone figures out why the API isn't working let us know! Thanks for the work you do @Nocifier.

Nocifer commented on 2022-08-08 20:12 (UTC)

@void09 perl-crypt-eksblowfish is already a dependency of this package, so your issue was probably that you hadn't rebuilt it against Perl 5.36. Regarding php-apcu, it was removed as a dependency with the 1.36.20 release. So if the API doesn't work for you, it's either something misconfigured on your end or an upstream issue.

@eshep Weird, I haven't modified anything in the Nginx conf file. Is this still an issue for you? Are you sure all your ZM modules/services are running without any errors?

void09 commented on 2022-08-07 15:29 (UTC) (edited on 2022-08-08 11:04 (UTC) by void09)

After updating to 1.36.24 I could no longer get the zoneminder web to load. I checked zoneminder service status and saw a " zmc_m7[7832]: ERR [zmc_m7] [Config mismatch, expected 225 items, read 221. Try running 'zmupdate.pl -f' to reload config.] Ran zmupdate.pl but it complained about some eksblowish perl cryptolibrary missing. Identified it as perl-crypt-eskblowfish. After its installation I could run that update command and the web was back.

Also noticed I lost zmninja access. I think the api does not work anymore (http://localIP:8095/api)

Later edit: I noticed the apcu php extension got removed from config here: https://aur.archlinux.org/cgit/aur.git/commit/?h=zoneminder&id=ce0f59ac4209ff4a3b98bbe5e6149d41411fb7d4 And I don't see marked as a dependency. Maintainer, can you please add it back ? the API is an essential part of zoneminder, will save a lot of people much wasted time figuring out. Thanks.

eshep commented on 2022-08-06 06:04 (UTC)

Just did an upgrade to 1.36.21-4 and after fixing all the perl module dependencies, I get a "site can’t be reached" message. I'm still getting constant recordings I can see and watch from the "storage" directory but no page is displayed at localhost:8095 as configured in my /etc/nginx/sites-available/zoneminder.conf file. The nginx server seems to be running "fine" with localhost:80 showing the welcome page.

zazenhei commented on 2022-08-02 22:23 (UTC)

@Nocifer Problem solved. Thank you.