Package Details: unifi 5.9.29-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: 31
Popularity: 1.395282
First Submitted: 2017-08-22 01:31
Last Updated: 2018-10-05 12:11

Latest Comments

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

phunni commented on 2018-11-04 14:20

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...

phunni commented on 2018-10-31 14:55

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.

freswa commented on 2018-10-05 12:26

@Yamakaky done

Yamakaky commented on 2018-10-04 17:36

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

meokey commented on 2018-09-20 18:29

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

Chilloutman commented on 2018-09-12 20:33

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.

xamindar commented on 2018-09-10 00:55

rkokk the mongodb 4.0 update was out months ago. How are you just now running across this problem? In any case, read through this thread as it was discussed a while back.

In my case, I had to restore a backup to get it working again.

rkokk commented on 2018-09-09 18:00

I have an issue with the fact that mongodb has upgraded in the repo to 4.0. Even downgrading the package to 3.6/3.4 does not resolve the following error. Which results in the mongodb rebooting continuesly. Any ideas how to fix this? I'm only using mongo for Unifi.

** 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.

wget commented on 2018-08-27 18:39

@thylacine222 thanks a lot for your comment this worked. For others, to see whether you are concerned by an Arch Linux ARM aarch64 variant, simply type uname -m. This should give you aarch64 if you are running an ARM 64 compatible build. Otherwise you might end up with armv7 simply printed.

benoliver999 commented on 2018-08-16 07:38

@GrayHatter That did the trick - thank you!