forum.opsi.org

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

Could not open DCOM connection

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

Seite 1 von 2

Could not open DCOM connection

Verfasst: 12 Dez 2024, 13:45
von Rexhepi
Moin,

beim Versuch den opsi-Client auf einem Windows-Host über die Konsole zu installieren, erhalte ich folgende Fehlermeldung:

Code: Alles auswählen

Could not open DCOM connection: rpc_s_access_denied   (windows.py:73)
Traceback (most recent call last):
  File "opsideployclientagent/windows.py", line 68, in dcom_connection
  File "impacket/dcerpc/v5/dcomrt.py", line 1076, in CoCreateInstanceEx
  File "impacket/dcerpc/v5/dcomrt.py", line 1854, in RemoteCreateInstance
  File "impacket/dcerpc/v5/rpcrt.py", line 859, in request
  File "impacket/dcerpc/v5/rpcrt.py", line 1323, in recv
impacket.dcerpc.v5.rpcrt.DCERPCException: rpc_s_access_denied
Der Befehl den ich dafür verwende:

Code: Alles auswählen

./opsi-deploy-client-agent <hostname>.<domäne> -u <domäne>\\<administrator>
Ich habe mit diesem Befehl schon viele opsi-Clients ausgerollt und hatte nie Probleme. Dann habe ich 1-2 Wochen nur am PXE-Boot gearbeitet, und jetzt geht es nicht mehr.

Die Windows-Firewall ist auf dem Client ausgeschaltet. DCOM und COM sind aktiviert.

opsi-Version: 4.3

Ich bitte um Hilfe. :)

VG
Rexhepi

Re: Could not open DCOM connection

Verfasst: 13 Dez 2024, 08:31
von Andi_089
Wir hatten das Problem auch in der Art.

Bei uns hat uns dann dieser Microsoft Artikel Weitergeholfen:

https://learn.microsoft.com/de-de/troub ... estriction

Das Ende vom Lied bei uns ist, dass wir per GPO einen Maschinenbezogenen Registry Eintrag setzen

Code: Alles auswählen

Pfad:		HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
REG_DWORD: 	LocalAccountTokenFilterPolicy
Value:		1 (Dez)
Damit klappt bei uns wieder alles.

Re: Could not open DCOM connection

Verfasst: 16 Dez 2024, 08:13
von Rexhepi
Vielen Dank für deine Antwort.

Leider erhalte ich immer noch die gleiche Fehlermeldung. :|

Re: Could not open DCOM connection

Verfasst: 19 Dez 2024, 13:35
von n.doerrer
Sind die anderen Voraussetzungen auch erfüllt?
https://docs.opsi.org/opsi-docs-de/4.3/ ... psi-deploy

Klappt die Anmeldung mit den credentials über "smbclient" oder "net use..." von einer anderen Maschine aus?
Um auszuschließen, dass es ein DCOM-Problem ist, könnte man es auch mal mit einem lokalen Admin-Account testen.

Re: Could not open DCOM connection

Verfasst: 19 Dez 2024, 15:16
von Rexhepi
n.doerrer hat geschrieben: ↑19 Dez 2024, 13:35 Sind die anderen Voraussetzungen auch erfüllt?
https://docs.opsi.org/opsi-docs-de/4.3/ ... psi-deploy
Ja, alle Voraussetzungen sind erfüllt, ich habe die mehrmals gecheckt.
n.doerrer hat geschrieben: ↑19 Dez 2024, 13:35 Klappt die Anmeldung mit den credentials über "smbclient" oder "net use..." von einer anderen Maschine aus?
Die Anmeldung von einem anderen Rechner aus funktionierte problemlos.
n.doerrer hat geschrieben: ↑19 Dez 2024, 13:35 Um auszuschließen, dass es ein DCOM-Problem ist, könnte man es auch mal mit einem lokalen Admin-Account testen.
Ich habe alle möglichen Konten ausprobiert, von opsi-Konten bis hin zu lokalen Admin-Konten. Immer noch die gleiche Fehlermeldung.

