Opsi Windows Client installiert nur beim hochfahren / On demand nicht aber beim Interval check

Antworten
juergensb
Beiträge: 6
Registriert: 15 Nov 2017, 16:32

Opsi Windows Client installiert nur beim hochfahren / On demand nicht aber beim Interval check

Beitrag von juergensb »

Hallo lieber Community,

bein ein absoluter Opsi Neuling weswegen es hoffentlich nur eine Kleinigkeit ist.

Habe einen Opsi Server (4.0.7.45) auf einem Ubuntu 14.04 laufen.
Die Installation eines Windows 10x64 Client funktioniert ohne Probleme, auch das erstmalige installieren von Software.
Auch wenn ich "On Demand" etwas installieren lasse, öffnet sich der Opsi Client und installiert.

Wenn ich aber einfach nur ein Programm auf Setup stelle wird die Software nicht installiert.
Der Opsi Client meldet zwar auf dem Rechner: opsi: Anstehende Installationen - aber nichts passiert.

Hat jemand ne Idee, warum alles funktioniert außer die "Intervall-Installation"?

Folgendes steht in der opsiclient.log:

Code: Alles auswählen

[5] [Nov 15 16:21:39] [ opsiclientd                   ] Session 'lpPPcdB6mmMQKuCOcJggJ0HSMXsfFgzr' from ip '127.0.0.1', application 'opsi-client-systray-4.0.7.2' expired after 120 seconds   (Session.pyo|190)
[6] [Nov 15 16:21:39] [ opsiclientd                   ] Session timer <_Timer(Thread-993, started daemon 6500)> canceled   (Session.pyo|128)
[5] [Nov 15 16:21:39] [ opsiclientd                   ] Session 'lpPPcdB6mmMQKuCOcJggJ0HSMXsfFgzr' from ip '127.0.0.1', application 'opsi-client-systray-4.0.7.2' deleted   (Session.pyo|225)
[6] [Nov 15 16:24:33] [ software on demand            ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0D1D0630> started processing   (Worker.pyo|251)
[5] [Nov 15 16:24:33] [ software on demand            ] New session created   (Session.pyo|184)
[6] [Nov 15 16:24:34] [ software on demand            ] Starting ServiceConnectionThread, timeout is 30 seconds   (OpsiService.pyo|164)
[5] [Nov 15 16:24:34] [ service connection            ] Connecting to config server 'https://192.168.192.51:4447/rpc' #1   (OpsiService.pyo|326)
[3] [Nov 15 16:24:34] [ 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] [Nov 15 16:24:34] [ service connection            ] Disabling mysql backend and license management module: no customer in modules file   (JSONRPC.pyo|572)
[6] [Nov 15 16:24:34] [ service connection            ] <JSONRPCBackend(host=u'192.168.192.51', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[3] [Nov 15 16:24:34] [ service connection            ] Refusing to set deflate because opsi service answers with wrong HTTP header contents.   (JSONRPC.pyo|424)
[5] [Nov 15 16:24:34] [ service connection            ] Connected to config server 'https://192.168.192.51:4447/rpc'   (OpsiService.pyo|355)
[5] [Nov 15 16:24:35] [ opsiclientd                   ] -----> Executing: getDepotId(u'n29255h2.kmf.lan')   (JsonRpc.pyo|134)
[6] [Nov 15 16:24:35] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[6] [Nov 15 16:24:35] [ software on demand            ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0D128910> started processing   (Worker.pyo|251)
[6] [Nov 15 16:24:35] [ software on demand            ] Reusing session for client '127.0.0.1', application 'opsi-client-systray-4.0.7.2'   (Worker.pyo|397)
[6] [Nov 15 16:24:35] [ software on demand            ] Starting ServiceConnectionThread, timeout is 30 seconds   (OpsiService.pyo|164)
[5] [Nov 15 16:24:35] [ service connection            ] Connecting to config server 'https://192.168.192.51:4447/rpc' #1   (OpsiService.pyo|326)
[3] [Nov 15 16:24:35] [ 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] [Nov 15 16:24:35] [ service connection            ] Disabling mysql backend and license management module: no customer in modules file   (JSONRPC.pyo|572)
[6] [Nov 15 16:24:35] [ service connection            ] <JSONRPCBackend(host=u'192.168.192.51', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[3] [Nov 15 16:24:35] [ service connection            ] Refusing to set deflate because opsi service answers with wrong HTTP header contents.   (JSONRPC.pyo|424)
[5] [Nov 15 16:24:35] [ service connection            ] Connected to config server 'https://192.168.192.51:4447/rpc'   (OpsiService.pyo|355)
[6] [Nov 15 16:24:36] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[6] [Nov 15 16:24:36] [ software on demand            ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0D378B70> started processing   (Worker.pyo|251)
[6] [Nov 15 16:24:36] [ software on demand            ] Reusing session for client '127.0.0.1', application 'opsi-client-systray-4.0.7.2'   (Worker.pyo|397)
[6] [Nov 15 16:24:36] [ software on demand            ] Starting ServiceConnectionThread, timeout is 30 seconds   (OpsiService.pyo|164)
[5] [Nov 15 16:24:36] [ service connection            ] Connecting to config server 'https://192.168.192.51:4447/rpc' #1   (OpsiService.pyo|326)
[3] [Nov 15 16:24:36] [ 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] [Nov 15 16:24:37] [ service connection            ] Disabling mysql backend and license management module: no customer in modules file   (JSONRPC.pyo|572)
[6] [Nov 15 16:24:37] [ service connection            ] <JSONRPCBackend(host=u'192.168.192.51', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[3] [Nov 15 16:24:37] [ service connection            ] Refusing to set deflate because opsi service answers with wrong HTTP header contents.   (JSONRPC.pyo|424)
[5] [Nov 15 16:24:37] [ service connection            ] Connected to config server 'https://192.168.192.51:4447/rpc'   (OpsiService.pyo|355)
[6] [Nov 15 16:24:37] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[6] [Nov 15 16:24:38] [ software on demand            ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0D2BFF50> started processing   (Worker.pyo|251)
[6] [Nov 15 16:24:38] [ software on demand            ] Reusing session for client '127.0.0.1', application 'opsi-client-systray-4.0.7.2'   (Worker.pyo|397)
[6] [Nov 15 16:24:38] [ software on demand            ] Starting ServiceConnectionThread, timeout is 30 seconds   (OpsiService.pyo|164)
[5] [Nov 15 16:24:38] [ service connection            ] Connecting to config server 'https://192.168.192.51:4447/rpc' #1   (OpsiService.pyo|326)
[3] [Nov 15 16:24:38] [ 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] [Nov 15 16:24:38] [ service connection            ] Disabling mysql backend and license management module: no customer in modules file   (JSONRPC.pyo|572)
[6] [Nov 15 16:24:38] [ service connection            ] <JSONRPCBackend(host=u'192.168.192.51', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[3] [Nov 15 16:24:38] [ service connection            ] Refusing to set deflate because opsi service answers with wrong HTTP header contents.   (JSONRPC.pyo|424)
[5] [Nov 15 16:24:38] [ service connection            ] Connected to config server 'https://192.168.192.51:4447/rpc'   (OpsiService.pyo|355)
[6] [Nov 15 16:24:39] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[6] [Nov 15 16:24:39] [ software on demand            ] Worker <ocdlib.SoftwareOnDemand.WorkerKioskJsonRpc object at 0x0D45F690> started processing   (Worker.pyo|251)
[6] [Nov 15 16:24:39] [ software on demand            ] Reusing session for client '127.0.0.1', application 'opsi-client-systray-4.0.7.2'   (Worker.pyo|397)
[6] [Nov 15 16:24:39] [ software on demand            ] Starting ServiceConnectionThread, timeout is 30 seconds   (OpsiService.pyo|164)
[5] [Nov 15 16:24:39] [ service connection            ] Connecting to config server 'https://192.168.192.51:4447/rpc' #1   (OpsiService.pyo|326)
[3] [Nov 15 16:24:39] [ 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] [Nov 15 16:24:39] [ service connection            ] Disabling mysql backend and license management module: no customer in modules file   (JSONRPC.pyo|572)
[6] [Nov 15 16:24:40] [ service connection            ] <JSONRPCBackend(host=u'192.168.192.51', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[3] [Nov 15 16:24:40] [ service connection            ] Refusing to set deflate because opsi service answers with wrong HTTP header contents.   (JSONRPC.pyo|424)
[5] [Nov 15 16:24:40] [ service connection            ] Connected to config server 'https://192.168.192.51:4447/rpc'   (OpsiService.pyo|355)
[3] [Nov 15 16:24:40] [ software on demand            ] Traceback:   (Logger.pyo|757)
[3] [Nov 15 16:24:40] [ software on demand            ]   File "OPSI\Service\Worker.pyo", line 292, in _errback
   (Logger.pyo|757)
[3] [Nov 15 16:24:40] [ software on demand            ]   File "twisted\internet\defer.pyo", line 653, in _runCallbacks
   (Logger.pyo|757)
[3] [Nov 15 16:24:40] [ software on demand            ]   File "ocdlib\SoftwareOnDemand.pyo", line 578, in _checkRpcs
   (Logger.pyo|757)
[3] [Nov 15 16:24:40] [ software on demand            ]      ==>>> You are not allowed to execute the method: 'backend_exit'   (Worker.pyo|301)
[3] [Nov 15 16:24:40] [ software on demand            ] [Failure instance: Traceback: <type 'exceptions.Exception'>: You are not allowed to execute the method: 'backend_exit'
twisted\internet\defer.pyo:653:_runCallbacks
ocdlib\SoftwareOnDemand.pyo:596:_processQuery
twisted\internet\defer.pyo:459:callback
twisted\internet\defer.pyo:567:_startRunCallbacks
--- <exception caught here> ---
twisted\internet\defer.pyo:653:_runCallbacks
ocdlib\SoftwareOnDemand.pyo:578:_checkRpcs
]   (Worker.pyo|302)
Die Fehlermeldung: "Failed to read version info from file u'/etc/opsi/version': [Errno 2] No such file or directory: u'/etc/opsi/version'" kann ich nicht ganz nachvollziehen, da die Datei vorhanden ist ist folgenden Inhalt hat: 4.0.7.45

Herzlichen Dank für jegliche Hilfe.

LG Ben
Zuletzt geändert von n.wenselowski am 17 Nov 2017, 11:26, insgesamt 1-mal geändert.
Grund: Log-Auszug in Code-Block gepackt.
Benutzeravatar
n.wenselowski
Ex-uib-Team
Beiträge: 3194
Registriert: 04 Apr 2013, 12:15

Re: Opsi Windows Client installiert nur beim hochfahren / On demand nicht aber beim Interval check

Beitrag von n.wenselowski »

Hallo Ben,

von welchem Intervall redest du denn? (Es gibt mehrere Möglichkeiten...)
Liege ich richtig mit dem vom Systray auf dem Client?
juergensb hat geschrieben: Folgendes steht in der opsiclient.log:

Code: Alles auswählen

[3] [Nov 15 16:24:34] [ 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)
Die Fehlermeldung: "Failed to read version info from file u'/etc/opsi/version': [Errno 2] No such file or directory: u'/etc/opsi/version'" kann ich nicht ganz nachvollziehen, da die Datei vorhanden ist ist folgenden Inhalt hat: 4.0.7.45
Da wir an der Stelle unter Windows sind gibt es dort die Datei /etc/opsi/version tatsächlich nicht. An dieser Stelle kannst du es ignorieren.


Viele Grüße

Niko

Code: Alles auswählen

import OPSI
juergensb
Beiträge: 6
Registriert: 15 Nov 2017, 16:32

Re: Opsi Windows Client installiert nur beim hochfahren / On demand nicht aber beim Interval check

Beitrag von juergensb »

Hallo Niko,

danke für den Hinweis.

Ja genau es geht um den systray_check_intervall. Den habe ich zur Versuchszwecke auf 5 Minuten gesetzt und so wird mir
alle 5 Minuten gemeldet das die neue Software installiert wird bzw. ein Update aufgespielt wird. Leider bleibt es bei den
Benachrichtigungen. Wie schon beschrieben gibt es diese Probleme bei einem Neustart oder der Installation "on_demand" nicht.

LG Ben
Benutzeravatar
n.wenselowski
Ex-uib-Team
Beiträge: 3194
Registriert: 04 Apr 2013, 12:15

Re: Opsi Windows Client installiert nur beim hochfahren / On demand nicht aber beim Interval check

Beitrag von n.wenselowski »

Hi,

das Systray checkt dann alle 5 Minuten ob Software zur Installation bereit steht. Das macht aber noch keine Installation.
Wenn du regelmäßig automatisch Software installieren lassen willst, musst du dem opsiclientd ein Timer-Event konfigurieren.


Gruß

Niko

Code: Alles auswählen

import OPSI
Antworten