Hi, Am Montag, 23. November 2020, 19:42:15 CET schrieb James Knott:
On 2020-11-23 12:59 p.m., Herbert Graeber wrote:
Here a "s" is missing. But only in the comment, not in the import-cert script, which implements the defaults.
I corrected that error by moving the cert file from servercert to servercerts. I also copied serverkey to YaST-CA.pem (it just says YaST.pem in unifi). Here's how far it gets now:
* unifi.service - unifi
Loaded: loaded (/usr/lib/systemd/system/unifi.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2020-11-23 13:37:18 EST; 24s ago
Process: 1836 ExecStart=/usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/jre/bin/java -Xmx1024M -jar /usr/lib/unifi/lib/ace.jar start (code=exited, status=203/EXEC)
Process: 1834 ExecStartPre=/usr/lib/unifi/bin/import-cert (code=exited, status=0/SUCCESS)
Main PID: 1836 (code=exited, status=203/EXEC)
Nov 23 13:37:18 linux systemd[1]: Starting unifi...
Nov 23 13:37:18 linux systemd[1]: Started unifi.
Nov 23 13:37:18 linux systemd[1836]: unifi.service: Failed to execute command: No such file or directory
Nov 23 13:37:18 linux systemd[1836]: unifi.service: Failed at step EXEC spawning /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/jre/bin/java: No such file or directory
You need package java-1_8_0-openjdk-headless Looks my Requirement of "jre-headless = 1.8.0" is not sufficient. The Unifi controller needs Java8, nothing newer.
Nov 23 13:37:18 linux systemd[1]: unifi.service: Main process exited, code=exited, status=203/EXEC
Nov 23 13:37:18 linux systemd[1]: unifi.service: Unit entered failed state.
Nov 23 13:37:18 linux systemd[1]: unifi.service: Failed with result 'exit-code'.
So, all the keys appear to be loading, but now it's choking on starting the service.
Herbert