Re: Could not open DCOM connection

Verfasst: 19 Dez 2024, 15:50
von n.doerrer
Hm, das hier habe ich noch gefunden, aber viel steht da auch nicht mehr https://github.com/fortra/impacket/issues/664

Ist vielleicht irgendwas im event log?

Re: Could not open DCOM connection

Verfasst: 20 Dez 2024, 13:56
von n.doerrer
Eine Möglichkeit ist mir noch eingefallen: Falls der domänen-username Sonderzeichen enthält (wie Akzent-Zeichen und Ähnliche) kann es nötig sein, ihn in doppelte Anführungszeichen zu setzen.

Re: Could not open DCOM connection

Verfasst: 02 Jan 2025, 09:28
von Rexhepi
Frohes neues Jahr!

Also habe ich den Befehl

Code: Alles auswählen

./opsi-deploy-client-agent <hostname>.<domain> -u <domain>\\<administrator> -vvv
ausgeführt und jetzt bekomme ich Folgendes:

Code: Alles auswählen

[6] [2025-01-02 08:18:23.275] [host.domain.de] Session: DOMAIN\sa_opsi - Logging off of SMB Session   (session.py:414)
[6] [2025-01-02 08:18:23.275] [host.domain.de] Session: DOMAIN\sa_opsi - Sending Logoff message   (session.py:416)
[7] [2025-01-02 08:18:23.275] [host.domain.de] SMB2Logoff:
    structure_size = 4
    reserved = 0

    Raw Hex:
        04 00 00 00   (session.py:417)
[6] [2025-01-02 08:18:23.275] [host.domain.de] Session: DOMAIN\sa_opsi - Receiving Logoff response   (session.py:420)
[7] [2025-01-02 08:18:23.276] [               ] Socket recv() returned 4 bytes (total 4)   (transport.py:154)
[7] [2025-01-02 08:18:23.276] [               ] Socket recv(68) (total 68)   (transport.py:128)
[7] [2025-01-02 08:18:23.276] [               ] Socket recv() returned 68 bytes (total 68)   (transport.py:154)
[7] [2025-01-02 08:18:23.276] [               ] Socket recv(4) (total 4)   (transport.py:128)
[7] [2025-01-02 08:18:23.276] [host.domain.de] SMB2Logoff:
    structure_size = 4
    reserved = 0

    Raw Hex:
        04 00 00 00   (session.py:424)
