Package Details: unifi-video 3.10.13-1

Git Clone URL: https://aur.archlinux.org/unifi-video.git (read-only, click to copy)
Package Base: unifi-video
Description: Centralized management system for Ubiquiti UniFi surveillance cameras.
Upstream URL: https://www.ubnt.com/
Licenses: custom
Conflicts: unifi-video-beta
Submitter: fryfrog
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 11
Popularity: 0.001840
First Submitted: 2016-04-18 17:44
Last Updated: 2020-10-11 02:45

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

paco3346 commented on 2017-07-18 13:41

No, just the first time. Once the config files are owned by the unifi-video user evostream never reverts them back to root.

What user owns the config files in /usr/lib/unifi-video/conf on Ubuntu?

fryfrog commented on 2017-07-18 03:30

@paco3346: Interesting, I wonder why this works on Ubuntu?

I *can* confirm you have to run their script as root, it complains otherwise. I can add the chown as a patch to the script they run perhaps.

It'd have this problem every time it started up, right?

paco3346 commented on 2017-07-18 03:08

@fryfrog I just installed this on another machine and had the same issue @klden described. The problem is that the evostreams binary is running as root so the first time it launches it creates a bunch of config files in /usr/lib/unifi-video/conf owned by root
Since the jar file runs as unifi-video it can't ever update these files which causes the backend streaming service (Evostream) to never be able to pick up on new camera streams (which is what breaks recording and live streaming).

Workaround: after you start unifi-video the first time run a chown -R unifi-video:unifi-video in /usr/lib/unifi-video/conf

I've not yet tested to see if you can run the systemd unit itself as unifi-video

klden commented on 2017-07-16 14:20

@fryfrog: yep it is from inside haha. I saw the logs from 1 of my camera and it couldn't connect to the unifi-server via port 6666. I'll spin up a ubuntu docker then! :D Thanks for your response!

Update: Your container image is working! Thanks!!

fryfrog commented on 2017-07-15 22:37

@klden: Are you having this issue *inside* your own network when going to the web ui directly? Or outside via port forward or their web portal? If outside, it is probably port forwards. If inside... that was one of the handful of issues I couldn't get sorted which made me spin up an Ubuntu docker instead. :/

klden commented on 2017-07-15 21:42

Hey, any idea why I can't see the live view for my camera? I can however see the jpg images every 1 sec :S

paco3346 commented on 2017-05-04 20:33

It's good to give back. I almost had to give up and just spin up a Ubuntu 16.04 server but reeeaaally wanted to stay with Arch. Love my Arch.

fryfrog commented on 2017-05-04 19:21

Thanks a bunch to *you* for finding the issues. I'm using a docker container, but at some point I'll re-test running it native. :)

paco3346 commented on 2017-05-04 19:05

Ah yes, I see your permissions update in there. I think I probably caused a few things to be owned by root while I was poking around. (I ran a few things as sudo). Thanks for updating!

fryfrog commented on 2017-05-04 05:00

Thanks for poking around, I'll fiddle these changes into the package and see how it turns out.

Edit: Package updated, .patch file added to fix server.xml. And java-runtime>=8 dependency.

I'm not going to do a chown as part of it, that already happens as part of post_install.