Package Details: zoneminder 1.36.5-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://www.zoneminder.com/
Keywords: camera cctv monitor record security surveillance video zoneminder
Licenses: GPL2
Conflicts: zoneminder-git
Submitter: None
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 64
Popularity: 0.136311
First Submitted: 2008-03-21 00:09
Last Updated: 2021-06-23 11:11

Dependencies (43)

Sources (8)

Latest Comments

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

langfingaz commented on 2021-03-28 11:57

@Mike616 Thanks for sharing your steps. I had to downgrade dav1d as well (back to version 0.7.1-1).

Mike616 commented on 2021-03-26 06:40

Okay it looks like zoneminder doesn't yet support the latest release of libx264. Downgrading ffmpeg, libx265, and libx264 to the previous versions solved the problem for me.

Here's how I did this:

Find the previous versions of all three packages:

$ cat /var/log/pacman.log | grep -P "x264|x265|ffmpeg"
[2021-03-25T22:17:19-0700] [ALPM] upgraded x264 (3:0.160.r3011.cde9a93-1 -> 3:0.161.r3039.544c61f-1)
[2021-03-25T22:17:19-0700] [ALPM] upgraded x265 (3.4-1 -> 3.5-1)
[2021-03-25T22:17:19-0700] [ALPM] upgraded ffmpeg (2:4.3.2-2 -> 2:4.3.2-3)

If you haven't cleared your pacman cache, you can install the previous cached versions. You'll have to do all three packages at the same time since they are dependent on each other:

# pacman -U /var/cache/pacman/pkg/{ffmpeg-2:4.3.2-2-x86_64.pkg.tar.zst,x264-3:0.160.r3011.cde9a93-1-x86_64.pkg.tar.zst,x265-3.4-1-x86_64.pkg.tar.zst}

You can tell pacman to ignore updates for these packages for the time being by adding the following to the options section of /etc/pacman.conf:

IgnorePkg   = ffmpeg
IgnorePkg   = x264
IgnorePkg   = x265

After doing this, all my cameras came back to life. Yay because I'm going on vacation tomorrow.

Mike616 commented on 2021-03-26 06:17

@alanking I just ran pacman -Suy and rebooted and now I'm having the same problem. All cameras are red. I can open the web console but cannot stream anything.

ERR ['zmc -m 7' exited abnormally, exit status 127]
ERR ['zma -m 6' exited abnormally, exit status 127]
WAR [ Memory verify failed for Front Door (high)(id:6)]
ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach.  zmc might not be running.]
ERR [Memory map file '/dev/shm/zm.mmap.8' does not exist in zmMemAttach.  zmc might not be running.]

Trying to run zmc or zma directly produces:

zmc: error while loading shared libraries: libx264.so.160: cannot open shared object file: No such file or directory

alanking commented on 2021-03-25 13:40

did this break for anyone else a couple of days ago. all my cameras are red and no longer working. Console still works fine.

ubone commented on 2021-03-16 15:09

http://ix.io/2T3U

error

wuestengecko commented on 2021-03-05 11:23

Git was installed and no user configuration is done.

Yes, that's what I was trying to say. It does fail when simply using makechrootpkg as well, unless you add --no-commit to the mentioned line. When you're building directly on your development host, where you're using git to push to the AUR, then git will find your user config during the build and use that.

I should probably add '--no-commit' to that cherry-pick line by default, yeah?

Yes, please do that.

Nocifer commented on 2021-03-05 11:17

@wuestengecko Ah, that's a new one for me. So then, since this could potentially affect anyone trying to build the package without having set up a git identity (Docker or no Docker), I should probably add '--no-commit' to that cherry-pick line by default, yeah?

raqua commented on 2021-03-05 11:13

@wuestengecko I understand, but .gitconfig is not created on installation of git package. I just tried it in virtual machine. EDIT- I also checked my other machines, it is not there. Git was installed and no user configuration is done. Therefore I believe this will also fail regardless of Docker. Maybe the "--no-commit" clause should be there.

wuestengecko commented on 2021-03-05 11:05

@raqua The issue isn't that your build environment is too dirty, it's precisely the opposite: your environment is too clean. The issue is this line in the PKGBUILD:

git cherry-pick 2fa0fbe448058f2826dadc44572a822af2a177d5

Without --no-commit, git wants to record the cherry-pick in the commit history, and it wants to do so with you as the committer. If you're building in a chroot (or Docker container - same effect), it doesn't know who you are, because why would you set up git in an ephemeral environment.

raqua commented on 2021-03-05 10:51

@Nocifer I am not doing anything dirty. At least I am not aware of it. All I do is

yay -Syy && yay -S pod2man zoneminder cronie apache mariadb 

I am doing it inside Docker container so it is by principle fresh install. I was using the same Dockerfile for months now, there is no change and it was building before. After I added my git contact info it builds.