[6] [2025-01-02 08:18:23.276] [host.domain.de] Disconnecting transport connection   (connection.py:951)
[6] [2025-01-02 08:18:23.276] [host.domain.de] Disconnecting DirectTcp socket   (transport.py:75)
[7] [2025-01-02 08:18:23.276] [               ] Socket recv() returned 0 bytes (total 4)   (transport.py:154)
[5] [2025-01-02 08:18:23.277] [host.domain.de] Installing opsi-client-agent   (common.py:420)
[6] [2025-01-02 08:18:23.277] [host.domain.de] Deploying from path c:\\opsi.org\tmp\opsi-deploy-client-agent-1735805789   (windows.py:330)
[6] [2025-01-02 08:18:23.277] [host.domain.de] JSONRPC request to https://localhost:4447: id='8f84f2aa-9ca1-4c8c-932b-96d2576e0b83', method=configState_getObjects, Content-Type=application/msgpack, Content-Encoding=lz4, timeout=300.0   (opsiservice.py:1268)
[7] [2025-01-02 08:18:23.278] [host.domain.de] Resetting dropped connection: localhost   (connectionpool.py:291)
[7] [2025-01-02 08:18:23.292] [host.domain.de] https://localhost:4447 "POST /rpc HTTP/11" 200 62   (connectionpool.py:546)
[6] [2025-01-02 08:18:23.292] [host.domain.de] Got response status=200, id='8f84f2aa-9ca1-4c8c-932b-96d2576e0b83', method=configState_getObjects, Content-Type=application/msgpack, Content-Encoding=, duration=0.015s   (opsiservice.py:1291)
[6] [2025-01-02 08:18:23.292] [host.domain.de] JSONRPC request to https://localhost:4447: id='e5efa2a8-64e6-47e2-9220-75eaef003dba', method=config_getObjects, Content-Type=application/msgpack, Content-Encoding=lz4, timeout=300.0   (opsiservice.py:1268)
[7] [2025-01-02 08:18:23.297] [host.domain.de] https://localhost:4447 "POST /rpc HTTP/11" 200 317   (connectionpool.py:546)
[6] [2025-01-02 08:18:23.298] [host.domain.de] Got response status=200, id='e5efa2a8-64e6-47e2-9220-75eaef003dba', method=config_getObjects, Content-Type=application/msgpack, Content-Encoding=, duration=0.005s   (opsiservice.py:1291)
[6] [2025-01-02 08:18:23.298] [host.domain.de] JSONRPC request to https://localhost:4447: id='fb0ab8cd-18b4-4147-bea6-9fbc6a5f82ad', method=productOnClient_updateObjects, Content-Type=application/msgpack, Content-Encoding=lz4, timeout=300.0   (opsiservice.py:1268)
[7] [2025-01-02 08:18:23.303] [host.domain.de] https://localhost:4447 "POST /rpc HTTP/11" 200 62   (connectionpool.py:546)
[6] [2025-01-02 08:18:23.303] [host.domain.de] Got response status=200, id='fb0ab8cd-18b4-4147-bea6-9fbc6a5f82ad', method=productOnClient_updateObjects, Content-Type=application/msgpack, Content-Encoding=, duration=0.005s   (opsiservice.py:1291)
[5] [2025-01-02 08:18:23.303] [host.domain.de] Running installation script...   (windows.py:344)
[7] [2025-01-02 08:18:23.303] [host.domain.de] Scheduled task xml: <?xml version="1.0" encoding="UTF-16"?>
                <Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
                        <Triggers>
                                <TimeTrigger>
                                        <StartBoundary>2000-01-01T00:00:00</StartBoundary>
                                        <Enabled>true</Enabled>
                                </TimeTrigger>
                        </Triggers>
                        <Principals>
                                <Principal id="LocalSystem">
                                        <UserId>S-1-5-18</UserId>
                                        <RunLevel>HighestAvailable</RunLevel>
                                </Principal>
                        </Principals>
                        <Settings>
                                <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
                                <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
                                <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
                                <AllowHardTerminate>true</AllowHardTerminate>
                                <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
                                <IdleSettings>
                                        <StopOnIdleEnd>true</StopOnIdleEnd>
                                        <RestartOnIdle>false</RestartOnIdle>
                                </IdleSettings>
                                <AllowStartOnDemand>true</AllowStartOnDemand>
                                <Enabled>true</Enabled>
                                <Hidden>true</Hidden>
                                <RunOnlyIfIdle>false</RunOnlyIfIdle>
                                <WakeToRun>false</WakeToRun>
                                <ExecutionTimeLimit>P1D</ExecutionTimeLimit>
                                <Priority>7</Priority>
                        </Settings>
                        <Actions Context="LocalSystem">
                                <Exec>
                                        <Command>cmd.exe</Command>
                                        <Arguments>/Q /c c:\\opsi.org\tmp\opsi-deploy-client-agent-1735805789\oca-installation-helper.exe --log-file c:\opsi.org\log\opsi-deploy-client-agent.log --log-level debug --service-address opsi.domain.de --service-username host.domain.de --service-password ***secret*** --client-id host.domain.de --no-gui --non-interactive</Arguments>
                                </Exec>
                        </Actions>
                </Task>
                   (windows.py:224)
