Package Details: unifi 5.10.20-1

Git Clone URL: https://aur.archlinux.org/unifi.git (read-only)
Package Base: unifi
Description: Centralized management system for Ubiquiti UniFi AP
Upstream URL: https://community.ubnt.com/unifi
Licenses: custom
Conflicts: tomcat-native
Submitter: seblu
Maintainer: freswa
Last Packager: freswa
Votes: 34
Popularity: 0.937156
First Submitted: 2017-08-22 01:31
Last Updated: 2019-03-14 10:25

Required by (0)

Sources (6)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

puithove commented on 2019-03-14 21:42

FYI - my previous report of having issues with permissions seems to have been caused by my stupidity. yaourt has been unmaintained for a long time, but I hadn't gotten around to switching. I noticed another package that ended up with bad permissions as well. Seems that yaourt has turned bad on me, so I've gotten myself straight on a new helper.

Anyway, just updated to 5.10.20-1 and all is well. Thanks!

Archanfel80HUN commented on 2019-03-14 08:48

Please update to 5.0.19 or 5.0.20 All issue has been resolved in these versions.

puithove commented on 2019-03-11 10:39

the user "unifi" needs to be able to read files in /usr/lib/unifi/lib and execute the mongodb* bins.

644 and 755 are what I ended up in.

Make sure you're removing the packages (thus deleting the files) before re-installing.

If you're using yaourt, try building the packages manually and install via pacman -U

gmask commented on 2019-03-09 14:49

What should the correct permissions be? Upon reinstallation I get the same 640 root:root for /usr/lib/unifi/lib and 740 root:root for mongodb-bin...

puithove commented on 2019-03-08 22:22

Was having the same (Connection refused) error below.

Found bad permissions all over the place apparently from installs of previous package versions. Everything in /usr/lib/unifi/lib was 640 and owned by root:root so unifi user could not access. Completely uninstalled unifi package and re-installed to fix.

Also bad perms on /usr/bin/mongo* which I think was 740 and owned by root:root so again unifi user couldn't run mongodb. Uninstalled package completely and re-installed with mongodb-bin.

Now back up and running.

gmask commented on 2019-03-01 22:01

Getting the same error:

org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)

There is no upgrade problem in my mongod.log. Any ideas?

Rob_H commented on 2019-02-28 20:46

@sulaweyo mongodb-bin "provides" mongodb. So if you install mongodb-bin explicitly, unifi will use it.

sulaweyo commented on 2019-02-28 19:47

As compiling mongodb takes a pretty long time it would be cool if the dependencie could be switched to mongodb-bin. Would save me the edit in the PKGBUILD each time

Rob_H commented on 2019-02-24 22:51

Getting the following error at startup?:

org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)

If so, check your /var/log/unifi/mongod.log for a line like this:

IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.6 before attempting an upgrade to 4.0; see http://dochub.mongodb.org/core/4.0-upgrade-fcv for more details.

Basically, that page instructs you to downgrade to MongoDB 3.6 and run a command in the console to bring the database version to 3.6. Once the database is in that state, you can restart Unifi with the newer MongoDB version and it should work. Fortunately, you don't need to uninstall the MongoDB package to do this, you can just run 3.6 from a temporary directory. Here's a summary of the steps I took, which fixed the problem for me:

  1. Stop Unifi.

  2. Download latest MongoDB 3.6 tarball ("legacy" Linux 64-bit version) from https://www.mongodb.com.

  3. Extract to a local directory.

  4. From the extracted directory, run: sudo -u unifi ./mongod --dbpath /usr/lib/unifi/data/db --port 27117 --unixSocketPrefix /usr/lib/unifi/run --logappend --logpath /usr/lib/unifi/logs/mongod.log --bind_ip 127.0.0.1

  5. From another terminal, run: mongo --shell --port 27117

  6. In the Mongo shell, run: db.adminCommand({setFeatureCompatibilityVersion: "3.6"})

  7. Exit the Mongo shell.

  8. CTRL-C to exit mongod gracefully. The Unifi database should be "upgraded" to 3.6 at this point.

  9. Restart Unifi. It should now upgrade the database automatically to 4.0.

Log in and enjoy!

Archanfel80HUN commented on 2019-02-19 13:57

Got this even if its a fresh install:

AnnotationConfigApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'autoOptimizer' defined in com.ubnt.service.AppContext: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ubnt.service.I.B]: Factory method 'autoOptimizer' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'deviceManager' defined in com.ubnt.service.AppContext: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ubnt.service.oOOO.D]: Factory method 'deviceManager' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eventManager' defined in com.ubnt.service.AppContext: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ubnt.service.private.OoOO]: Factory method 'eventManager' threw exception; nested exception is java.lang.NoClassDefFoundError: javax/activation/DataSource [14:55:57,232] <db-server> INFO db - DbServer stopped