forum.opsi.org

opsi support forum
https://forum.opsi.org/

Opsi Client Kiosk lässt sich nicht öffnen

https://forum.opsi.org/viewtopic.php?t=9330

Seite 2 von 3

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 14 Dez 2017, 14:21
von n.wenselowski
Hi,

siehst du wohin er die Verbindung macht?
Geht die auf den lokalen Host oder zu einem opsi-Server?


Gruß

Niko

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 14 Dez 2017, 14:31
von Grugi
Hi,

genau das habe ich auch schon gesehen. Leider will er sich mit dem Localhost verbinden. Nur ich habe keine Ahnung wo ich das umstellen kann.

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 14 Dez 2017, 14:39
von n.wenselowski
Hi,

das ist schon korrekt so.

Du musst dann mal im Log des opsiclientd schauen (C:\opsi.org\log).
Da müssten mehr Informationen - hoffentlich ein Traceback - zu dem Fehler zu finden sein.
Falls nicht, kann es sein, dass für den Client das Loglevel des opsiclientd erhöht werden muss.


Gruß

Niko

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 14 Dez 2017, 15:03
von Grugi
Da sieht es so aus.

[6] [Dec 14 15:00:12] [ software on demand ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0437E1D0> started processing (Worker.pyo|251)
[5] [Dec 14 15:00:12] [ software on demand ] New session created (Session.pyo|184)
[6] [Dec 14 15:00:12] [ software on demand ] Starting ServiceConnectionThread, timeout is 5 seconds (OpsiService.pyo|164)
[5] [Dec 14 15:00:12] [ service connection ] Connecting to config server 'https://xxxxxx:4447' #1 (OpsiService.pyo|326)
[3] [Dec 14 15:00:12] [ service connection ] Failed to read version info from file u'/etc/opsi/version': [Errno 2] No such file or directory: u'/etc/opsi/version' (Backend.pyo|206)
[5] [Dec 14 15:00:13] [ service connection ] Disabling mysql backend and license management module: no customer in modules file (JSONRPC.pyo|572)
[6] [Dec 14 15:00:13] [ service connection ] <JSONRPCBackend(host=u'xxxx', deflate=False)>: Connected to service (JSONRPC.pyo|497)
[3] [Dec 14 15:00:13] [ service connection ] Refusing to set deflate because ops service answers with wrong HTTP header contents. (JSONRPC.pyo|424)
[5] [Dec 14 15:00:13] [ service connection ] Connected to config server 'https://xxxxxx:4447' (OpsiService.pyo|355)
[5] [Dec 14 15:00:14] [ opsiclientd ] -----> Executing: getDepotId(u'xxxxx') (JsonRpc.pyo|134)
[6] [Dec 14 15:00:14] [ opsiclientd ] Got result (JsonRpc.pyo|142)
[6] [Dec 14 15:00:15] [ software on demand ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0441C270> started processing (Worker.pyo|251)
[5] [Dec 14 15:00:15] [ software on demand ] New session created (Session.pyo|184)
[6] [Dec 14 15:00:15] [ software on demand ] Starting ServiceConnectionThread, timeout is 5 seconds (OpsiService.pyo|164)
[5] [Dec 14 15:00:15] [ service connection ] Connecting to config server 'https://xxxxx:4447' #1 (OpsiService.pyo|326)
[3] [Dec 14 15:00:15] [ service connection ] Failed to read version info from file u'/etc/opsi/version': [Errno 2] No such file or directory: u'/etc/opsi/version' (Backend.pyo|206)
[5] [Dec 14 15:00:15] [ service connection ] Disabling mysql backend and license management module: no customer in modules file (JSONRPC.pyo|572)
[6] [Dec 14 15:00:15] [ service connection ] <JSONRPCBackend(host=u'xxxxx', deflate=False)>: Connected to service (JSONRPC.pyo|497)
[3] [Dec 14 15:00:15] [ service connection ] Refusing to set deflate because opsi service answers with wrong HTTP header contents. (JSONRPC.pyo|424)
[5] [Dec 14 15:00:15] [ service connection ] Connected to config server 'https://xxxxx' (OpsiService.pyo|355)
[5] [Dec 14 15:00:16] [ opsiclientd ] -----> Executing: getDepotId(u'xxxxxxxxx') (JsonRpc.pyo|134)
[6] [Dec 14 15:00:16] [ opsiclientd ] Got result (JsonRpc.pyo|142)
[6] [Dec 14 15:00:16] [ software on demand ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0291E2F0> started processing (Worker.pyo|251)
[6] [Dec 14 15:00:16] [ software on demand ] Reusing session for client '127.0.0.1', application 'opsi-client-kiosk-4.0.7.11' (Worker.pyo|397)
[6] [Dec 14 15:00:16] [ software on demand ] Starting ServiceConnectionThread, timeout is 5 seconds (OpsiService.pyo|164)
[5] [Dec 14 15:00:16] [ service connection ] Connecting to config server 'https://xxxxx:4447' #1 (OpsiService.pyo|326)
[3] [Dec 14 15:00:16] [ service connection ] Failed to read version info from file u'/etc/opsi/version': [Errno 2] No such file or directory: u'/etc/opsi/version' (Backend.pyo|206)
[5] [Dec 14 15:00:17] [ service connection ] Disabling mysql backend and license management module: no customer in modules file (JSONRPC.pyo|572)
[6] [Dec 14 15:00:17] [ service connection ] <JSONRPCBackend(host=u'opsi.avgsysdo.de', deflate=False)>: Connected to service (JSONRPC.pyo|497)
[3] [Dec 14 15:00:17] [ service connection ] Refusing to set deflate because opsi service answers with wrong HTTP header contents. (JSONRPC.pyo|424)
[5] [Dec 14 15:00:17] [ service connection ] Connected to config server 'https://xxxxx:4447' (OpsiService.pyo|355)
[5] [Dec 14 15:00:17] [ opsiclientd ] -----> Executing: getKioskProductInfosForClient(u'XXXX') (JsonRpc.pyo|134)
[2] [Dec 14 15:00:18] [ event config on_demand{user_logged_in}] Traceback: (Logger.pyo|757)
[2] [Dec 14 15:00:18] [ event config on_demand{user_logged_in}] File "OPSI\Backend\JSONRPC.pyo", line 103, in processResult
(Logger.pyo|757)
[2] [Dec 14 15:00:18] [ event config on_demand{user_logged_in}] ==>>> u"'productVersion' (error on server)" (JSONRPC.pyo|111)
[6] [Dec 14 15:00:18] [ opsiclientd ] Traceback: (Logger.pyo|757)
[6] [Dec 14 15:00:18] [ opsiclientd ] File "OPSI\Service\JsonRpc.pyo", line 140, in execute
(Logger.pyo|757)
[6] [Dec 14 15:00:18] [ opsiclientd ] File "<string>", line 1, in <module>
(Logger.pyo|757)
[6] [Dec 14 15:00:18] [ opsiclientd ] File "<string>", line 1, in getKioskProductInfosForClient
(Logger.pyo|757)
[6] [Dec 14 15:00:18] [ opsiclientd ] File "OPSI\Backend\JSONRPC.pyo", line 679, in _jsonRPC
(Logger.pyo|757)
[6] [Dec 14 15:00:18] [ opsiclientd ] File "OPSI\Backend\JSONRPC.pyo", line 148, in execute
(Logger.pyo|757)
[6] [Dec 14 15:00:18] [ opsiclientd ] File "OPSI\Backend\Backend.pyo", line 148, in waitForResult
(Logger.pyo|757)
[6] [Dec 14 15:00:18] [ opsiclientd ] ==>>> u"'productVersion' (error on server)" (JsonRpc.pyo|145)
[3] [Dec 14 15:00:18] [ opsiclientd ] Execution error: u"'productVersion' (error on server)" (JsonRpc.pyo|146)

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 14 Dez 2017, 17:57
von n.wenselowski
Hi,

danke für den Traceback!

Ich glaube da hast du tatsächlich noch einen Fehler entdeckt. Ich hoffe, dass ich dir morgen eine Fix zukommen lassen kann.


Gruß

Niko

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 15 Dez 2017, 10:28
von n.wenselowski
Hi,

sollte mit python-opsi 4.0.7.52 behoben sein.
Das baut gerade in experimental.
Ich freue mich über Feedback!


Viele Grüße

Niko

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 15 Dez 2017, 12:23
von Grugi
Hallo n.wenselowski,

ich möchte dir sagen dass es nach Installation des neuen Pakets geht. Wunderbar. Vielen dank an dieser Stelle.

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 20 Dez 2017, 12:34
von n.wenselowski
Hi Grugi,
Grugi hat geschrieben:ich möchte dir sagen dass es nach Installation des neuen Pakets geht. Wunderbar. Vielen dank an dieser Stelle.
Danke für die schnelle Rückmeldung!


Viele Grüße

Niko

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 07 Aug 2018, 13:11
von bademeister
Hallo zusammen,

wir bekommen komischerweise seit heute vermehrt die Meldung: Access violoation. (siehe: https://nextcloud.isw.uni-stuttgart.de/ ... ctX2R2dm9j)
Seit gestern haben wir den aktuellen opsi-client-agent drin, ich weiß aber nicht, ob es damit in Zusammenhang steht.

Bei einem Client habe ich auch zeitgleich noch einen Rename gemacht (da unsere Windows-Domäne einen Prefix "isw-" vorschreibt).
Rename: isw-client01.isw.uni-stuttgart.de -> client01.isw.uni-stuttgart.de (existiert im DNS und ist auflösbar)
Ich habe den Client in der lokalen opsiclientd.conf sowie im configed auf den DNS Namen umbenannt.

Trotzdem sehe ich im opsiclientd.log, dass er versucht mit dem alten Namen zu verbinden:

Code: Alles auswählen

[6] [Aug 07 12:59:14] [ service connection            ]      ==>>> Backend configuration error: Failed to get depot server for client 'isw-client01.isw.uni-stuttgart.de'   (JsonRpc.pyo|145)
[3] [Aug 07 12:59:14] [ service connection            ] Execution error: Backend configuration error: Failed to get depot server for client 'isw-client01.isw.uni-stuttgart.de'   (JsonRpc.pyo|146)
[6] [Aug 07 12:59:14] [ software on demand            ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x02BEC0B0> started processing   (Worker.pyo|251)
[6] [Aug 07 12:59:14] [ software on demand            ] Reusing session for client '127.0.0.1', application 'opsi-client-kiosk-4.1.0.0'   (Worker.pyo|397)
[6] [Aug 07 12:59:14] [ software on demand            ] Starting ServiceConnectionThread, timeout is 5 seconds   (OpsiService.pyo|164)
[5] [Aug 07 12:59:14] [ service connection            ] Connecting to config server 'https://opsi.isw.uni-stuttgart.de:4447/rpc' #1   (OpsiService.pyo|326)
[3] [Aug 07 12:59:14] [ service connection            ] Failed to read version info from file u'/etc/opsi/version': [Errno 2] No such file or directory: u'/etc/opsi/version'   (Backend.pyo|206)
[6] [Aug 07 12:59:15] [ service connection            ] Verifying modules file signature   (JSONRPC.pyo|586)
[5] [Aug 07 12:59:15] [ service connection            ] Modules file signature verified (customer: Universitaet Stuttgart, ISW)   (JSONRPC.pyo|611)
[6] [Aug 07 12:59:15] [ service connection            ] <JSONRPCBackend(host=u'opsi.isw.uni-stuttgart.de', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[3] [Aug 07 12:59:16] [ service connection            ] Refusing to set deflate because opsi service answers with wrong HTTP header contents.   (JSONRPC.pyo|424)
[5] [Aug 07 12:59:16] [ service connection            ] Connected to config server 'https://opsi.isw.uni-stuttgart.de:4447/rpc'   (OpsiService.pyo|355)
[5] [Aug 07 12:59:16] [ opsiclientd                   ] -----> Executing: getKioskProductInfosForClient(u'isw-client01.isw.uni-stuttgart.de')   (JsonRpc.pyo|134)
[2] [Aug 07 12:59:16] [ opsiclientd                   ] Traceback:   (Logger.pyo|757)
[2] [Aug 07 12:59:16] [ opsiclientd                   ]   File "OPSI\Backend\JSONRPC.pyo", line 103, in processResult
   (Logger.pyo|757)
[2] [Aug 07 12:59:16] [ opsiclientd                   ]      ==>>> Backend missing data error: Unknown host u'isw-client01.isw.uni-stuttgart.de'   (JSONRPC.pyo|111)
[6] [Aug 07 12:59:16] [ opsiclientd                   ] Traceback:   (Logger.pyo|757)
[6] [Aug 07 12:59:16] [ opsiclientd                   ]   File "OPSI\Service\JsonRpc.pyo", line 140, in execute
   (Logger.pyo|757)
[6] [Aug 07 12:59:16] [ opsiclientd                   ]   File "<string>", line 1, in <module>
   (Logger.pyo|757)
[6] [Aug 07 12:59:16] [ opsiclientd                   ]   File "<string>", line 1, in getKioskProductInfosForClient
   (Logger.pyo|757)
[6] [Aug 07 12:59:16] [ opsiclientd                   ]   File "OPSI\Backend\JSONRPC.pyo", line 679, in _jsonRPC
   (Logger.pyo|757)
[6] [Aug 07 12:59:16] [ opsiclientd                   ]   File "OPSI\Backend\JSONRPC.pyo", line 148, in execute
   (Logger.pyo|757)
[6] [Aug 07 12:59:16] [ opsiclientd                   ]   File "OPSI\Backend\Backend.pyo", line 148, in waitForResult
   (Logger.pyo|757)
[6] [Aug 07 12:59:16] [ opsiclientd                   ]      ==>>> Backend missing data error: Unknown host u'isw-client01.isw.uni-stuttgart.de'   (JsonRpc.pyo|145)
Muss ich den Namen noch irgendwo anpassen?

Viele Grüße,
Felix

Re: Opsi Client Kiosk lässt sich nicht öffnen

Verfasst: 07 Aug 2018, 14:57
von n.wenselowski
Hi,

bitte mal opsiclientd & opsiclientdguard stoppen und dann die opsiclientd.conf checken. Wenn die Daten bei laufendem Client in der Config-Datei geändert werden besteht die Chance, dass sie später vom opsiclientd wieder überschrieben wurden.


Gruß

Niko
Alle Zeiten sind UTC+02:00
Seite 2 von 3

Powered by phpBB® Forum Software © phpBB Limited

Deutsche Übersetzung durch phpBB.de