[6] [2025-01-02 08:18:23.339] [host.domain.de] Register scheduled task 'opsi-deploy-client-agent-1735805903'   (windows.py:236)
[6] [2025-01-02 08:18:23.381] [host.domain.de] Scheduled task started   (windows.py:242)
[7] [2025-01-02 08:18:32.486] [host.domain.de] TSCH SessionError: code: 0x8004130b - SCHED_E_TASK_NOT_RUNNING - There is no running instance of the task.   (windows.py:252)
[6] [2025-01-02 08:18:32.487] [host.domain.de] Scheduled task ended   (windows.py:253)
[6] [2025-01-02 08:18:32.487] [host.domain.de] Removing scheduled task 'opsi-deploy-client-agent-1735805903'   (windows.py:259)
[7] [2025-01-02 08:18:32.497] [host.domain.de] Evaluating success   (common.py:425)
[6] [2025-01-02 08:18:32.497] [host.domain.de] JSONRPC request to https://localhost:4447: id='4d423c71-fbe5-41d3-b62e-52a58ba87ea9', method=productOnClient_getObjects, Content-Type=application/msgpack, Content-Encoding=lz4, timeout=300.0   (opsiservice.py:1268)
[7] [2025-01-02 08:18:32.498] [host.domain.de] Resetting dropped connection: localhost   (connectionpool.py:291)
[7] [2025-01-02 08:18:32.512] [host.domain.de] https://localhost:4447 "POST /rpc HTTP/11" 200 438   (connectionpool.py:546)
[6] [2025-01-02 08:18:32.512] [host.domain.de] Got response status=200, id='4d423c71-fbe5-41d3-b62e-52a58ba87ea9', method=productOnClient_getObjects, Content-Type=application/msgpack, Content-Encoding=, duration=0.015s   (opsiservice.py:1291)
[u][b][3] [2025-01-02 08:18:32.513] [host.domain.de] Deployment to host.domain.de failed: Installation of opsi-client-agent on client host.domain.de unsuccessful   (common.py:445)[/b][/u]
[5] [2025-01-02 08:18:32.513] [host.domain.de] Cleaning up   (windows.py:382)
[6] [2025-01-02 08:18:32.513] [host.domain.de] Using smbprotocol to cleanup files   (windows.py:390)
[6] [2025-01-02 08:18:32.513] [host.domain.de] Initialising connection, guid: f43c7485-1d79-47f7-b070-d82db6b0864b, require_signing: True, server_name: host.domain.de, port: 445   (connection.py:741)
[6] [2025-01-02 08:18:32.513] [host.domain.de] Setting up transport connection   (connection.py:864)
[6] [2025-01-02 08:18:32.513] [host.domain.de] Connecting to DirectTcp socket   (transport.py:64)
[7] [2025-01-02 08:18:32.519] [               ] Socket recv(4) (total 4)   (transport.py:128)
[6] [2025-01-02 08:18:32.519] [host.domain.de] Starting negotiation with SMB server   (connection.py:873)
[6] [2025-01-02 08:18:32.520] [host.domain.de] Negotiating with SMB2 protocol with highest client dialect of: SMB_3_1_1   (connection.py:1542)
[7] [2025-01-02 08:18:32.520] [host.domain.de] Adding client guid f43c7485-1d79-47f7-b070-d82db6b0864b to negotiate request   (connection.py:1550)
[7] [2025-01-02 08:18:32.520] [host.domain.de] Adding client capabilities 69 to negotiate request   (connection.py:1558)
[7] [2025-01-02 08:18:32.520] [host.domain.de] Adding preauth integrity capabilities of hash SHA512 and salt b'\xf5\xa1\xbf\xea\xf6\xd0p7\xa7m\t\xa8\xb1\xb6<_{\xdf\x19\x07\x11e\xdcm\x1b$\x8f\xaa\xc9\x05t~' to negotiate request   (connection.py:1571)
[7] [2025-01-02 08:18:32.520] [host.domain.de] Adding encryption capabilities of AES128|256 GCM and AES128|256 CCM to negotiate request   (connection.py:1581)
[7] [2025-01-02 08:18:32.520] [host.domain.de] Adding netname context id of host.domain.de to negotiate request   (connection.py:1587)
[7] [2025-01-02 08:18:32.520] [host.domain.de] Adding signing algorithms AES_GMAC, AES_CMAC, and HMAC_SHA256 to negotiate request   (connection.py:1593)
[6] [2025-01-02 08:18:32.521] [host.domain.de] Sending SMB2 Negotiate message   (connection.py:1606)
[7] [2025-01-02 08:18:32.521] [host.domain.de] SMB3NegotiateRequest:
Obwohl ich keine Konfigurationen geändert habe, erhalte ich jetzt eine andere Fehlermeldung.

