[opensuse] Re: Ubiquiti Controller Software for Linux - DEB only?
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
You need a certificate and key and add them in /etc/sysconfig/unifi. Where would I find those? You shall generate your own.
How do I do that? tnx jk
Hi, Am Samstag, 21. November 2020, 03:04:13 CET schrieb James Knott:
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
You need a certificate and key and add them in /etc/sysconfig/unifi.
Where would I find those?
You shall generate your own.
How do I do that?
Whatever you like. You can use pure openssl or one of the many tools built on top of it. I prefer easyrsa. Even letsencrypt will do, but thats designed for public websites and you do not want to make you unifi controller public. I will modify my package so that it's possible to leave certificate of Ubiquiity active. That will give you a security warning and you have to confirm that the browser shall ignore that. Herbert
21.11.2020 12:51, Herbert Graeber пишет:
Hi,
Am Samstag, 21. November 2020, 03:04:13 CET schrieb James Knott:
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
You need a certificate and key and add them in /etc/sysconfig/unifi.
Where would I find those?
You shall generate your own.
How do I do that?
Whatever you like. You can use pure openssl or one of the many tools built on top of it. I prefer easyrsa. Even letsencrypt will do, but thats designed for public websites and you do not want to make you unifi controller public.
It has nothing to do with providing public access to the server. It is about automatically trusting certificate because letsencrypt is trusted by browsers (and any other program that verifies certificate chain). As letsencrypt certificates are issued for a short period of time, renewing them without access to letsencrypt site form the server in question is indeed difficult to automate.
On 2020-11-21 4:51 a.m., Herbert Graeber wrote:
Hi,
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
You need a certificate and key and add them in /etc/sysconfig/unifi. Where would I find those? You shall generate your own. How do I do that? Whatever you like. You can use pure openssl or one of the many tools built on top of it. I prefer easyrsa. Even letsencrypt will do, but thats designed for
Am Samstag, 21. November 2020, 03:04:13 CET schrieb James Knott: public websites and you do not want to make you unifi controller public.
I will modify my package so that it's possible to leave certificate of Ubiquiity active. That will give you a security warning and you have to confirm that the browser shall ignore that.
Herbert _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Can you provide a bit more info on what files go where? For example, I have found /etc/sysconfig/unifi, where I find: ## Path: Network/Unifi ## Description: Unifi controller settings ## Type: string ## Default: "/etc/ssl/servercerts/serverkey.pem" # # Key for TLS encryption UNIFI_TLS_KEY="" ## Type: string ## Default: "/etc/ssl/servercert/servercert.pem" # # Certificate for TLS encryption UNIFI_TLS_CERT="" ## Type: string ## Default: "/etc/pki/trust/anchors/YaST.pem" # # CA Certificate for TLS encryption UNIFI_TLS_CA_CERT="" Using openssl, I created the files in servercert and servercerts, but when I try running the controller, I get an error: * 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 12:21:19 EST; 6min ago Process: 24600 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: 24469 ExecStartPre=/usr/lib/unifi/bin/import-cert (code=exited, status=0/SUCCESS) Main PID: 24600 (code=exited, status=203/EXEC) Nov 23 12:21:17 linux import-cert[24469]: 140674435469760:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76: Nov 23 12:21:17 linux import-cert[24469]: unable to load private key Nov 23 12:21:19 linux import-cert[24469]: Importing keystore /var/tmp/unifi.p12 to /usr/lib/unifi/data/keystore... Nov 23 12:21:19 linux import-cert[24469]: keytool error: java.io.FileNotFoundException: /var/tmp/unifi.p12 (No such file or directory) Nov 23 12:21:19 linux systemd[1]: Started unifi. Nov 23 12:21:19 linux systemd[24600]: unifi.service: Failed to execute command: No such file or directory Nov 23 12:21:19 linux systemd[24600]: 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 Nov 23 12:21:19 linux systemd[1]: unifi.service: Main process exited, code=exited, status=203/EXEC Nov 23 12:21:19 linux systemd[1]: unifi.service: Unit entered failed state. Nov 23 12:21:19 linux systemd[1]: unifi.service: Failed with result 'exit-code'. It's difficult to figure out what's necessary, when working with something you're not familiar with. tnx jk
23.11.2020 20:30, James Knott пишет:
On 2020-11-21 4:51 a.m., Herbert Graeber wrote:
Hi,
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
You need a certificate and key and add them in /etc/sysconfig/unifi. Where would I find those? You shall generate your own. How do I do that? Whatever you like. You can use pure openssl or one of the many tools built on top of it. I prefer easyrsa. Even letsencrypt will do, but thats designed for
Am Samstag, 21. November 2020, 03:04:13 CET schrieb James Knott: public websites and you do not want to make you unifi controller public.
I will modify my package so that it's possible to leave certificate of Ubiquiity active. That will give you a security warning and you have to confirm that the browser shall ignore that.
Herbert _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Can you provide a bit more info on what files go where? For example, I have found /etc/sysconfig/unifi, where I find:
## Path: Network/Unifi ## Description: Unifi controller settings ## Type: string ## Default: "/etc/ssl/servercerts/serverkey.pem" # # Key for TLS encryption UNIFI_TLS_KEY=""
## Type: string ## Default: "/etc/ssl/servercert/servercert.pem" # # Certificate for TLS encryption UNIFI_TLS_CERT=""
## Type: string ## Default: "/etc/pki/trust/anchors/YaST.pem" # # CA Certificate for TLS encryption UNIFI_TLS_CA_CERT=""
Using openssl, I created the files in servercert and servercerts, but when I try running the controller, I get an error:
* 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 12:21:19 EST; 6min ago
Process: 24600 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: 24469 ExecStartPre=/usr/lib/unifi/bin/import-cert (code=exited, status=0/SUCCESS)
Main PID: 24600 (code=exited, status=203/EXEC)
Nov 23 12:21:17 linux import-cert[24469]: 140674435469760:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
Nov 23 12:21:17 linux import-cert[24469]: unable to load private key
You need all three certificates. Or simply remove ExecStartPre and leave default self signed certificate. I do not see how one self signed certificate is better than another self signed certificate.
Nov 23 12:21:19 linux import-cert[24469]: Importing keystore /var/tmp/unifi.p12 to /usr/lib/unifi/data/keystore...
Nov 23 12:21:19 linux import-cert[24469]: keytool error: java.io.FileNotFoundException: /var/tmp/unifi.p12 (No such file or directory)
Nov 23 12:21:19 linux systemd[1]: Started unifi.
Nov 23 12:21:19 linux systemd[24600]: unifi.service: Failed to execute command: No such file or directory
Nov 23 12:21:19 linux systemd[24600]: 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
Nov 23 12:21:19 linux systemd[1]: unifi.service: Main process exited, code=exited, status=203/EXEC
Nov 23 12:21:19 linux systemd[1]: unifi.service: Unit entered failed state.
Nov 23 12:21:19 linux systemd[1]: unifi.service: Failed with result 'exit-code'. It's difficult to figure out what's necessary, when working with something you're not familiar with. tnx jk _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
On 2020-11-23 12:39 p.m., Andrei Borzenkov wrote:
You need all three certificates. Or simply remove ExecStartPre and leave default self signed certificate. I do not see how one self signed certificate is better than another self signed certificate.
Where would I find that ExecStartPre to remove it? I don't see it anywhere I've looked. Also, the defaults did not exist when I started. I created the first two and don't know what's expected for the third. As I mentioned, this sort of thing is quite foreign to me, so I really don't know what to look for.
23.11.2020 20:54, James Knott пишет:
On 2020-11-23 12:39 p.m., Andrei Borzenkov wrote:
You need all three certificates. Or simply remove ExecStartPre and leave default self signed certificate. I do not see how one self signed certificate is better than another self signed certificate.
Where would I find that ExecStartPre to remove it?
In unit definition file.
I don't see it anywhere I've looked. Also, the defaults did not exist when I started.
As you were already told, defaults come with ubiquity controller archive.
I created the first two and don't know what's expected for the third. As I mentioned, this sort of thing is quite foreign to me, so I really don't know what to look for.
There are other users packaging it. They do not force you to use custom certificates. For your convenience: $ osc se unifi
pruning cache pruned 0 files comprised of 0 bytes No matches found for 'unifi' in projects #################################################################### matches for 'unifi' in packages:
# Project # Package home:hgraeber unifi home:jhhudso unifi home:marcelloceschia:ubiquiti unifi home:stefan_van_der_eijk unifi home:worldcitizen unifi home:zawel1:unifi unifi $
On 2020-11-23 1:17 p.m., Andrei Borzenkov wrote:
As you were already told, defaults come with ubiquity controller archive.
I created the first two and don't know what's expected for the third. As I mentioned, this sort of thing is quite foreign to me, so I really don't know what to look for. There are other users packaging it. They do not force you to use custom certificates. For your convenience:
As I mentioned, this is not an area I'm familiar with. This is the first mention of that archive. However, as shown in other posts I am making progress and am past the certificate issue and now the service is failing to start. This is an illustration of what's long been a problem in the *nix world in that there's a general lack of documentation and often combined with "almost works". That can leave people frustrated. Years ago, I used to work for IBM Canada, doing 3rd level support, and part of my job was documentation of my work. I would have a co-worker review what the task was and my documentation of it. Until they were satisfied, I would never release it to the users. I have the background that helps me work through problems that many others would just give up on. However, when I'm walking in cold on something, I may need some help.
On 23/11/2020 18.54, James Knott wrote:
On 2020-11-23 12:39 p.m., Andrei Borzenkov wrote:
You need all three certificates. Or simply remove ExecStartPre and leave default self signed certificate. I do not see how one self signed certificate is better than another self signed certificate.
Where would I find that ExecStartPre to remove it? I don't see it anywhere I've looked. Also, the defaults did not exist when I started. I created the first two and don't know what's expected for the third. As I mentioned, this sort of thing is quite foreign to me, so I really don't know what to look for.
It is plain standard systemd. systemctl --full edit unifi.service But notice that an update to the package may remove your modification, so might want to do an override instead: systemctl edit unifi.service -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
On 2020-11-23 2:09 p.m., Carlos E. R. wrote:
It is plain standard systemd.
Which is fine if you're familiar with it. I'm not. While I may be a more advanced Linux user than most, it's not where my strength is. That would be telecom and networks. In another note, I mentioned about the poor documentation that so often exists in the *nix world, which seems to assume everyone is a developer. Fact is, there are many whose interests lie elsewhere and who only see Linux as a tool and a better OS than the one you're often stuck with when buying a computer. Now, if you want to talk to me about IPv6, Ethernet or WiFi, then I can give you an ear full. ;-)
On 23/11/2020 20.21, James Knott wrote:
On 2020-11-23 2:09 p.m., Carlos E. R. wrote:
It is plain standard systemd.
Which is fine if you're familiar with it. I'm not. While I may be a more advanced Linux user than most, it's not where my strength is. That would be telecom and networks. In another note, I mentioned about the poor documentation that so often exists in the *nix world, which seems to assume everyone is a developer. Fact is, there are many whose interests lie elsewhere and who only see Linux as a tool and a better OS than the one you're often stuck with when buying a computer.
Now, if you want to talk to me about IPv6, Ethernet or WiFi, then I can give you an ear full. ;-)
I know :-) But systemd is documented. It is not as initd, when each service worked differently, there is a common interface. You no longer need to learn a hundred systems. It is even documented by openSUSE! https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-ref... Thus, I know nothing about Ubiquiti, but I know for sure how to access that ExecStartPre. It is the same for all services. Standard :-) And no, I'm very far from being a systemd expert. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
Hi, Am Montag, 23. November 2020, 18:30:06 CET schrieb James Knott:
On 2020-11-21 4:51 a.m., Herbert Graeber wrote:
Hi,
Am Samstag, 21. November 2020, 03:04:13 CET schrieb James Knott:
On 2020-11-20 5:45 p.m., Herbert Graeber wrote:
You need a certificate and key and add them in /etc/sysconfig/unifi.
Where would I find those?
You shall generate your own.
How do I do that?
Whatever you like. You can use pure openssl or one of the many tools built on top of it. I prefer easyrsa. Even letsencrypt will do, but thats designed for public websites and you do not want to make you unifi controller public.>
I will modify my package so that it's possible to leave certificate of Ubiquiity active. That will give you a security warning and you have to confirm that the browser shall ignore that.
Herbert _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Can you provide a bit more info on what files go where?
Some time ago Yast had ist own PKI and pust its certificates and keys in /etc/ssl/servercerts. The CA certifiacte was stored in /etc/pki/trust/anchors/ YaST.pem. That's is the reason I choose the default mentioned in /etc/ sysconfig/unifi. But meanwhile the PKI in Yast has gone. You do net have to use these paths you con set the variables in /etc/sysconfig/ unifi and store the certificates and the key wherever you want.
For example, I have found /etc/sysconfig/unifi, where I find:
## Path: Network/Unifi ## Description: Unifi controller settings ## Type: string ## Default: "/etc/ssl/servercerts/serverkey.pem" # # Key for TLS encryption UNIFI_TLS_KEY=""
## Type: string ## Default: "/etc/ssl/servercert/servercert.pem"
Here a "s" is missing. But only in the comment, not in the import-cert script, which implements the defaults.
# # Certificate for TLS encryption UNIFI_TLS_CERT=""
## Type: string ## Default: "/etc/pki/trust/anchors/YaST.pem" # # CA Certificate for TLS encryption UNIFI_TLS_CA_CERT=""
Using openssl, I created the files in servercert and servercerts, but when I try running the controller, I get an error:
* 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 12:21:19 EST; 6min ago
Process: 24600 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: 24469 ExecStartPre=/usr/lib/unifi/bin/import-cert (code=exited, status=0/SUCCESS)
Main PID: 24600 (code=exited, status=203/EXEC)
Nov 23 12:21:17 linux import-cert[24469]: 140674435469760:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
Nov 23 12:21:17 linux import-cert[24469]: unable to load private key
Looks like /etc/ssl/servercerts/serverkey.pem doesn't exist tor isn't a key in PEM format.
Nov 23 12:21:19 linux import-cert[24469]: Importing keystore /var/tmp/unifi.p12 to /usr/lib/unifi/data/keystore...
Followup error: Unifi expects certificate and key in p12 format, which cannot be generate without the private key .
Nov 23 12:21:19 linux import-cert[24469]: keytool error: java.io.FileNotFoundException: /var/tmp/unifi.p12 (No such file or directory)
Followup error: The p12-File cannot be loaded.
Nov 23 12:21:19 linux systemd[1]: Started unifi.
Nov 23 12:21:19 linux systemd[24600]: unifi.service: Failed to execute command: No such file or directory
Nov 23 12:21:19 linux systemd[24600]: 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
Nov 23 12:21:19 linux systemd[1]: unifi.service: Main process exited, code=exited, status=203/EXEC
Nov 23 12:21:19 linux systemd[1]: unifi.service: Unit entered failed state.
Nov 23 12:21:19 linux systemd[1]: unifi.service: Failed with result 'exit-code'. It's difficult to figure out what's necessary, when working with something you're not familiar with. tnx jk
Herbert
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 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.
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
On 2020-11-24 8:24 a.m., Herbert Graeber wrote:
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.
I have both 8 & 9 headless installed. I'll try removing 9 and see what happens.
On 2020-11-24 9:12 a.m., James Knott wrote:
On 2020-11-24 8:24 a.m., Herbert Graeber wrote:
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.
I have both 8 & 9 headless installed. I'll try removing 9 and see what happens.
Here's the result: * unifi.service - unifi Loaded: loaded (/usr/lib/systemd/system/unifi.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-11-24 09:15:12 EST; 24s ago Process: 10084 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: 10082 ExecStartPre=/usr/lib/unifi/bin/import-cert (code=exited, status=0/SUCCESS) Main PID: 10084 (code=exited, status=203/EXEC) Nov 24 09:15:12 linux systemd[1]: Starting unifi... Nov 24 09:15:12 linux systemd[1]: Started unifi. Nov 24 09:15:12 linux systemd[10084]: unifi.service: Failed to execute command: No such file or directory Nov 24 09:15:12 linux systemd[10084]: 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 Nov 24 09:15:12 linux systemd[1]: unifi.service: Main process exited, code=exited, status=203/EXEC Nov 24 09:15:12 linux systemd[1]: unifi.service: Unit entered failed state. Nov 24 09:15:12 linux systemd[1]: unifi.service: Failed with result 'exit-code'.
On Tue, Nov 24, 2020 at 5:17 PM James Knott
On 2020-11-24 9:12 a.m., James Knott wrote:
On 2020-11-24 8:24 a.m., Herbert Graeber wrote:
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.
I have both 8 & 9 headless installed. I'll try removing 9 and see what happens.
Here's the result:
* unifi.service - unifi
Loaded: loaded (/usr/lib/systemd/system/unifi.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-11-24 09:15:12 EST; 24s ago
Process: 10084 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)
What happens if you execute this command manually?
Process: 10082 ExecStartPre=/usr/lib/unifi/bin/import-cert (code=exited, status=0/SUCCESS)
Main PID: 10084 (code=exited, status=203/EXEC)
Nov 24 09:15:12 linux systemd[1]: Starting unifi...
Nov 24 09:15:12 linux systemd[1]: Started unifi.
Nov 24 09:15:12 linux systemd[10084]: unifi.service: Failed to execute command: No such file or directory
Nov 24 09:15:12 linux systemd[10084]: 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
Is this file present?
Nov 24 09:15:12 linux systemd[1]: unifi.service: Main process exited, code=exited, status=203/EXEC
Nov 24 09:15:12 linux systemd[1]: unifi.service: Unit entered failed state.
Nov 24 09:15:12 linux systemd[1]: unifi.service: Failed with result 'exit-code'. _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
On 2020-11-24 9:12 a.m., James Knott wrote:
On 2020-11-24 8:24 a.m., Herbert Graeber wrote:
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.
I have both 8 & 9 headless installed. I'll try removing 9 and see what happens.
An update for the opensuse version arrived last night and it appears to work. I was in the process of downloading an Ubuntu ISO, to install in a VM, when I noticed the update was available. I guess the threat of installing Ubuntu did the trick! ;-) I no longer have to boot my notebook computer into Windows to configure my AP. Incidentally, it was very easy to copy the configuration file to my Linux system. I just opened a browser on it and connected to the Unifi server running on Windows. From there I was able to just download the backup I just created directly into my download directory. tnx
On 2020-12-06 9:07 a.m., James Knott wrote:
On 2020-11-24 9:12 a.m., James Knott wrote:
On 2020-11-24 8:24 a.m., Herbert Graeber wrote:
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.
I have both 8 & 9 headless installed. I'll try removing 9 and see what happens.
An update for the opensuse version arrived last night and it appears to work.
I was in the process of downloading an Ubuntu ISO, to install in a VM, when I noticed the update was available. I guess the threat of installing Ubuntu did the trick! ;-)
I no longer have to boot my notebook computer into Windows to configure my AP.
Incidentally, it was very easy to copy the configuration file to my Linux system. I just opened a browser on it and connected to the Unifi server running on Windows. From there I was able to just download the backup I just created directly into my download directory.
tnx
Forgot to mention, the repository is located here: https://download.opensuse.org/repositories/home:/hgraeber/openSUSE_Leap_15.2...
24.11.2020 16:24, Herbert Graeber пишет:
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.
jre-headless = 1.8.0 is provided by two packages - java-1_8_0-openjdk-headless and java-1_8_0-openj9-headless. They install into different directories. As long as user is using just /usr/bin/java, likely no difference will be noticed. You probably should use /usr/lib64/jvm/jre-1.8.0/bin/java instead.
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
Herbert Graeber -
James Knott