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.
Search Criteria
Package Details: unifi 8.6.9-1
Package Actions
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)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- java-runtime-headless (jre10AUR, jre12AUR, jdk10AUR, jdk10-openj9-binAUR, jdk7AUR, jre7AUR, amazon-corretto-16AUR, jdk16-adoptopenjdkAUR, jdk8-armAUR, liberica-jre-11-binAUR, jdk11-j9-binAUR, jre11-jbr-xdg-headlessAUR, jre16-openjdk-headlessAUR, jre14-openjdk-headlessAUR, jre15AUR, jre14AUR, jre13AUR, jre16AUR, jre18-openjdk-headlessAUR, amazon-corretto-19-binAUR, liberica-jre-11-full-binAUR, jdk13-openjdk-binAUR, liberica-jre-8-full-binAUR, jre-openj9-headlessAUR, jre12-openjdk-headlessAUR, jdk11-dragonwell-standard-binAUR, jdk11-jetbrains-binAUR, zulu-15-binAUR, jdk20-openj9-binAUR, zulu-13-binAUR, jdk8-dragonwell-extended-binAUR, jdk8-dragonwell-standard-binAUR, jdk11-dragonwell-extended-binAUR, jdk17-dragonwell-standard-binAUR, jre11AUR, jdk8-j9-binAUR, jdk7-j9-binAUR, jdk7r1-j9-binAUR, jre13-openjdk-headlessAUR, jre15-openjdk-headlessAUR, jdk8-openj9-binAUR, jre-ltsAUR, microsoft-openjdk-11-binAUR, microsoft-openjdk-17-binAUR, microsoft-openjdk-21-binAUR, liberica-nik-24-full-binAUR, zulu-17-binAUR, zulu-11-binAUR, zulu-8-binAUR, liberica-jdk-17-full-binAUR, liberica-jdk-11-lite-binAUR, liberica-jdk-11-full-binAUR, liberica-jdk-11-binAUR, jre19-openjdk-headlessAUR, jdk17-jetbrains-binAUR, zulu-jdk-fx-binAUR, zing-21-binAUR, zing-8-binAUR, jre17AUR, java-openjdk-binAUR, jre21-zulu-binAUR, amazon-corretto-17AUR, amazon-corretto-21-binAUR, jre17-zulu-binAUR, jdk21-temurinAUR, amazon-corretto-8AUR, amazon-corretto-11AUR, jdk11-temurinAUR, liberica-jdk-full-binAUR, liberica-jdk-21-full-binAUR, liberica-jdk-8-full-binAUR, jdk17-temurinAUR, zulu-21-binAUR, jdk-temurinAUR, jre8AUR, jdk8AUR, zulu-17-fx-binAUR, jdk8-perfAUR, zulu-jre-fx-binAUR, zulu-fx-binAUR, zulu8-fx-binAUR, zulu11-fx-binAUR, zulu17-fx-binAUR, zulu21-fx-binAUR, jdk-openj9-binAUR, jdk11-openj9-binAUR, jdk17-openj9-binAUR, jre-jetbrainsAUR, jre-openjdk-wakefield-headlessAUR, jre-openjdk-wakefieldAUR, jdk-openjdk-wakefieldAUR, jdk21-openj9-binAUR, zulu-23-binAUR, jreAUR, jdkAUR, jdk21-jetbrains-binAUR, java-openjdk-ea-binAUR, jre-zulu-binAUR, jre-zulu-fx-binAUR, jdk21-dragonwell-standard-binAUR, jdk21-dragonwell-extended-binAUR, jdk-openjdk, jdk11-openjdk, jdk17-openjdk, jdk21-openjdk, jre-openjdk, jre-openjdk-headless, jre11-openjdk, jre11-openjdk-headless, jre17-openjdk, jre17-openjdk-headless, jre21-openjdk, jre21-openjdk-headless, jre8-openjdk-headless)
- mongodbAUR (mongodb32-binAUR, percona-server-mongodb-binAUR, mongodb36-binAUR, mongodb34-binAUR, mongodb40-binAUR, mongodb44-binAUR, mongodb42-binAUR, mongodb60-binAUR, mongodb50-binAUR, mongodb50AUR, ferretdbAUR, mongodb70-binAUR, ferretdb-binAUR, mongodbAUR, mongodb-binAUR, mongodb44AUR)
Required by (0)
Sources (6)
Latest Comments
« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 23 Next › Last »
wget commented on 2019-02-11 00:17 (UTC) (edited on 2019-02-11 00:31 (UTC) by wget)
CountMurphy commented on 2019-02-08 03:36 (UTC)
The current Mongodb package is beyond broken. Can we replace it with mongodb-bin?
tbw commented on 2019-01-20 09:45 (UTC) (edited on 2019-01-20 09:47 (UTC) by tbw)
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
.
phunni commented on 2018-11-04 14:20 (UTC) (edited on 2018-11-04 14:21 (UTC) by phunni)
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 (UTC)
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 (UTC)
@Yamakaky done
Yamakaky commented on 2018-10-04 17:36 (UTC)
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 (UTC) (edited on 2018-09-20 18:36 (UTC) by meokey)
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 (UTC)
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.
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