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)

Dependencies (45)

Sources (8)

Latest Comments

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 63 Next › Last »

jlanzobr commented on 2019-12-02 20:54 (UTC)

Note: ZoneMiner is broken on PHP 7.4. Do not upgrade php or related packages. Add IgnorePkg = php-gd php-fpm php-sodium php-intl php php-apache in /etc/pacman.conf. Use downgrade (AUR package) to downgrade if you accidentally updated in a recent pacman -Syu.

Nocifer commented on 2019-11-26 09:25 (UTC)

@compgamer89 yes, /var/log/zoneminder should indeed be set to 755 instead of the current 775. I've already fixed this ages ago on my side but I've been waiting for the next upstream release of ZM before I upload the fixed PKGBUILD, because I didn't want to force people to do a reinstall for something so small and easily fixable by hand. Though of course, ZM not having had a new upstream release in almost a year has complicated things a wee bit...

compgamer89 commented on 2019-11-25 23:53 (UTC)

Does the package need to set 775 permissions on /var/ directories? Getting this error with logrotate:

● logrotate.service - Rotate log files
   Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-11-25 00:00:04 PST; 15h ago
     Docs: man:logrotate(8)
           man:logrotate.conf(5)
  Process: 3626 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
 Main PID: 3626 (code=exited, status=1/FAILURE)

Nov 25 00:00:04 <server> systemd[1]: Starting Rotate log files...
Nov 25 00:00:04 <server> logrotate[3626]: error: skipping "/var/log/zoneminder/cake_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Nov 25 00:00:04 <server> logrotate[3626]: error: skipping "/var/log/zoneminder/error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Nov 25 00:00:04 <server> logrotate[3626]: error: skipping "/var/log/zoneminder/http_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Nov 25 00:00:04 <server> logrotate[3626]: error: skipping "/var/log/zoneminder/http_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Nov 25 00:00:04 <server> systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Nov 25 00:00:04 <server> systemd[1]: logrotate.service: Failed with result 'exit-code'.
Nov 25 00:00:04 <server> systemd[1]: Failed to start Rotate log files.

ultimategrandson commented on 2019-08-25 22:57 (UTC)

@Nocifer My intention is to put the DB on a different server. So I'll experiment with modifying the makepkg script and see how it goes. Happy to try out the build if you enable ARM on the package. Thanks.

Nocifer commented on 2019-08-25 20:04 (UTC)

@ultimategrandson A MySQL-compatible database is needed for ZoneMinder to work properly (PostgreSQL for example is not compatible if memory serves) but it's not a hard requirement to install it on the same machine as ZoneMinder (it could be installed on another server and accessed remotely) nor is it necessary to specifically use MariaDB (MySQL itself for example is perfectly compatible).

If for whatever reason you need to remove MariaDB as a dependency, then you'll need to edit the PKGBUILD and delete or comment out line 63. The same goes for Nginx by the way: if you don't need it you can delete or comment out line 60. The install script is supposed to understand when MariaDB and/or Nginx are missing and act accordingly, but of course your mileage may vary, so keep in mind that things may indeed break at some point or another. It goes without saying of course that if they do break, your feedback about what happened would be most welcome :)

Regarding ARM compatibility: last year it was reported by some other user that one of the required Perl packages could not be built on ARM, but I don't have an ARM system myself so I just took them on their word. But if you say you built it successfully, then that probably means we can now safely include ARM as compatible, so I'll do so on the next update. And if there are any bumps along the road (e.g. ZoneMinder building on ARM but then not working properly during runtime) I guess this will be a good way to encounter them and maybe even fix them.

ultimategrandson commented on 2019-08-25 02:03 (UTC)

Using Yay (and ignoring the arch warnings), I actually installed this package on Archlinux ARM (Raspberry Pi 2) and it works perfectly, this actually worked better than the Rapbian package, at least in my experience, as the zmNinja app worked out of the box.

I'm a bit of a noob but; the dependencies that are installed; are they all really required to run Zoneminder or are they just required to build it? I understand ffmpeg, etc are necessary but could MariaDB be made optional? Or is there a way to exclude certain packages when I install?

ImNtReal commented on 2019-08-07 17:19 (UTC)

Ok. I can handle it that way. It's a bit confusing to me why they didn't just include all defaults in /etc/zoneminder/zm.conf, and only use the conf.d directory for user overrides.

Nocifer commented on 2019-08-06 05:51 (UTC)

@ImNtReal well, I could, but perhaps it would be simpler if you just made a new conf file inside /etc/zoneminder/conf.d and named it e.g. 03-custom.conf and used that one to override the stuff in 01-system-paths.conf? The reason for that is that 01-system-paths.conf is not supposed to contain any user adjustments, it even says so on the tin:

# *** DO NOT EDIT THIS FILE ***
#
# To make custom changes to the variables below, create a new configuration
# file, with an extention of .conf, containing your desired modifications.

Not that it matters much, if you ask me, but perhaps there is some valid reason for this warning, related to how ZM works internally. Anyway, if you really find it that much of a bother, I guess it won't hurt to add 01-system-paths.conf to the backup array when I next update the package and leave it up to the user. But I must warn you, judging by the ZM upstream's very slow progress as of late, this next update could be tomorrow or it could be next year :)

ImNtReal commented on 2019-08-05 18:14 (UTC)

Could you add etc/zoneminder/conf.d/01-system-paths.conf to the backup array, so my changes don't get wiped when I update?

zombielinux commented on 2019-06-13 11:49 (UTC)

That's what did it. Seems to be online now.

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 63 Next › Last »