Skip to main content
Question

Promox Worker installieren

  • July 15, 2025
  • 7 comments
  • 174 views

Ich versuche in unserem Proxmox Cluster den Worker zu installieren, in dem ich das aus der Veeam Console entsprechend starte.

Ich habe keinen eigenen Linux Client oder ähnliches installiert, das soll alles direkt von Veeam kommen, wie es auch gewünscht und gefordert ist.

Promox ist aktuell, Veeam auch.

Dennoch erhalte ich den Fehler:

Failed to deploy the worker VM: Cannot access a closed Stream.

Worker *Name* test failed: Cannot access al closed Stream.

 

Porst sollten soweit offen sein, keine Chance es fertig zu stellen.

Was ist hier mein Fehler?

 

Andere Proxys, für VMWare gingen ohne probleme.


Danke

Andreas

7 comments

Dynamic
Forum|alt.badge.img+13
  • Veeam Vanguard
  • July 15, 2025

Hallo Andreas,

ich betreibe im Lab zwei Proxmox Hosts, die Worker wurden hier Problemlos deployed.

Können die Worker via DHCP eine Adresse beziehen, oder hast Du hier direkt eine IP vergeben?

 

Meine Proxmox Hosts habe ich via root Credentials hinterlegt. 

 

Wie schaut im Log Bereich aus, unter: C:\ProgramData\Veeam\Backup\Plugins\PVE ? Findest Du dort mehr Informationen die Du mit uns teilen könntest?

 

EDIT: eben noch gefunden, das beschreibt dein Problem ganz gut: Veeam Proxmox VE Worker VM: Cannot access a closed Stream - Thomas-Krenn-Wiki-en

LG Markus


  • Author
  • Comes here often
  • July 15, 2025

Danke für die Info:

den Link von Thomas Kern kannte ich und habe es auch eingestellt.

 

Anbei mal der Inhalt der Log Datei:

 

 

 

