ich versuche gerade einiger Zeit mal wieder einen OPSI Client über die Konsole anzulegen:
Code: Alles auswählen
/var/lib/opsi/depot/opsi-client-agent/opsi-deploy-client-agent -u 'domain\admin' -c ph-testgb001.peiker-holding.de --depot ph-opsi.peiker-holding.de
Code: Alles auswählen
[3] [2022-08-30 13:23:53.869] [ph-testgb001.peiker-holding.de] Could not open DCOM connection: Could not connect: timed out (windows.py:70)
Traceback (most recent call last):
File "impacket/dcerpc/v5/transport.py", line 352, in connect
TimeoutError: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "opsideployclientagent/windows.py", line 63, in dcom_connection
File "impacket/dcerpc/v5/dcomrt.py", line 982, in __init__
File "impacket/dcerpc/v5/dcomrt.py", line 1071, in initConnection
File "impacket/dcerpc/v5/rpcrt.py", line 803, in connect
File "impacket/dcerpc/v5/transport.py", line 355, in connect
impacket.dcerpc.v5.rpcrt.DCERPCException: Could not connect: timed out
Ich habe mal ins apt log geschaut:
Code: Alles auswählen
Start-Date: 2022-07-17 12:58:29
Commandline: apt upgrade
Upgrade: grafana:amd64 (9.0.0, 9.0.3), opsipxeconfd:amd64 (4.2.0.27-1, 4.2.0.30-1), opsi-linux-bootimage:amd64 (20220428-1, 20220516-1), opsi-tftpd-hpa:amd64 (5.2.8-77, 5.2.8-78), opsiconfd:amd64 (4.2.0.255-1, 4.2.0.272-1), opsi-utils:amd64 (4.2.0.165-1, 4.2.0.172-1), opsi-server-full:amd64 (4.2.0.66-1, 4.2.0.69-1)
End-Date: 2022-07-17 13:00:19
Code: Alles auswählen
Start-Date: 2022-08-30 13:20:40
Commandline: apt-get dist-upgrade
Upgrade: tzdata:amd64 (2021a-1+deb11u4, 2021a-1+deb11u5), grafana:amd64 (9.0.3, 9.1.1), opsi-linux-bootimage:amd64 (20220516-1, 20220617-1), redis-timeseries:amd64 (1.4.11.0-1, 1.6.16.1-1), opsiconfd:amd64 (4.2.0.272-1, 4.2.0.284-1), opsi-utils:amd64 (4.2.0.172-1, 4.2.0.183-1)
End-Date: 2022-08-30 13:21:50
Habt Ihr ein paar Brotkrümchen für mich, nach den ich Suchen sollte?
Grüße
Gregor