Hallo,
mir ist im ersten Post ein Fehler passiert.
Beide Clients haben die gleichen Voraussetzungen.
- sind im lokalen Netz
- sind erreichbar
- Benutzer ist angemeldet
- opsi-client-agent 4.1.1.16-2
- Windows 10 1909
Die Version des opsi-client-agent ist nich die selbe. Alle Clients mit der aktuellen Version (4.1.1.16-2) haben no response als Ergebnis. Ich habe noch ein paar wenige Clients mit einer älteren Version (4.1.0.0-48), dort funktioniert die Abfrage der Session Informationen.
opsi-client-agent 4.1.1.16-2
Code: Alles auswählen
opsi@opsi01:~$ opsi-admin -a https://10.1.50.105:4441/opsiclientd -u "pc2058.domain.de" -p "8b513b2a3ba51860ffe842ffcf74c1e8" method getActiveSessions
[2] Traceback: (Logger.py|798)
[2] File "/usr/lib/python2.7/dist-packages/OPSI/Backend/JSONRPC.py", line 103, in processResult
raise exception
(Logger.py|798)
[2] ==>>> AttributeError("'pywintypes.datetime' object has no attribute 'dayself_update_from_url'") (error on server) (JSONRPC.py|112)
[2] Traceback: (Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 781, in execute
command.execute(self, self.getParams()[1:])
(Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 1211, in execute
result = method(*params)
(Logger.py|798)
[2] File "<string>", line 1, in getActiveSessions
(Logger.py|798)
[2] File "/usr/lib/python2.7/dist-packages/OPSI/Backend/JSONRPC.py", line 664, in _jsonRPC
return jsonrpc.execute()
(Logger.py|798)
[2] File "/usr/lib/python2.7/dist-packages/OPSI/Backend/JSONRPC.py", line 149, in execute
return self.waitForResult()
(Logger.py|798)
[2] File "/usr/lib/python2.7/dist-packages/OPSI/Backend/Backend.py", line 206, in waitForResult
raise self.error # pylint: disable=raising-bad-type
(Logger.py|798)
[2] ==>>> AttributeError("'pywintypes.datetime' object has no attribute 'dayself_update_from_url'") (error on server) (opsi-admin|783)
[3] Failed to execute u'method getActiveSessions': AttributeError("'pywintypes.datetime' object has no attribute 'dayself_update_from_url'") (error on server) (opsi-admin|785)
[2] Traceback: (Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 381, in main
shell.execute()
(Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 786, in execute
raise RuntimeError(message)
(Logger.py|798)
[2] ==>>> Failed to execute u'method getActiveSessions': AttributeError("'pywintypes.datetime' object has no attribute 'dayself_update_from_url'") (error on server) (opsi-admin|393)
[2] Traceback: (Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 1723, in <module>
main(sys.argv[1:])
(Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 394, in main
raise error
(Logger.py|798)
[2] ==>>> Failed to execute u'method getActiveSessions': AttributeError("'pywintypes.datetime' object has no attribute 'dayself_update_from_url'") (error on server) (opsi-admin|1730)
[3] Error during execution: Failed to execute u'method getActiveSessions': AttributeError("'pywintypes.datetime' object has no attribute 'dayself_update_from_url'") (error on server) (opsi-admin|1731)
opsi@opsi01:~$ opsi-admin -d method hostControlSafe_getActiveSessions 'pc2058.domain.de'
{
"pc2058.domain.de": {
"result": null,
"error": {
"message": "AttributeError(\"'pywintypes.datetime' object has no attribute 'dayself_update_from_url'\")",
"class": "AttributeError"
}
}
}
[2] Traceback: (Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 389, in main
searchForError(dict(resultAsJSON))
(Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 371, in searchForError
searchForError(obj[key])
(Logger.py|798)
[2] File "/usr/bin/opsi-admin", line 368, in searchForError
raise ErrorInResultException(obj['error'])
(Logger.py|798)
opsi-client-agent 4.1.0.0-48
Code: Alles auswählen
opsi@opsi01:~$ opsi-admin -a https://192.168.169.10:4441/opsiclientd -u "nb2097.domain.de" -p "7f6f4769703103f69bc26f3fb7441484" method getActiveSessions
[
{
"UserName": "a80672",
"AuthenticationPackage": "Kerberos",
"LogonServer": "DC01",
"LogonId": 1887219,
"Upn": "a80672@domain.de",
"Session": 1,
"DnsDomainName": "domain.de",
"Sid": "S-1-5-21-484763869-1580436667-725345543-3069",
"LogonType": 2,
"LogonDomain": "domain",
"LogonTime": "2020-12-17 06:05:16"
}
]
opsi@opsi01:~$ opsi-admin -d method hostControlSafe_getActiveSessions 'nb2097.domain.de'
{
"nb2097.domain.de": {
"result": [
{
"UserName": "a80672",
"AuthenticationPackage": "Kerberos",
"LogonServer": "DC01",
"LogonId": 1887219,
"Upn": "a80672@domain.de",
"Session": 1,
"DnsDomainName": "domain.de",
"Sid": "S-1-5-21-484763869-1580436667-725345543-3069",
"LogonType": 2,
"LogonDomain": "domain",
"LogonTime": "2020-12-17 06:05:16"
}
],
"error": null
}
}
Vermutlich hätte ich mir den Code sparen können. Mit opsi-client-agent 4.1.1.17-2 funktionieren die Session Informationen wieder.
Da ich die Session Informationen oft brauche, wann wird opsi-client-agent 4.1.1.17-2 in stable veröffentlicht?
Viele Grüße
isnoguter