Code: Alles auswählen

[2025-01-02 08:18:32.513] [host.domain.de] Deployment to host.domain.de failed: Installation of opsi-client-agent on client host.domain.de unsuccessful   (common.py:445)

Re: Could not open DCOM connection

Verfasst: 08 Jan 2025, 08:27
von n.doerrer
Ebenso frohes neues Jahr!

Das ist auf alle Fälle schonmal ein Schritt nach vorne.
Die Fehlermeldung suggeriert, dass die Installation (oder mindestens der oca-installation-helper) auf dem client gestartet wurde. Dazu gibts mehr infos auf dem client unter c:\opsi.org\log\opsi-client-agent.log (oder falls es nicht so weit gekommen sein sollte unter %temp%\oca-installation-helper.log des users, der für das setup verwendet wird).

Re: Could not open DCOM connection

Verfasst: 08 Jan 2025, 10:32
von Rexhepi
Hier die Logdatei opsi-client-agent.log:

Code: Alles auswählen

[INFO      2025-01-02 09:18:28] Installation helper running from 'c:\opsi.org\tmp\opsi-deploy-client-agent-1735805789\oca-installation-helper.exe', working dir 'C:\Windows\system32'   (__main__.py:62)
[DEBUG     2025-01-02 09:18:28] Config from cmdline: interactive=False, client_id=s000008y.domain.de, service_address=opsi.domain.de, service_username=s000008y.domain.de, service_password=********************************, depot=None, group=None, force_recreate_client=False, finalize=noreboot, dns_domain=None, read_conf_files=('install.conf', 'config.ini', 'opsiclientd.conf'), install_condition=always, set_mac_address=True, end_command=None, end_marker=None   (config.py:80)
[DEBUG     2025-01-02 09:18:28] Delete temp dir 'C:\Windows\TEMP\oca-installation-helper-tmp'   (__main__.py:352)
[INFO      2025-01-02 09:18:28] Copy installation files from 'c:\opsi.org\tmp\opsi-deploy-client-agent-1735805789' to 'C:\Windows\TEMP\oca-installation-helper-tmp'   (__main__.py:292)
[INFO      2025-01-02 09:18:28] Installation files succesfully copied to 'C:\Windows\TEMP\oca-installation-helper-tmp'   (__main__.py:292)
[INFO      2025-01-02 09:18:28] Running elevated. Continuing execution.   (__main__.py:390)
[INFO      2025-01-02 09:18:28] Filling empty config fields from windows registry.   (__main__.py:71)
[DEBUG     2025-01-02 09:18:28] Requesting key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\opsi-client-agent and value INSTALL_PARAMS   (config.py:226)
[INFO      2025-01-02 09:18:28] Could not open registry key, skipping fill_config_from_registry.   (config.py:244)
[DEBUG     2025-01-02 09:18:28] Caught Error [WinError 2] Das System kann die angegebene Datei nicht finden   (config.py:245)
Traceback (most recent call last):
  File "ocainstallationhelper\config.py", line 238, in fill_config_from_registry
  File "ocainstallationhelper\config.py", line 229, in get_registry_value
