Probleme mit Clients durch neuen Server

Antworten
uniquare
Beiträge: 6
Registriert: 04 Mär 2013, 10:22
Kontaktdaten:

Probleme mit Clients durch neuen Server

Beitrag von uniquare »

Hallo liebes Opsi-Forum / Support-Team

Wir haben uns entschlossen die Server-Seite von Opsi neu zu machen da wir vom 32bit OS weg wollten.
Für einige der Clients lief der Umstieg problemlos, andere Clients verweigern aber das Zusammenspiel.

Code: Alles auswählen

opsiconfd --version => 4.2.0.180 [python-opsi=4.2.0.206]
opsi config editor  Version 4.1.9.8.5 (2021/04/12)
Exemplarischer Problem-Client

Code: Alles auswählen

opsi-client-agent Version ist 4.1.0.0-32
###
(0)       
(1)       [1] [Aug 04 13:03:16:831] --
(2)       [1] [Aug 04 13:03:16:831] --
(3)       [1] [Aug 04 13:03:16:831] c:\opsi.org\log\\opsi-script-part-Wt93Nz17.log
(4)       [1] [Aug 04 13:03:16:831] opsi-script 4.12.1.5 started at >>
(5)       [1] [Aug 04 13:03:16:832] opsi-script log file with encoding utf8
(6)       [1] [Aug 04 13:03:16:832] startmessage opsi-script created at CentralForm.FormCreate: 04/08/2021 13:03:16
(7)       [1] [Aug 04 13:03:16:832] Loading skin from: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\winstskin
(8)       [1] [Aug 04 13:03:16:832] Called with parameter: /opsiservice\r\nhttps://opsisrv.lan:4447/rpc\r\n/clientid\r\nopsiclient1.lan\r\n/username\r\nopsiclient1.lan\r\n/password\r\n***(confidential)***
(9)       [1] [Aug 04 13:03:16:832] Depot path from readconfig:  j:\ 04/08/2021 13:03:16
(10)      [1] [Aug 04 13:03:16:832] startmessage StartProgramModes and create log: 04/08/2021 13:03:16
(11)      [1] [Aug 04 13:03:16:832] pm: 5 04/08/2021 13:03:16
(12)      [1] [Aug 04 13:03:16:832] startmessage start opsi service connection: 04/08/2021 13:03:16
(13)      [1] [Aug 04 13:03:16:832] startmessage: opsidata initialized: 04/08/2021 13:03:16
(14)      [1] [Aug 04 13:03:16:832] opsiclient1.lan
(15)      [1] [Aug 04 13:03:16:832] Starting Servicecall: backend_info
(16)      [1] [Aug 04 13:03:16:832] Problem getting backend_info from service
(17)      [1] [Aug 04 13:03:16:832] startmessage: opsidata initialized: 04/08/2021 13:03:16
(18)      [1] [Aug 04 13:03:16:832] startmessage create log: 04/08/2021 13:03:16
(19)      [1] [Aug 04 13:03:16:832] force_min_loglevel: 4
(20)      [1] [Aug 04 13:03:16:832] default_loglevel: 7
(21)      [1] [Aug 04 13:03:16:832] debug_prog: false
(22)      [1] [Aug 04 13:03:16:832] debug_lib: true
(28)      [3] [Aug 04 13:03:16:999] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0-> retrieveJSONObject:1: Stream read error
(31)      [3] [Aug 04 13:03:17:050] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0-> retrieveJSONObject:1: Stream read error
(32)      [3] [Aug 04 13:03:17:050] Failed fetching sorted POC list !
(33)      [3] [Aug 04 13:03:17:050] No correct calculated installation sequence !
(34)      [6] [Aug 04 13:03:17:050] Starting fetching unsorted POC list
(37)      [3] [Aug 04 13:03:17:113] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0-> retrieveJSONObject:1: Stream read error
(40)      [3] [Aug 04 13:03:17:161] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0-> retrieveJSONObject:1: Stream read error
(43)      [3] [Aug 04 13:03:17:242] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0-> retrieveJSONObject:1: Stream read error
(44)      [1] [Aug 04 13:03:17:242] Computername:opsiclient1.lan
(45)      [1] [Aug 04 13:03:17:242] Computername according to Environment Variable :host
(46)      [1] [Aug 04 13:03:17:242] opsi service URL https://opsisrv.lan:4447
(47)      [6] [Aug 04 13:03:17:243] Depot path:  j:\
(48)      [6] [Aug 04 13:03:17:243] 
(50)      [6] [Aug 04 13:03:17:245] bootmode BKSTD
(52)      [6] [Aug 04 13:03:17:245] Registry key [HKLM\SOFTWARE\opsi.org\winst]  opened
(53)      [6] [Aug 04 13:03:17:245]                   Variable "RebootRequested"  is keeping its value "0"
(54)      [6] [Aug 04 13:03:17:245]                   Variable "LastLogFilename"  is keeping its value "c:\opsi.org\log\opsi-script.log"
(55)      [6] [Aug 04 13:03:17:245]                   Variable "ContinueLogFile"  is keeping its value "0"
(56)      [6] [Aug 04 13:03:17:245]                   Variable "NumberOfErrors"  is keeping its value "0"
(57)      [6] [Aug 04 13:03:17:245]                   Key flushed
(58)      [6] [Aug 04 13:03:17:245]                   Key closed
(59)      [5] [Aug 04 13:03:17:247] -------- submitted part of log file ends here, see the rest of log file on client ----------
Es gibt Clients mit derselben opsi-client-agent-Version (4.1.0.0-32) die ohne Problem funktionieren.
Auf einem der Problem-Clients haben wir nach
- deactivate
- und entfernen der Services
den aktuellen Client installiert (mittels service-setup.cmd), danach gab es kein weiteres Problem.
Jetzt würden wir natürlich - da es einerseits einige Clients trifft und andrerseits nicht (nur?) an der Client-Version liegt - gerne wissen, wie wir das Problem in den Griff kriegen könnten, ohne auf jedem Client händisch den Agent zu installieren.

Vielen Dank im Voraus .. :)
Antworten