2025-07-15 14:39:18.5426 00013 [10768] ERROR | [StorageClient][0HNDQ1TA2MSLH:0000001F]:  <== Request "Get" "https://localhost:6172/api/credentials/ssh/df0eaac7-99a3-4308-a45d-c99cdeaef15d", body: "{}"
2025-07-15 14:39:18.5426 00013 [10768] ERROR | [StorageClient][0HNDQ1TA2MSLH:0000001F]:  ==> Response "Get" "https://localhost:6172/api/credentials/ssh/df0eaac7-99a3-4308-a45d-c99cdeaef15d", "code: 401", duration: "10 msec", body: ""
2025-07-15 14:39:18.5426 00013 [10768] INFO  | [StorageClient][Retry][0HNDQ1TA2MSLH:0000001F]: Authentication data is outdated during request https://localhost:6172/api/credentials/ssh/df0eaac7-99a3-4308-a45d-c99cdeaef15d. Try refresh
2025-07-15 14:39:18.5426 00013 [10768] INFO  | [StorageClient][0HNDQ1TA2MSLH:0000001F]: Update DbProvider token...
2025-07-15 14:39:18.5620 00013 [10768] ERROR | [StorageClient][0HNDQ1TA2MSLH:0000001F]:  <== Request "Get" "https://localhost:6172/api", body: "{}"
2025-07-15 14:39:18.5620 00013 [10768] ERROR | [StorageClient][0HNDQ1TA2MSLH:0000001F]:  ==> Response "Get" "https://localhost:6172/api", "code: 401", duration: "15 msec", body: ""
2025-07-15 14:39:18.5620 00013 [10768] INFO  | [VeeamPlatformAuthenticator][0HNDQ1TA2MSLH:0000001F]: Refresh auth data
2025-07-15 14:39:18.5620 00013 [10768] INFO  | [VeeamPlatformAuthenticator][0HNDQ1TA2MSLH:0000001F]: VeeamAuth parameters: /purpose:DATA /clientCertificateThumbprint:EAEDB9BC87B6F690A6D4043C71E022EF162AAC38 /platformId:{01208ee8-47fe-4ea8-8727-5115874da1ad}
2025-07-15 14:39:18.7423 00102 [10768] INFO  | [VeeamPlatformAuthenticator][0HNDQ1TA2MSLH:0000001F]: VBR auth token claims: unique_name: NT AUTHORITY\SYSTEM, purpose: DATA, platform_id: 01208ee8-47fe-4ea8-8727-5115874da1ad, user_sid: S-1-5-18, session_id: c2d00f2d-1081-49b4-b278-8aeb6d3a3a72, is_backup_administrator: True, role: Veeam Backup Administrator, nbf: 1752583158, exp: 1752584058, iat: 1752583158, iss: Veeam, aud: Veeam
2025-07-15 14:39:18.7423 00013 [10768] INFO  | [StorageClient][0HNDQ1TA2MSLH:0000001F]: Public JWT token part: eyJhbGciOiJSUzI1NiIsImtpZCI6IkIxMTk3OEVGOUVCRDlGNDQxOUQ1NTZBQjIxOUIyRUFCOTI0QTFGOUIiLCJ0eXAiOiJKV1QifQ.eyJ1bmlxdWVfbmFtZSI6Ik5UIEFVVEhPUklUWVxcU1lTVEVNIiwicHVycG9zZSI6IkRBVEEiLCJwbGF0Zm9ybV9pZCI6IjAxMjA4ZWU4LTQ3ZmUtNGVhOC04NzI3LTUxMTU4NzRkYTFhZCIsInVzZXJfc2lkIjoiUy0xLTUtMTgiLCJzZXNzaW9uX2lkIjoiYzJkMDBmMmQtMTA4MS00OWI0LWIyNzgtOGFlYjZkM2EzYTcyIiwiaXNfYmFja3VwX2FkbWluaXN0cmF0b3IiOiJUcnVlIiwicm9sZSI6IlZlZWFtIEJhY2t1cCBBZG1pbmlzdHJhdG9yIiwibmJmIjoxNzUyNTgzMTU4LCJleHAiOjE3NTI1ODQwNTgsImlhdCI6MTc1MjU4MzE1OCwiaXNzIjoiVmVlYW0iLCJhdWQiOiJWZWVhbSJ9
2025-07-15 14:42:36.2116 00013 [10768] INFO  | [EntitiesSynchronizer]: Starting full Cluster "d203819a-4e9e-317d-5a36-269807f537b2" rescan within Session 097c78cf-1f74-4c8c-a73d-c48ce6b31222
2025-07-15 14:42:36.2116 00123 [10768] INFO  | [ProxmoxNode][pmox-2][4c4c4544-0048-4d10-8056-c7c04f325332][VM Cache]: Scanning VMs...
2025-07-15 14:42:36.2116 00123 [10768] INFO  | [ProxmoxNode][pmox-2][4c4c4544-0048-4d10-8056-c7c04f325332][VM Cache]: Updating the VMs list...
2025-07-15 14:42:36.2116 00124 [10768] INFO  | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332][VM Cache]: Scanning VMs...
2025-07-15 14:42:36.2116 00124 [10768] INFO  | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332][VM Cache]: Updating the VMs list...
2025-07-15 14:42:36.8170 00123 [10768] INFO  | [ProxmoxNode][pmox-2][4c4c4544-0048-4d10-8056-c7c04f325332][VM Cache]: Updating the received 6 VMs
2025-07-15 14:42:36.8170 00123 [10768] INFO  | [ProxmoxNode][pmox-2][4c4c4544-0048-4d10-8056-c7c04f325332][VM Cache]: VM scan summary: discovered VMs: 6, new VMs: 0, updated VMs: 0, removed VMs: 0
2025-07-15 14:42:37.0715 00124 [10768] INFO  | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332][VM Cache]: Updating the received 9 VMs
2025-07-15 14:42:37.0715 00124 [10768] INFO  | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332][VM Cache]: VM scan summary: discovered VMs: 9, new VMs: 0, updated VMs: 0, removed VMs: 0
2025-07-15 14:44:39.6703 00013 [10768] INFO  | [WorkerManager][0HNDQ1TA2MSMA:00000002]: CreateWorkerAsync begin, Id: 8c1ca170-2c2f-4dea-8b11-5413a21a0951
2025-07-15 14:44:39.6703 00013 [10768] INFO  | [WindowsCertificateStore][0HNDQ1TA2MSMA:00000002]: Finding certificate with friendlyName "Veeam self-signed certificate for Proxmox VE workers"
2025-07-15 14:44:39.6703 00013 [10768] INFO  | [WindowsCertificateStore][0HNDQ1TA2MSMA:00000002]: Certificate has been found: "Service certificate: CN=IGZBAK01.igzev.intern, O=Veeam Software, OU=Veeam Software. EffectiveDate: 11.11.2024 12:10:37. ExpirationDate: 11.11.2034 12:10:37. Thumbprint:7682392E8BF012D0F34A06AC0A77A7E5ECE3DFC9"
2025-07-15 14:44:39.6703 00013 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04][UpdatesManager][0HNDQ1TA2MSMA:00000002]: UpdatesManager created with settings {"ProductPackageName":"veeamworkerpve","CurrentVersion":"1.0","CheckUpdaterStateInterval":"00:00:10","WaitUpdaterStateTimeout":"00:10:00","CheckInstallProgressInterval":"00:00:05","InstallUpdatesTimeOut":"01:00:00","LocalOrigins":{"10ca1a6e-de9b-4b92-bd00-176e96b59e8a":{"Id":"10ca1a6e-de9b-4b92-bd00-176e96b59e8a","Name":"worker IGZBAK04, 8c1ca170-2c2f-4dea-8b11-5413a21a0951","PackagesNames":["veeamworkerpve"]}}}
2025-07-15 14:44:39.6703 00013 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04][0HNDQ1TA2MSMA:00000002]: Save worker 8c1ca170-2c2f-4dea-8b11-5413a21a0951 data to DB
2025-07-15 14:44:39.7717 00013 [10768] INFO  | [WorkerManager][0HNDQ1TA2MSMA:00000002]: CreateWorkerAsync end, Id: 8c1ca170-2c2f-4dea-8b11-5413a21a0951
2025-07-15 14:44:41.3790 00100 [10768] INFO  | [TaskManager][0HNDQ1TA2MSMA:00000003]: Initiate iteration for task queue processor
2025-07-15 14:44:41.5205 00131 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Changed "worker IGZBAK04, 8c1ca170-2c2f-4dea-8b11-5413a21a0951" state from Configured to Preparing
2025-07-15 14:44:41.5205 00131 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Save worker 8c1ca170-2c2f-4dea-8b11-5413a21a0951 data to DB
2025-07-15 14:44:41.5479 00131 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Testing the worker IGZBAK04
2025-07-15 14:44:41.5479 00131 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Deploying a worker VM
2025-07-15 14:44:41.5479 00131 [10768] INFO  | [WindowsCertificateStore]: Finding certificate with friendlyName "Veeam self-signed certificate for Proxmox VE workers"
2025-07-15 14:44:41.5479 00131 [10768] INFO  | [WindowsCertificateStore]: Certificate has been found: "Service certificate: CN=IGZBAK01.igzev.intern, O=Veeam Software, OU=Veeam Software. EffectiveDate: 11.11.2024 12:10:37. ExpirationDate: 11.11.2034 12:10:37. Thumbprint:7682392E8BF012D0F34A06AC0A77A7E5ECE3DFC9"
2025-07-15 14:44:41.5479 00131 [10768] INFO  | [WorkersCertificateManager]: Loaded parent certificate with thumbprint "7682392E8BF012D0F34A06AC0A77A7E5ECE3DFC9"
2025-07-15 14:44:42.5645 00131 [10768] INFO  | [WorkersCertificateManager]: Created worker certificate with thumbprint "5B716FCFB38A7ADB33B7E075096F307A6C283F64"
2025-07-15 14:44:42.5645 00131 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Cloud init config for worker IGZBAK04, 8c1ca170-2c2f-4dea-8b11-5413a21a0951 #cloud-config
hostname: IGZBAK04
manage_etc_hosts: true
growpart:
  mode: auto
  ignore_growroot_disabled: true
