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.
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.177935 |
| 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)
xamindar commented on 2018-09-10 00:55 (UTC)
rkokk commented on 2018-09-09 18:00 (UTC) (edited on 2018-09-09 18:01 (UTC) by rkokk)
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 (UTC)
@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 (UTC)
@GrayHatter That did the trick - thank you!
GrayHatter commented on 2018-08-16 06:05 (UTC)
I had that issue with postgresql, it's because systemd sucks... reboot and it'll start working again...
k0ste commented on 2018-08-16 00:51 (UTC)
@benoliver999, from what version you upgrade?
benoliver999 commented on 2018-08-15 15:24 (UTC) (edited on 2018-08-15 15:24 (UTC) by benoliver999)
I always get a cold sweat when it's time to upgrade, and sure enough... I'm getting an error again:
unifi.service: Failed to determine user credentials: No such process
unifi.service: Failed at step USER spawning /usr/bin/java: No such process
jonascj commented on 2018-08-02 18:40 (UTC)
In case anyone wonders how to use the package (I did for a few minutes):
-
Start service "systemctl start unifi.service" (optionally enable it "systemctl enable unifi.service").
-
Now the controller software is running, its web gui available at https://localhost:8443
thylacine222 commented on 2018-07-01 04:56 (UTC)
You just need to comment out
rm -r "${pkgdir}/usr/lib/unifi/lib/native"
Or edit it to remove whichever packages are not compiled for your architecture.
Not sure why these are deleted in this PKGBUILD by default.
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