UniFi controller
http://www.ubnt.com
The UniFi® Software-Defined Networkingplatform is an end-to-end
system of network devices across different loctions all controlled
from a single interface.
-
4
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:hgraeber/unifi && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
README.SUSE | 0000000408 408 Bytes | |
UniFi.unix.zip | 0154692869 148 MB | |
_service | 0000000306 306 Bytes | |
import-cert | 0000001984 1.94 KB | |
mongod-wrapper | 0000000059 59 Bytes | |
sysconfig.unifi | 0000000581 581 Bytes | |
tmpfiles.unifi.conf | 0000000030 30 Bytes | |
unifi-user.conf | 0000000068 68 Bytes | |
unifi.changes | 0000124227 121 KB | |
unifi.conf | 0000000034 34 Bytes | |
unifi.service.in | 0000000507 507 Bytes | |
unifi.spec | 0000006234 6.09 KB | |
unifi.xml | 0000001151 1.12 KB |
Comments 11
any possibility you can help create controller 5.10.23 install for Leap 15.1 ?? or help me learn to build them the way you have ? my company has decided if i can not get unifi controller and video working in to Suse that we will have to part with all the Ubiquiti in the complex here at the Village,, that to me is just a shame,, any help would be appreciated thank you
I cannot really recommend to package a binary this way. Another problem is that Unifi Controller is based on an older version MongoDB not provided anymore. I have found a way around the latter, but it's only a matter of time until it breaks again.
A better way is to use some sort of container, for example docker, which contains all needed components und uses the linux distribution Ubiquity works with, that means Ubuntu. Here a link to a docker image: https://hub.docker.com/r/jacobalberty/unifi
Meanwhile, I updated my package for you... Have fun.
Hello,
I had a problem after installing unifi on OpenSUSE 15.2 ... The service would not start.
The problem was that I couldn't find java java-1.8.0-openjdk-1.8.0
The quick fix was to create a symbolic link to not update the configuration files.
ln -s java-1.8.0-openj9-1.8.0 / java-1.8.0-openjdk-1.8.0
Hello,
To solve the problem of adoption of AP on the internal network.
Must open in the firewall
TCP port https, http, 8080, 8443
UDP port 3478
From this moment on, Unifi finds the devices.
Hello, I've got a problem installing unifi on a new SuSE Leap 15.4. The user unifi and the group won't be created. So the service crashed :( Is it possible to fix this, or is there an older version?
Greetings Torsten
Sorry it's still not functional...
beverly:~ # rpm -Uhv unifi* Preparing... ################################# [100%] Updating / installing... 1:unifi-webrtc-7.3.76-lp154.3.1 ################################# [ 50%] 2:unifi-7.3.76-lp154.3.1 warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root
########################### [100%]
/usr/lib/tmpfiles.d/unifi.conf:1: Failed to resolve user 'unifi': No such process Updating /etc/sysconfig/unifi ...
I hope the creation of group 'unifi' is fixed with the latest build.
Hello, wish a good new year...
sorry still broken:
beverly:~ # journalctl -xeu unifi.service
Jan 07 14:32:33 beverly systemd[1]: Starting unifi...
░░ Subject: A start job for unit unifi.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ ░░ A start job for unit unifi.service has begun execution.
░░ ░░ The job identifier is 1456.
Jan 07 14:32:33 beverly systemd[17753]: unifi.service: Failed to determine user credentials: No such process
Jan 07 14:32:33 beverly systemd[17753]: unifi.service: Failed at step USER spawning /usr/lib/unifi/bin/import-cert: No such process
░░ Subject: Process /usr/lib/unifi/bin/import-cert could not be executed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ ░░ The process /usr/lib/unifi/bin/import-cert could not be executed and failed.
░░ ░░ The error number returned by this process is ERRNO.
Jan 07 14:32:33 beverly systemd[1]: unifi.service: Control process exited, code=exited, status=217/USER
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ ░░ An ExecStartPre= process belonging to unit unifi.service has exited.
░░ ░░ The process' exit code is 'exited' and its exit status is 217.
Jan 07 14:32:33 beverly systemd[1]: unifi.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ ░░ The unit unifi.service has entered the 'failed' state with result 'exit-code'.
Jan 07 14:32:33 beverly systemd[1]: Failed to start unifi.
░░ Subject: A start job for unit unifi.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ ░░ A start job for unit unifi.service has finished with a failure.
░░ ░░ The job identifier is 1456 and the job result is failed.
beverly:~ # systemctl status unifi.service
× unifi.service - unifi
Jan 07 14:32:33 beverly systemd[1]: Starting unifi...
Jan 07 14:32:33 beverly systemd[17753]: unifi.service: Failed to determine user credentials: No such process
Jan 07 14:32:33 beverly systemd[17753]: unifi.service: Failed at step USER spawning /usr/lib/unifi/bin/import-cert: No such process
Jan 07 14:32:33 beverly systemd[1]: unifi.service: Control process exited, code=exited, status=217/USER
Jan 07 14:32:33 beverly systemd[1]: unifi.service: Failed with result 'exit-code'.
Jan 07 14:32:33 beverly systemd[1]: Failed to start unifi.
Meanwhile I have added the openssl dependency to the rpm. I am not sure that this will solve your issue, because it is likely that openssl is already present anyway.
If the problem persists, try if you can execute /usr/lib/unifi/bin/import-cert as root. Your key and certificate must be readable by root only. Access from user and group unifi is not necessary. The key must be accessible without a password, to be copied in Javas password store.
Hello, I did a new clean installation. There is no user unifi in /etc/passwd nor a unifi group in /etc/groups. I started import-cert as root: ./import-cert: No certifcate and/or key specified leave Ubiquities certificate. I do not need a own cert.
Here are the logs: ''... Checking for file conflicts: ..............................................................................................................................................................................................................................................................done Installing: unifi-webrtc-7.3.76-lp154.4.1.x86_64 ....................................................................................................................................................................................................................................[done] warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root warning: user unifi does not exist - using root warning: group unifi does not exist - using root /usr/lib/tmpfiles.d/unifi.conf:1: Failed to resolve user 'unifi': No such process Updating /etc/sysconfig/unifi ... (2/2) Installing: unifi-7.3.76-lp154.4.1.x86_64 ...........................................................................................................................................................................................................................................[done]
beverly:/usr/lib/unifi/bin # systemctl status unifi.service ○ unifi.service - unifi Loaded: loaded (/usr/lib/systemd/system/unifi.service; disabled; vendor preset: disabled) Active: inactive (dead) beverly:/usr/lib/unifi/bin # systemctl start unifi.service
Job for unifi.service failed because the control process exited with error code. See "systemctl status unifi.service" and "journalctl -xeu unifi.service" for details. beverly:/usr/lib/unifi/bin # systemctl status unifi.service × unifi.service - unifi Loaded: loaded (/usr/lib/systemd/system/unifi.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2023-01-20 10:24:49 CET; 15s ago Process: 8517 ExecStartPre=/usr/lib/unifi/bin/import-cert (code=exited, status=217/USER)
Jan 20 10:24:49 beverly systemd[1]: Starting unifi... Jan 20 10:24:49 beverly systemd[8517]: unifi.service: Failed to determine user credentials: No such process Jan 20 10:24:49 beverly systemd[8517]: unifi.service: Failed at step USER spawning /usr/lib/unifi/bin/import-cert: No such process Jan 20 10:24:49 beverly systemd[1]: unifi.service: Control process exited, code=exited, status=217/USER Jan 20 10:24:49 beverly systemd[1]: unifi.service: Failed with result 'exit-code'.
journalctl -xeu unifi.service
Jan 20 10:24:49 beverly systemd[1]: Starting unifi... ░░ Subject: A start job for unit unifi.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit unifi.service has begun execution. ░░ ░░ The job identifier is 49135. Jan 20 10:24:49 beverly systemd[8517]: unifi.service: Failed to determine user credentials: No such process Jan 20 10:24:49 beverly systemd[8517]: unifi.service: Failed at step USER spawning /usr/lib/unifi/bin/import-cert: No such process ░░ Subject: Process /usr/lib/unifi/bin/import-cert could not be executed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The process /usr/lib/unifi/bin/import-cert could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 20 10:24:49 beverly systemd[1]: unifi.service: Control process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ An ExecStartPre= process belonging to unit unifi.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. Jan 20 10:24:49 beverly systemd[1]: unifi.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit unifi.service has entered the 'failed' state with result 'exit-code'. Jan 20 10:24:49 beverly systemd[1]: Failed to start unifi. ░░ Subject: A start job for unit unifi.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit unifi.service has finished with a failure. ░░ ░░ The job identifier is 49135 and the job result is failed.''
Looks like the creation of user and group "unifi" ist still broken. I will setup a virtual machine to test and fix initial installation of the package.
Now everything works fine. Thanks a lot :)