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

For a reason I don't know, the port of the mongodb instance changed without any previous warning from 27117 to 27017. I had to go in /usr/lib/unifi/data/system.properties and change the unifi.db.port property.

The current Mongodb package is beyond broken. Can we replace it with mongodb-bin?

Thanks for packaging this.

Since I had both Java 11 (default) and Java 8 Open JDK installed, I had to change the unifi.service file a little bit, replacing the two /usr/bin/java by usr/lib/jvm/java-8-openjdk/bin/java.

No ideas?

I've tried uninstalling and reinstalling everything. Unfortunately, I can't remember how recently I've made a backup either and there doesn't seem to be a way to make a new backup without starting the unifi manager - which I can't do...

I also tried downgrading everything as suggested elsewhere in these comments, but still couldn't get mongo/unifi started...

I'm only hitting problems with the mongodb update now, quite simply because I haven't got around to it before!

I've tried following the advice below and when I try and run in docker, as advised by Chilloutman I get the following error:

2018-10-31T14:51:46.912+0000 E STORAGE [initandlisten] WiredTiger error (-31802) [1540997506:912201][1:0x7f671c35da00], connection: Version incompatibility detected: unsupported WiredTiger file version: this build requires a maximum version of 2, and the file is version 3: WT_ERROR: non-specific WiredTiger error

I've tried downgrading wiredtiger, but that has no effect (as I half expected). I can't find anything else in the comments specifically about this. I'm hoping that once I get past this, I can follow the other advice and upgrade the db.

@Yamakaky done

Did you consider removing the files in /var? They are auto created by the tmpfiles.d system anyway.

Chilloutman's comment helps me a lot from the DB issue.

prepare docker environment of course; then run Chilloutman's command on one terminal, once it pauses waiting for connection, open another terminal and run command as root:

# mongo 127.0.0.1:27017

> db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } )

> exit

back to the first dock terminal, ctrl-c to kill the process; it should be ready to restart unifi; weird thing for me is that I have to change the ownership of db directory in unifi or the process has no access to the files inside:

2018-09-20T14:06:28.393-0400 I CONTROL [initandlisten] options: { net: { bindIp: "127.0.0.1", port: 27117, unixDomainSocket: { pathPrefix: "/usr/lib/unifi/run" } }, storage: { dbPath: "/usr/lib/unifi/data/db" }, systemLog: { destination: "file", logAppend: true, path: "/usr/lib/unifi/logs/mongod.log" } } 2018-09-20T14:06:28.393-0400 E STORAGE [initandlisten] Unable to read the storage engine metadata file: FileNotOpen: Failed to read metadata from /usr/lib/unifi/data/db/storage.bson 2018-09-20T14:06:28.393-0400 F - [initandlisten] Fatal Assertion 28661 at src/mongo/db/storage/storage_engine_metadata.cpp 91 2018-09-20T14:06:28.393-0400 F - [initandlisten]

$ sudo ls -l /usr/lib/unifi/data/db/storage.bson -rw------- 1 systemd-journal-upload unifi 95 May 3 2017 /usr/lib/unifi/data/db/storage.bson $ sudo chown -R unifi /usr/lib/unifi/data/db

Upgrade tip: you can use docker to launch an older version of mongodb in order to perform the database upgrade:

docker run -v /var/lib/unifi/data/db:/data/db -p 27017:27017 mongo:3.6-jessie

I found this approach easier than downgrading all the necessary libraries.