write_files:
  - path: /etc/ssh/sshd_config
    content: |-
      PasswordAuthentication yes
      Subsystem  sftp    /usr/libexec/openssh/sftp-server
      #PermitRootLogin prohibit-password
  - path: /opt/VeeamBackupWorker/worker-initial.json
    content: |-
      {
        "WorkerId": "8c1ca170-2c2f-4dea-8b11-5413a21a0951"
      }
  - path: /opt/VeeamBackupWorker/openssl/certificate.pem
    content: |-
      -----BEGIN CERTIFICATE-----
      MIIFrDCCA5SgAwIBAgIVAK+1rXe7OHA4H2Kj2kDa/4YQt+/xMA0GCSqGSIb3DQEB
      CwUAMFIxFzAVBgNVBAsTDlZlZWFtIFNvZnR3YXJlMRcwFQYDVQQKEw5WZWVhbSBT
      b2Z0d2FyZTEeMBwGA1UEAxMVSUdaQkFLMDEuaWd6ZXYuaW50ZXJuMB4XDTI0MTEx
      MTExMTAzN1oXDTM0MTExMTExMTAzN1owRTEXMBUGA1UECxMOVmVlYW0gU29mdHdh
      cmUxFzAVBgNVBAoTDlZlZWFtIFNvZnR3YXJlMREwDwYDVQQDEwhJR1pCQUswNDCC
      AiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAMXI1SIkQLDswKbjYz4QSTLo
      I1Aa3kVt919hZ3+qNIeGDMUKv1CMYFpjCiJoesypYnlWgW5yrAklNB+iVsfSzAbA
      LJwKXKvS4mZxxSD7XPcYTviQwRD1dNRPdAHJy1B+FmLX2ZNf/d5UTwMAKZGHf/hd
      GJsepVXTWbqhw4p+QfOVJ5lcZ/zEHiMxmrX5loD0rAWyizycQ8j8w53w8N04pKOP
      kEsTJQQLDhyp1WLMYnjoMqUGhp6GLCCmlXXOoV1wF22DDT2pTSFtlA6e9EZj5Wpm
      eaMDVJogakPIupkMlGKuJb0fVBHWrcjykzeKekSnY/G/WT1kO8fGme9KZ9nGbswu
      84Y62DrM1C5gGDRTXJwxCEYTZHNgQ+kpOBzmmNZ4ksc2zOmR99GpEba0bBE+vKxD
      7JbenNUefYUDh9NufF521M6iQuZcJ16J1ERmC/UueT/sdSQlg/MXMm0qIcnG6BKH
      8aDK43RQhWvWDGWltoU5paxLsolHw1bt9xBIqoWSy0f5St4Y9HjvDzqIOYX7+16K
      AUccTmytmVqKJi19T0FaplgWwSy0TLcA/98mh3269C1/C/EJ2P2UAIxzO9fSIAL/
      qdOfrWe/6Mz03aeIoT4DDuq0UYOhZlX9aomr2lzV60HhgS8a3nBVALqcDb2iHJ+V
      4IgsbxmvDmyyLQyH2b6VAgMBAAGjgYUwgYIwCwYDVR0PBAQDAgeAMBMGA1UdJQQM
      MAoGCCsGAQUFBwMBMB8GA1UdIwQYMBaAFMXul166T1DGlhhqwbYtjp2KM5+uMAkG
      A1UdEwQCMAAwHQYDVR0OBBYEFA/bhF7QVCx9zkPEQBw1/qvh8H9OMBMGA1UdEQQM
      MAqCCElHWkJBSzA0MA0GCSqGSIb3DQEBCwUAA4ICAQA51EFXFJrT4C3Rbx9l/ZHw
      ujgeCM4E7QeE0d1sJJg7ml66H5PGzQrP/2v8mfWscs4gvXmiCKFoqNAfrx9WD452
      yrGPnte0HPaBM6aqi1MmslT55WFshHSQQzHLgcbfOI0bv5u+X3cIRX+WWcsxOZQf
      8DdZNXnq2RTrIQca0r4K9DC9VM9VdiBv4IvsgnBEqG6as5rmvLxy+VBJ3VeDsQQa
      LWv7BkxV1RBvd2UzkUi0Af85eWQA7B+5KW9pSZ4zkiySCWdWXBG6M2LnG/58ovO6
      Ral9LMnoVyKqLL0m/mbYvnrLQZfbQRccGvxcNeMaQDyHocWNqu+l5PZc3oWyNZ39
      tKegdarAlpvHdwuRCfoWfwOYBLX0ksJdCZft0IWMbszgSvEagkXkaFQtI24MH6rh
      4N3UzJxchYid43Y6pelEfoOHp9Qg79C20ai8Z0cmQQUohVQM+D/Qeqrz9bhdCPjc
      m9qmB87daINyNVL2oABE5SA+5DlKG0fMjVDKzIs5ujG43iuMbulq93Ty66F2XyiR
      9/YJWN6ae3dpmh10W7GdRjd52oV/HjGSdvfNE2BBiQKwvIqEAuj1lTTHF8XKAYjs
      BpVGEgFERJFSD9dVvYbKtKlck4RvyAUwxIJQ2iAefUUjdFLm2McR7wIXPT1ZCf1h
      5rOU8Wi5GLsRKBVv55Iv5Q==
      -----END CERTIFICATE-----
  - path: /opt/VeeamBackupWorker/openssl/certificatePassword
    content: |-
      ***
  - path: /opt/VeeamBackupWorker/openssl/privateKey.pem
    content: |-
      ***
  - path: /etc/veeam-updater/settings.yaml
    content: |+
      notificationsToProductEnabled: false
      internetConnectionEnabled: true
      overwriteSystemProxy: false
      proxyExclude: []
  - path: /etc/cloud/cloud.cfg.d/90_dpkg.cfg
    content: |-
      datasource_list: [ None ]
  - path: /opt/VeeamBackupAgent/network/network_config.yml
    content: |+
      interfaces:
        - name: eth0
          type: ethernet
          state: up
          ipv4:
            enabled: true
            dhcp: true
          ipv6:
            enabled: false
      dns-resolver:
        config:
          server: []
