| 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.197036 |
| First Submitted: | 2017-08-22 01:31 (UTC) |
| Last Updated: | 2024-11-07 20:46 (UTC) |
Ubiquiti seems to primarily operate off of ui.com -- ubnt.com still resolves but is there a reason to keep using what seems to be the old domain? (The download link works with the ui.com host, I just checked.)
Asking because the mismatch made me spend a paranoid 20 minutes confirming that ubnt.com really was owned and operated by Ubiquiti, since I'd only ever seen ui.com.
tmpfiles can be used to set permissions only. Best to track whatever possible in the package.
I don't really understand systemd tmpfiles, but /var/lib/unifi is created by both the PKGBUILD and unifi.tmpfiles. I think the PKGBUILD line is unnecessary since the directory is empty in the package. The tmpfiles line creates it at the point it is needed and with the correct permissions and ownership.
My system doesn't have a JAVA17EXEC environment variable, so I had to set the path manually.
Just to make it a little easier for those who may not (yet) be proficient with systemd:
After installing "unifi."
Pacman -Q | grep 17-openjdk
If you don't have an OpenJDK Java 17 package already installed, then install ONE of the Java 17 packages: jdk17-openjdk, jre17-openjdk, OR jre17-openjdk-headless.
systemctl enable unifi.service
ls /usr/lib/jvm/java-17*/bin/java
Note the full path to the java excutable (I will refer to this path as $JAVA17EXEC below, but be sure to use the actual path listed by "ls").
sudo systemctl edit --full unifi.service
in the editor that appears, look for the [SERVICE] section and replace the ExecStart and ExecStop lines with:
ExecStart=$JAVA17EXEC --add-opens java.base/java.time=ALL-UNNAMED -jar /usr/lib/unifi/lib/ace.jar start
ExecStop=$JAVA17EXEC -jar /usr/lib/unifi/lib/ace.jar stop
Save the edited file and exit the editor.
systemctl start unifi.service
systemctl status unifi.service
If systemctl reports that "unifi" is running, then you're good to go.
Thanks to killermoehre.
The dependency says 'java-runtime-headless>=17'
Yeah, as far as I can see, upstream says 17 only.
Unifi doesn't support Java 22.
[2024-07-19 14:05:41,555] <launcher> ERROR launcher - Java 22 is not supported!
Please adjust the dependencies.
I am using a fresh install of 8.2.93-1 with mongodb-bin latest version.
I can only get unifi 8.2.93-1 to work with mongodb36 and mongodb40, anything newer than that and the service will just restart over and over forever unable to open the mongodb database.
The link of mongodb is not working atm. Somebody contact with the mantainer of mongodb aur package
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