nach dem Update auf opsi 4.1 kann der opsi-configed nicht mehr mittels Java Web Start (javaws) aufgerufen werden. Stattdessen startet javaws, der Progressbar läuft bis 69% und dann hängt das ganze.
Server: Ubuntu 16.04
Client: Linux (Mate) und Windows
Der OPSI Server selbst läuft ohne Probleme. opsi-admin funktioniert, opsi-configed lokal auf dem OPSI Server gestartet funktioniert auch.
Javaws Cache Verzeichnis löschen führt zu keiner Veränderung.
Aufruf mittels "javaws -verbose https://opsi-server:4447/configed.jnlp" zeigt, dass opsi-configed gar nicht gestartet wird (ohne Verbose kommen auch gar keine Ausgaben), sondern er versucht, commons-io.jar und configed.jar zu aktualisieren.
Die gekürzte Ausgabe sieht so aus:
Code: Alles auswählen
...
Connecting https://opsi-server:4447/configed/swingx.jar
Adding sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/swingx.jar
done https://opsi-server:4447/configed/swingx.jar
isCached: remote:193816 cached:193816
isCurrent:isCached true
isCurrent:lastModified cache:1516974000000 actual:1516974000000
isCurrent: https://opsi-server:4447/configed/commons-io.jar = true
Disconnecting sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/commons-io.jar
Removed sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/commons-io.jar
isCached: remote:4896559 cached:3535360
isCurrent:isCached false
isCurrent: https://opsi-server:4447/configed/configed.jar = false
isCached: remote:4896559 cached:3535360
Disconnecting sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/configed.jar
Removed sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/configed.jar
Connecting https://opsi-server:4447/configed/configed.jar
Adding sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/configed.jar
done https://opsi-server:4447/configed/configed.jar
Selecting proxy for: https://opsi-server:4447/configed/configed.jar
Selected proxies: [DIRECT]
isCached: remote:1393958 cached:794624
isCurrent:isCached false
isCurrent: https://opsi-server:4447/configed/swingx.jar = false
isCached: remote:1393958 cached:794624
Disconnecting sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/swingx.jar
Removed sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/swingx.jar
Connecting https://opsi-server:4447/configed/swingx.jar
Adding sun.net.www.protocol.https.DelegateHttpsURLConnection:https://opsi-server:4447/configed/swingx.jar
done https://opsi-server:4447/configed/swingx.jar
Selecting proxy for: https://opsi-server:4447/configed/swingx.jar
Selected proxies: [DIRECT]
Downloading https://opsi-server:4447/configed/configed.jar using https://opsi-server:4447/configed/configed.jar (encoding : null)
Downloading file: https://opsi-server:4447/configed/configed.jar into: /home1/user/.cache/icedtea-web/cache/2/https/opsi-server/configed/configed.jar
isCached: remote:4896559 cached:3535360
isCurrent:isCached false
Downloading https://opsi-server:4447/configed/swingx.jar using https://opsi-server:4447/configed/swingx.jar (encoding : null)
Downloading file: https://opsi-server:4447/configed/swingx.jar into: /home1/user/.cache/icedtea-web/cache/4/https/opsi-server/configed/swingx.jar
isCached: remote:1393958 cached:794624
isCurrent:isCached false
Auf einen anderen (frisch installierten) Testsystem (in einem anderen Netz) funktioniert es. Dort geht es danach wie folgt weiter:
Code: Alles auswählen
...
Jar found at /var/tmp/user/.cache/icedtea-web/cache/2/https/opsi-test-server/configed/configed.jarhas been verified as SIGNED_OK
Jar found at /var/tmp/user/.cache/icedtea-web/cache/4/https/opsi-test-server/configed/swingx.jarhas been verified as SIGNED_OK
Jar found at /var/tmp/user/.cache/icedtea-web/cache/3/https/opsi-test-server/configed/commons-io.jarhas been verified as SIGNED_OK
CN=uib gmbh,O=uib gmbh,STREET=Bonifaziusplatz 1B,L=Mainz,ST=Rheinland-Pfalz,C=DE,1.3.6.1.4.1.311.60.2.1.1=#13054d61696e7a,1.3.6.1.4.1.311.60.2.1.2=#130f526865696e6c616e642d5066616c7a,1.3.6.1.4.1.311.60.2.1.3=#13024445,2.5.4.5=#13084852422036393432,2.5.4.15=#0c1450726976617465204f7267616e697a6174696f6e in cacerts gefunden (/home/user/.config/icedtea-web/security/trusted.certs)
CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3 in cacerts gefunden (/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/security/cacerts)
App already has trusted publisher: true
App already has trusted publisher: true
Ending check for signed JNLP file...
App already has trusted publisher: true
App already has trusted publisher: true
Trusted Only manifest attribute not found. Continuing.
Die Codebasis stimmt mit der Codebasis im Manifest überein und die Anwendung ist signiert. Fahre fort. Um Einzelheiten zu erfahren siehe: http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/security/no_redeploy.html.
Found alaca URLs to be verified
- https://opsi-test-server:4447/configed
- https://opsi-test-server:4447
...
Meine Frage:
* gibt es Leute, die ein ähnliches Problem hatten, speziell nach dem Update auf opsi 4.1?
gruss,
Jörg Steffens