runcmd:
  - hostnamectl set-hostname IGZBAK04
  - sudo nmstatectl apply /opt/VeeamBackupAgent/network/network_config.yml
  - firewall-cmd --permanent --add-port=19000/tcp
  - firewall-cmd --reload
  - rpm -e veeamproxypve
  - sudo rm /etc/pam.d/veeam-login-policy
  - sudo rm /etc/pam.d/veeam-login-accept-policy
  - sudo rm /etc/pam.d/veeam-pwd-complexity
  - sudo rm /etc/pam.d/sshd
  - sudo sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
  - sudo service sshd restart
  - sudo rm -f -r /var/log/veeam_backup/*
  - sudo bash -c 'export VEEAM_WORKER_SKIP_SERVICE_START=1; rpm -i /opt/veeamworkerpve-*.el*.x86_64.rpm;'
  - sudo rm -f /opt/veeamworkerpve-*.el*.x86_64.rpm
  - sudo chmod 640 /opt/VeeamBackupWorker/openssl/certificate.pem
  - sudo chmod 640 /opt/VeeamBackupWorker/openssl/certificatePassword
  - sudo chmod 640 /opt/VeeamBackupWorker/openssl/privateKey.pem
  - sudo groupdel veeam-admins
  - sudo groupdel veeam-users
  - sudo groupdel veeam-users-mfa
  - rm -f /etc/ssh/sshd_config.d/50-cloud-init.conf
  - sudo touch /etc/cloud/cloud-init.disabled
  - sudo shutdown -h now

2025-07-15 14:44:42.5645 00125 [10768] INFO  | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332]: Image C:\Program Files\Veeam\Plugins\PVE\Service\Images\PveWorker_1.3.0.189.img is actual. Version: 1.3.0.189
2025-07-15 14:44:42.8609 00125 [10768] INFO  | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332]: Starting upload image with version 1.3.0.189
2025-07-15 14:45:01.9493 00013 [10768] ERROR | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332]:  <== Request "Post" "https://pmox-1.oob.igzev.intern:8006/api2/json/nodes/pmox-1/storage/local/upload", body: "{}"
2025-07-15 14:45:01.9493 00013 [10768] ERROR | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332]:  ==> Response "Post" "https://pmox-1.oob.igzev.intern:8006/api2/json/nodes/pmox-1/storage/local/upload", "status: Error", duration: "18 sec 969 msec", body: """"
2025-07-15 14:45:01.9493 00013 [10768] INFO  | [ProxmoxRestClientFactoryBase][Retry]: Retry request after "10 sec". Retry 1/10 for request "https://pmox-1.oob.igzev.intern:8006/api2/json/nodes/pmox-1/storage/local/upload"
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332]:  <== Request "Post" "https://pmox-1.oob.igzev.intern:8006/api2/json/nodes/pmox-1/storage/local/upload", body: "{}"
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [ProxmoxNode][pmox-1][4c4c4544-0048-4e10-804e-c7c04f325332]:  ==> Response "Post" "https://pmox-1.oob.igzev.intern:8006/api2/json/nodes/pmox-1/storage/local/upload", "status: Error", duration: "12 msec", body: """"
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Failed to deploy the worker VM: Cannot access a closed Stream.: System.ObjectDisposedException: Cannot access a closed Stream.
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at System.IO.Strategies.BufferedFileStreamStrategy.CopyToAsync(Stream destination, Int32 bufferSize, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at System.Net.Http.StreamToStreamCopy.CopyAsync(Stream source, Stream destination, Int32 bufferSize, Boolean disposeSource, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: --- End of stack trace from previous location ---
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at System.Net.Http.HttpContent.<CopyToAsync>g__WaitAsync|56_0(ValueTask copyTask)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.ProxmoxBackup.RestClient.ProxmoxRestClient.ThrowResultException(InternalResponse response)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.Vbf.Rest.Common.ApiClient.ApiClientBase.ExecuteAsync[T](RestRequest request, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.ProxmoxBackup.RestClient.ProxmoxRestClient.ExecuteAndGetDataAsync[TResponse](RestRequest request, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.ProxmoxBackup.RestClient.ProxmoxRestClient.UploadImageInternalAsync(String filePath, String nodeId, String storageId, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.ProxmoxBackup.RestClient.Additional.Extensions.ProxmoxRestClientExtensions.UploadImageAsync(ProxmoxRestClient restClient, String filePath, String nodeId, String storageId, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.PlatformService.Plugin.ProxyManagement.ImageManagement.ImageUpdaterBase.<>c__DisplayClass5_0.<<UpdateImagesAsync>b__0>d.MoveNext()
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: --- End of stack trace from previous location ---
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.PlatformService.BackupRestore.Workers.PveSpecificWorkerManager.GetImageNameAsync(ProxmoxNode node, WorkerConfiguration configuration, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.PlatformService.BackupRestore.Workers.PveSpecificWorkerManager.DeployWorkerInstanceAsync(BackupWorker worker, VmAffinity affinity, String cloudInitConfigYaml, CancellationToken cancellationToken)
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.Vbf.WorkerManagement.WorkerManagers.WorkerManager.<>c__DisplayClass123_0.<<DeployVirtualMachineAsync>b__2>d.MoveNext()
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: --- End of stack trace from previous location ---
2025-07-15 14:45:11.9753 00198 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]:    at Veeam.Vbf.TaskManagement.Extensions.ProgressReporterExtensions.PerformAsync[T](IProgressReporterBase reporter, ILogger logger, String startMessage, Func`2 successMessage, Func`2 failMessage, Func`1 payloadTask, Func`2 resultOnFail)
2025-07-15 14:45:11.9784 00131 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Changed "worker IGZBAK04, 8c1ca170-2c2f-4dea-8b11-5413a21a0951" state from Preparing to Configured
2025-07-15 14:45:11.9784 00131 [10768] INFO  | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Save worker 8c1ca170-2c2f-4dea-8b11-5413a21a0951 data to DB
2025-07-15 14:45:12.1734 00131 [10768] ERROR | [Worker][8c1ca170-2c2f-4dea-8b11-5413a21a0951][IGZBAK04]: Worker IGZBAK04 test failed: Cannot access a closed Stream.
 


  • Author
  • Comes here often
  • July 15, 2025

Danke für den Beitrag, den Link vom Kern kannte ich schon und hatte es auch abgearbeitet.

Anbei die Logdatei.


Dynamic
Forum|alt.badge.img+13
  • Veeam Vanguard
  • July 15, 2025

Hi Andreas, ich habe eben mal in das Log geschaut - konnte aber auch nichts finden, was hier weiterhilft. Ich würde zwischendrin schon mal einen Case eröffnen. 
In der Zwischenzeit meldet sich hier vielleicht noch ein Kollege mit einem hilfreichen Vorschlag.

Support Case: KB1771: How to Create a Veeam Support Case

LG Markus


  • Author
  • Comes here often
  • July 17, 2025

Hallo Markus,

danke, das werde ich mal machen.

 

Gruß

Andreas


Dynamic
Forum|alt.badge.img+13
  • Veeam Vanguard
  • July 17, 2025

Moin Andreas,

viel Erfolg, Du kannst uns ja gerne mal mitteilen, was das Ergebnis bzw. die Lösung war.

LG Markus


Dynamic
Forum|alt.badge.img+13
  • Veeam Vanguard
  • July 23, 2025

Guten Morgen Andreas,

bist Du über den Support weitergekommen? Wenn ja, was war die Lösung des Problems? Danke für ein kurzes Feedback

LG Markus