Arch Linux User Repository

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

Part of the problem is "net.http" option specified in the config file.

I tried running the DB manually and it worked for a while, after several seconds it crashes and I can't figure out why (the log didn't help as I expected).

From what I can tell the main problem is the mongod parameter "--nohttpinterface" which was deprecated before and was removed with MongoDB 3.6, see link.

In our case the mongod process just exits with an error because unifi still invokes MongoDB as shown below:

bin/mongod --dbpath /usr/lib/unifi/data/db --port 27117 --unixSocketPrefix /usr/lib/unifi/run --logappend --logpath /usr/lib/unifi/logs/mongod.log --nohttpinterface --bind_ip 127.0.0.1

My workaround was to replace the mongod link in /usr/lib/unifi/bin with the following tiny script which just removes the now unsupported parameter:

#!/bin/bash  
exec /usr/bin/mongod ${*//--nohttpinterface/}

Strange enough I still had to restart unifi a couple of times after the above change and had to start the mongod process manually once (as unifi:unifi user/group) before MongoDB was willing to cooperate with unifi. But now it works without problems (until the next unifi update where I will have to redo the change).

+1, @mellofone & @abra

downgraded both and it works now. Cheers guys, never would have been able to get this working with out you guys!

mellofone

+1, mongodb update breaks unifi, although downgrading mongodb to 3.4.9-1 didn't help. Fixed it by downgrading wiredtiger to version 2.9.3-1 (current version was 2.9.3.20171205-2).

Anyone else having a problem getting this running after a mongodb update to 3.6.x? Starting the unifi service properly starts, but the mongod process itself never actually starts. Downgrading mongodb to 3.4.9-1 seems to solve it.

Unfortunately, it doesn't work for Cloud Access (it gives you the access to your controller via https://unifi.ubnt.com). If you log in to unifi.ubnt.com and try to launch your local controller "using cloud", you get an error. Here's a part of the log file you are prompted to download: }, { "0": "WEBRTC_SDP_REQUESTING" }, { "0": "WEBRTC_SDP_RECEIVING_ERROR", "1": { "error_code": "JNI library is not loaded" } }, { "0": "WEBRTC_CONNECTION_ERROR", "1": { "error_code": "JNI library is not loaded" } },

As much as I understand, there are some dependencies that are missing.

Cloud access works on my Debian host flawlessly. It would be great if you could make it work on Arch too.

To get it to start and not complain about a missing javax/activation/DataSource I had to change the .service file to:

ExecStart=/usr/bin/java --add-modules java.activation -jar /usr/lib/unifi/lib/ace.jar start

@mal, @sublu in arch team - he used the force.

Ah, you're right, I misunderstood this bit of the wiki: "If you initially forgot to commit the .SRCINFO and added it in a later commit, the AUR will still reject your pushes because the .SRCINFO must exist for every commit."

@mal, commit should not be rejected. This case - just human mistake.