Package Details: unifi 8.6.9-1

Git Clone URL: https://aur.archlinux.org/unifi.git (read-only, click to copy)
Package Base: unifi
Description: Centralized management system for Ubiquiti UniFi AP
Upstream URL: https://unifi-network.ui.com
Licenses: custom
Conflicts: tomcat-native
Submitter: seblu
Maintainer: freswa
Last Packager: freswa
Votes: 68
Popularity: 0.164122
First Submitted: 2017-08-22 01:31 (UTC)
Last Updated: 2024-11-07 20:46 (UTC)

Dependencies (3)

Required by (0)

Sources (6)

Pinned Comments

freswa commented on 2019-10-30 11:50 (UTC)

We are on Stable with this Package. Please flag out-of-date only if the Version provided with this package does not match the version under "Stable" in this link: https://help.ubnt.com/hc/en-us/articles/360008240754#1

Latest Comments

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

k0ste commented on 2018-03-15 04:10 (UTC)

5.6 -> 5.7:

  1. Download UniFi backup via Settings -> Maintenance.
  2. Stop unifi service and remove unifi package.
  3. Remove /var/lib/unifi
  4. pacman -Syu --ignore jre (we use jre 8).
  5. Install unifi 5.7 package.
  6. Start unifi service and restore backup.
  7. At this step my unifi kill himself. Don't know is normal or not, but after restart my backup is deployed and UniFi works fine.

adamc83 commented on 2018-03-10 03:14 (UTC)

This no longer works with Java 7. I upgraded to jre8-openjdk-headless and everything seems to be working without issue.

xamindar commented on 2018-03-08 23:02 (UTC)

Any plans to update this to 5.7 stable?

amuze commented on 2018-02-04 12:08 (UTC)

Running 4.14.15-1-ARCH

I installed unifi 5.6.30-1 from AUR without any issues.

systemctl status unifi and systemctl status mongodb return the following respectively:

● unifi.service - Ubiquiti UniFi Server Loaded: loaded (/usr/lib/systemd/system/unifi.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2018-02-03 11:28:25 GMT; 10h ago Main PID: 1106 (java) Tasks: 867 (limit: 4915) CGroup: /system.slice/unifi.service └─1106 /usr/bin/java -jar /usr/lib/unifi/lib/ace.jar start

Feb 03 11:28:25 ryzen java[1106]: at org.apache.log4j.LogManager.<clinit>(LogManager.java:127) Feb 03 11:28:25 ryzen java[1106]: at org.apache.log4j.Logger.getLogger(Logger.java:104) Feb 03 11:28:25 ryzen java[1106]: at com.ubnt.service.B.oooo.o00000(Unknown Source) Feb 03 11:28:25 ryzen java[1106]: at com.ubnt.service.B.oooo.<clinit>(Unknown Source) Feb 03 11:28:25 ryzen java[1106]: at com.ubnt.ace.Launcher.<clinit>(Unknown Source) Feb 03 11:28:26 ryzen java[1106]: WARNING: An illegal reflective access operation has occurred Feb 03 11:28:26 ryzen java[1106]: WARNING: Illegal reflective access by org.springframework.cglib.core.ReflectUtils$2 (file:/usr/lib/unifi/lib/spring-core-3.2.8.RELEASE.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.Protecti Feb 03 11:28:26 ryzen java[1106]: WARNING: Please consider reporting this to the maintainers of org.springframework.cglib.core.ReflectUtils$2 Feb 03 11:28:26 ryzen java[1106]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations Feb 03 11:28:26 ryzen java[1106]: WARNING: All illegal access operations will be denied in a future release</clinit></clinit></clinit>

● mongodb.service - High-performance, schema-free document-oriented database Loaded: loaded (/usr/lib/systemd/system/mongodb.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2018-02-03 11:28:25 GMT; 10h ago Main PID: 1105 (mongod) Tasks: 23 (limit: 4915) CGroup: /system.slice/mongodb.service └─1105 /usr/bin/mongod --quiet --config /etc/mongodb.conf

Feb 03 11:28:25 ryzen systemd[1]: Started High-performance, schema-free document-oriented database.

So as far as I can ascertain everything that should be running is up.

However, when attempting to access https://localhost:8443/ I get an invalid certificate message.

If I elect to continue anyway the browser goes into wait mode and that's the end of it.

/opt/unifi/logs is empty /var/log/mongodb/mongod.log contains nothing to indicate any issues.

benoliver999 commented on 2018-02-01 12:32 (UTC)

FWIW I had to do what @xamindar did

Uninstall unfii and deps

rm -r /var/lib/unifi /var/lib/mongodb

Reinstall unifi and deps

start the service

The first screen on the setup page has a restore from backup option which worked well for me.

xamindar commented on 2018-01-30 08:50 (UTC) (edited on 2018-01-30 11:58 (UTC) by xamindar)

After updating to unifi 5.6.30 and then removing the pacman blocks for mongo and a few other related packages and updating everything else.... unifi is broken again. I see mongo running as a process but the unifi web page and app just times out.

EDIT: mongo db is broken. logs show continually exiting with code:62 and this message: "IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details."

I'm pretty sure I was already running 3.4 before when it was working.

EDIT2: Ended up having to do a fresh unifi install and then restore from backup. That got it working on the new mongodb and controller.

yaron commented on 2018-01-28 10:27 (UTC)

The latest version is finally working (5.6.30).

Archanfel80HUN commented on 2018-01-07 12:33 (UTC)

Latest version gave me this at install: :: no results found for mongodb<3.6.0 (dependency tree: unifi mongodb) :: no results found for wiredtiger<=2.9.3 (dependency tree: unifi wiredtiger)