FileNotFoundError: [WinError 2] Das System kann die angegebene Datei nicht finden
[INFO      2025-01-02 09:18:28] Filling empty config fields from config files.   (__main__.py:74)
[INFO      2025-01-02 09:18:28] Config file 'C:\Windows\TEMP\oca-installation-helper-tmp\install.conf' not found   (config.py:124)
[INFO      2025-01-02 09:18:28] Config file 'C:\Program Files (x86)\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf' not found   (config.py:124)
[INFO      2025-01-02 09:18:28] Reading config file 'C:\Windows\TEMP\oca-installation-helper-tmp\files\opsi\cfg\config.ini'   (config.py:143)
[DEBUG     2025-01-02 09:18:28] Config after reading 'C:\Windows\TEMP\oca-installation-helper-tmp\files\opsi\cfg\config.ini': interactive=False, client_id=s000008y.domain.de, service_address=opsi.domain.de, service_username=s000008y.domain.de, service_password=********************************, dns_domain=   (config.py:190)
[INFO      2025-01-02 09:18:28] Filling empty config fields from zeroconf information.   (__main__.py:78)
[INFO      2025-01-02 09:18:28] Filling empty config fields from default.   (__main__.py:92)
[INFO      2025-01-02 09:18:28] Got config: service_address='opsi.domain.de', service_username='s000008y.domain.de', client_id='s000008y.domain.de'   (__main__.py:94)
[INFO      2025-01-02 09:18:28] Starting installation   (__main__.py:197)
[DEBUG     2025-01-02 09:18:28] opsi-client-agent versions: installed=None, this=None   (__main__.py:202)
[INFO      2025-01-02 09:18:28] Connecting to service...   (__main__.py:292)
[DEBUG     2025-01-02 09:18:28] Current proxy related environment variables: http_proxy=None, https_proxy=None, no_proxy=None   (__init__.py:182)
[INFO      2025-01-02 09:18:28] Using proxy settings: http_proxy=None, https_proxy=None, no_proxy='localhost,ip6-localhost,S000008Y.domain.de,127.0.0.1,::1'   (__init__.py:219)
[INFO      2025-01-02 09:18:28] Connecting to service https://opsi.domain.de:4447/rpc   (jsonrpc.py:608)
[INFO      2025-01-02 09:18:28] JSONRPC request to https://opsi.domain.de:4447/rpc: ip_version=auto, id=1, method=backend_getInterface, Content-Type=application/json, Content-Encoding=, timeout=(10, 300)   (jsonrpc.py:461)
[DEBUG     2025-01-02 09:18:28] Starting new HTTPS connection (1): opsi.domain.de:4447   (connectionpool.py:1051)
[DEBUG     2025-01-02 09:18:28] Using ip version auto   (jsonrpc.py:94)
[ERROR     2025-01-02 09:18:31] HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))   (__main__.py:223)
Traceback (most recent call last):
  File "urllib3\connection.py", line 199, in _new_conn
  File "urllib3\util\connection.py", line 60, in create_connection
  File "socket.py", line 962, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "urllib3\connectionpool.py", line 789, in urlopen
  File "urllib3\connectionpool.py", line 490, in _make_request
  File "urllib3\connectionpool.py", line 466, in _make_request
  File "urllib3\connectionpool.py", line 1095, in _validate_conn
  File "urllib3\connection.py", line 693, in connect
  File "urllib3\connection.py", line 206, in _new_conn
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "requests\adapters.py", line 667, in send
  File "urllib3\connectionpool.py", line 843, in urlopen
  File "urllib3\util\retry.py", line 519, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "ocainstallationhelper\__main__.py", line 214, in install
  File "ocainstallationhelper\__main__.py", line 241, in service_setup
  File "ocainstallationhelper\backend.py", line 19, in __init__
  File "opsicommon\client\jsonrpc.py", line 259, in __init__
  File "opsicommon\client\jsonrpc.py", line 610, in connect
  File "opsicommon\client\jsonrpc.py", line 475, in _execute_rpc
  File "requests\sessions.py", line 637, in post
  File "requests\sessions.py", line 589, in request
  File "requests\sessions.py", line 703, in send
  File "opsicommon\client\jsonrpc.py", line 75, in send
  File "requests\adapters.py", line 700, in send
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))
[ERROR     2025-01-02 09:18:31] HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))   (__main__.py:439)
Traceback (most recent call last):
  File "urllib3\connection.py", line 199, in _new_conn
  File "urllib3\util\connection.py", line 60, in create_connection
  File "socket.py", line 962, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "urllib3\connectionpool.py", line 789, in urlopen
  File "urllib3\connectionpool.py", line 490, in _make_request
  File "urllib3\connectionpool.py", line 466, in _make_request
  File "urllib3\connectionpool.py", line 1095, in _validate_conn
  File "urllib3\connection.py", line 693, in connect
  File "urllib3\connection.py", line 206, in _new_conn
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "requests\adapters.py", line 667, in send
  File "urllib3\connectionpool.py", line 843, in urlopen
  File "urllib3\util\retry.py", line 519, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "ocainstallationhelper\__main__.py", line 436, in run
  File "ocainstallationhelper\__main__.py", line 214, in install
  File "ocainstallationhelper\__main__.py", line 241, in service_setup
  File "ocainstallationhelper\backend.py", line 19, in __init__
  File "opsicommon\client\jsonrpc.py", line 259, in __init__
  File "opsicommon\client\jsonrpc.py", line 610, in connect
  File "opsicommon\client\jsonrpc.py", line 475, in _execute_rpc
  File "requests\sessions.py", line 637, in post
  File "requests\sessions.py", line 589, in request
  File "requests\sessions.py", line 703, in send
  File "opsicommon\client\jsonrpc.py", line 75, in send
  File "requests\adapters.py", line 700, in send
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))
[ERROR     2025-01-02 09:18:31] HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))   (__main__.py:292)
Traceback (most recent call last):
  File "urllib3\connection.py", line 199, in _new_conn
  File "urllib3\util\connection.py", line 60, in create_connection
  File "socket.py", line 962, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "urllib3\connectionpool.py", line 789, in urlopen
  File "urllib3\connectionpool.py", line 490, in _make_request
  File "urllib3\connectionpool.py", line 466, in _make_request
  File "urllib3\connectionpool.py", line 1095, in _validate_conn
  File "urllib3\connection.py", line 693, in connect
  File "urllib3\connection.py", line 206, in _new_conn
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "requests\adapters.py", line 667, in send
  File "urllib3\connectionpool.py", line 843, in urlopen
  File "urllib3\util\retry.py", line 519, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "ocainstallationhelper\__main__.py", line 436, in run
  File "ocainstallationhelper\__main__.py", line 214, in install
  File "ocainstallationhelper\__main__.py", line 241, in service_setup
  File "ocainstallationhelper\backend.py", line 19, in __init__
  File "opsicommon\client\jsonrpc.py", line 259, in __init__
  File "opsicommon\client\jsonrpc.py", line 610, in connect
  File "opsicommon\client\jsonrpc.py", line 475, in _execute_rpc
  File "requests\sessions.py", line 637, in post
  File "requests\sessions.py", line 589, in request
  File "requests\sessions.py", line 703, in send
  File "opsicommon\client\jsonrpc.py", line 75, in send
  File "requests\adapters.py", line 700, in send
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='opsi.domain.de', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x076930B0>: Failed to resolve 'opsi.domain.de' ([Errno 11001] getaddrinfo failed)"))
Alle Zeiten sind UTC+02:00
Seite 1 von 2

Powered by phpBB® Forum Software © phpBB Limited

Deutsche Übersetzung durch phpBB.de