Package Details: zoneminder 1.36.33-2

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://www.zoneminder.com/
Keywords: camera cctv monitor record security surveillance video zoneminder
Licenses: GPL-2.0-only
Conflicts: zoneminder-git
Submitter: None
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 70
Popularity: 0.33
First Submitted: 2008-03-21 00:09 (UTC)
Last Updated: 2024-02-12 12:50 (UTC)

Latest Comments

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

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.

zazenhei commented on 2022-08-01 05:39 (UTC)

@Nocifer Thank you for your help so far. However, when I run makepkg -si, I get the following error How can I deal with this? [lemon@iex tmp]$ LANG=C makepkg -si ==> ERROR: install file (zoneminder.install) does not exist or is not a regular file.

Nocifer commented on 2022-07-30 08:47 (UTC) (edited on 2022-07-30 08:48 (UTC) by Nocifer)

@zazenhei Sure, just edit the PKGBUILD before or during setup and change pkgver=1.36.21 to pkgver=1.36.19, pkgrel=4 to pkgrel=1, and the first line in the checksums array from 'ca83cf52233db39daabdb13e280da4eff04a428b73e3e1e36f42174cf43c43ed' to 'SKIP' (make sure to keep the quotes).

zazenhei commented on 2022-07-30 04:16 (UTC)

Is there a way to downgrade the software version to 1.36.19-1?

Nocifer commented on 2022-07-29 07:21 (UTC) (edited on 2022-07-29 07:23 (UTC) by Nocifer)

@Synthead Good catch. It was just a useless attempt at PKGBUILD beautification on my part and it ended up biting me in the a$$. I've reverted the source package names to their default upstream names. I've also removed the checksum for RTSP because looking it over I realized that even though it's superficially a zipped archive, in practice it's pulling the latest master (there are no tagged releases) so its contents are subject to change without a moment's notice.

@zazenhei This sounds more like a bug to me; could you please report it to upstream? I can see a recently merged fix about zmc crashing here but I can't tell if it's the same bug affecting you.

zazenhei commented on 2022-07-28 22:18 (UTC)

zmc is not working properly. Jul 29 07:15:30 iex zmdc[180432]: ERR ['zmc -m 1' exited abnormally, exit status 255] Jul 29 07:15:30 iex zmdc[180432]: ERR ['zmc -m 2' exited abnormally, exit status 255] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.4' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.4' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:30 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.4' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.4' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.4' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.4' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex zmtrigger[180513]: ERR [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.] Jul 29 07:15:31 iex systemd[1]: Stopping ZoneMinder CCTV recording and security system...

synthead commented on 2022-07-28 17:38 (UTC)

This is in the source array:

"ZoneMinder.tar.gz::https://github.com/ZoneMinder/zoneminder/archive/refs/tags/${pkgver}.tar.gz"

The ZoneMinder.tar.gz in the beginning of this string specifies a custom file name for this remote. However, if the remote changes (i.e. a new version), makepkg sees that we still have a ZoneMinder.tar.gz file present and does not attempt to update it. Afterward, the sha256sum does not match, and the build fails.

If you want to keep "ZoneMinder" in the file name, you should probably slip the version number in it like this:

"ZoneMinder-${pkgver}.tar.gz::https://github.com/ZoneMinder/zoneminder/archive/refs/tags/${pkgver}.tar.gz"

This way, when a new $pkgver should trigger a new archive download, makepkg will see that the new file name doesn't exist, and it will fetch it as a new file.

Nocifer commented on 2022-07-25 21:24 (UTC) (edited on 2022-07-25 21:33 (UTC) by Nocifer)

@reapster An even better solution would be that the maintainer doesn't forget to properly update the zoneminder-php.ini file, which is provided by the package for this exact reason :P

EDIT: @void09 Maybe you're running more cameras than the multiwatch daemon is configured by default to handle? If so, try to edit the service file and change the /usr/bin/multiwatch -f 10 part to something larger, like 15 or 20.

reapster commented on 2022-07-25 21:12 (UTC)

In case anyone gets the below error (in /var/log/zoneminder/error.log or similar)

2022-07-25 16:52:50 Error: [Error] Class "IntlDateFormatter" not found
Stack Trace:
#0 /usr/share/webapps/zoneminder/www/api/app/Config/bootstrap.php(123): require_once()
#1 /usr/share/webapps/zoneminder/www/api/lib/Cake/Core/Configure.php(98): include('...')
#2 /usr/share/webapps/zoneminder/www/api/lib/Cake/bootstrap.php(442): Configure::bootstrap()
#3 /usr/share/webapps/zoneminder/www/api/app/webroot/index.php(105): include('...')
#4 /usr/share/webapps/zoneminder/www/api/index.php(41): require('...')
#5 {main}

Fix is to just uncomment the line below in /etc/php/php.ini: extension=intl

(And probably make sure php-intl package is installed via pacman/yay)

Otherwise working great, thanks for keeping this package up to date!