Package Details: unifi-video 3.9.11-1

Git Clone URL: https://aur.archlinux.org/unifi-video.git (read-only)
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: 7
Popularity: 0.016837
First Submitted: 2016-04-18 17:44
Last Updated: 2018-11-06 04:18

Latest Comments

1 2 3 4 Next › Last »

mgb0 commented on 2018-10-06 05:55

@fryfrog I just set this up and had to use @mohaine's script to get mongodb to start

Another issue I had was the missing /usr/lib/unifi-video/data directory. The unifi-video service wouldn't start until I manually created the data subdir and changed the ownership to unifi-video

fryfrog commented on 2018-02-07 04:54

@mohaine, what is trying to start mongodb w/ the --nohttpinterface option? Nothing shows up when I grep -ir -- "--nohttpinterface" the sources.

Edit: It must be something inside the java files. :/

sdkyuzo commented on 2018-02-07 04:24

Thanks mohaine for the fix. New to unifi-video, arch is my preferred distro. Couldn't get it running because of mongod startup errors, your script fixed the issue. Thanks for commenting on a fix for the rest of us to find and use!

mohaine commented on 2017-12-30 16:52

after doing a system update, unifi refused to get past the "Processing update" page. It seems that mongo will not start due to an unknown cmd line argument.

I replaced the mongod sym link (/usr/lib/unifi-video/bin/mongod) with the following bash script to remove the argument and all is well.

#!/bin/bash

args=$@
delete=('--nohttpinterface')
clean=${args[@]/$delete}
exec '/usr/bin/mongod' $clean

fryfrog commented on 2017-09-20 22:05

Heads up, 3.8.0 adds a new port. If you're doing anything tricky, you'll need 7442 as well as the old 7443. A symptom I saw from this was that the cameras would connect after the update, do their firmware update and then never re-appear.

klden commented on 2017-07-23 04:30

@fryfrog @paco3346

chowning the config folder does fix the problem for the live view! Thanks for finding this out!

fryfrog commented on 2017-07-18 15:43

@paco3346: Sorry for not updating, I also help w/ the docker version and did that way back when 3.7.1 came out. Should have done this one too. :/

I checked inside my docker and that dir is all unifi-video:unifi-video.

I'll add a chown to the packages install/update and it'll "fix" it every install/upgrade at least. Or maybe it should be a pre-run in the systemd unit file? :/

paco3346 commented on 2017-07-18 13:43

Also, 3.7.1 has been out for a while https://community.ubnt.com/t5/UniFi-Video-Blog/UniFi-Video-3-7-1-Release/ba-p/1947714

I've had no issues simply swapping out the version number and updating the sha256 hash.

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?