Avamar: O backup do Avamar VMware falha aleatoriamente com o ERRO: 0237 Não é possível criar thread (11) Recurso temporariamente indisponível

Summary: O backup do Avamar VMware falha aleatoriamente com o ERRO: 0237 Não é possível criar thread (11) Recurso temporariamente indisponível após o upgrade para o proxy 19.3.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

  • Implementando o proxy versão 19.3 usando o proxy deployment manager.


  • Ao usar o proxy versão 19.3, os backups aleatórios de imagem da VM falham mostrando as seguintes mensagens de erro: 
    [VcbImageBackupAssistThread]  ERROR: <0237> Cannot create thread (11) Resource temporarily unavailable
avvcbimage Info <43574>: vcApiVersion 6.5
avvcbimage Info <43575>: VSphereHTTP::vcVersion65 will be true
avvcbimage Info <42137>: job type = 4
.
avvcbimage Info <16041>: VDDK:VixDiskLib: Advanced transport plugin /usr/lib/vmware-vix-disklib/lib64/libdiskLibPlugin.so was successfully loaded into vixDiskLib.
avvcbimage Info <16041>: VDDK:VixDiskLib: Enabling advanced transport modes.
[VcbImageBackupAssistThread]  ERROR: <0001> threadimpl::runthread Exception Resource temporarily unavailable
avvcbimage Info <9772>: Starting graceful (staged) termination, MCS cancel (wrap-up stage)

Cause

  • A contagem de tarefas do proxy excedeu o valor (512) definido para "TasksMax", mesmo que o valor esteja definido como "infinito" no arquivo "/etc/systemd/system/multi-user.target.wants/avagent.service", conforme abaixo: 
    <Proxy_Name>:~ # less /etc/systemd/system/multi-user.target.wants/avagent.service
.
[Service]
ExecStart=/etc/init.d/avagent start
ExecStop=/etc/init.d/avagent stop
KillMode=process
Restart=on-abort
RemainAfterExit=yes
TasksMax=infinity
  • Além disso, ao verificar a contagem de tarefas do serviço "vami-sfcb.service", ele mostra a contagem correta de tarefas conforme abaixo: 
    <Proxy_Name>:~ # systemctl status vami-sfcb.service
  vami-sfcb.service - LSB: Small Footprint CIM Broker Service
   Loaded: loaded (/etc/init.d/vami-sfcb; disabled; vendor preset: disabled)
   Active: active (running) since <DAY> <yyyy-mm-dd hh:mm:ss UTC; # days ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 16 (limit: 512)
   CGroup: /system.slice/vami-sfcb.service
              6873 /opt/vmware/sbin/vami-sfcbd -d
              6878 /opt/vmware/sbin/vami-sfcbd -d
              6882 /opt/vmware/sbin/vami-sfcbd -d
              6883 /opt/vmware/sbin/vami-sfcbd -d
              6892 /opt/vmware/sbin/vami-sfcbd -d
              6901 /opt/vmware/sbin/vami-sfcbd -d
             11366 /usr/local/avamarclient/bin/avagent.bin --listenport=28009...
  • Mas ao verificar o número de contagem de tarefas de "avagent.service", ele mostra o valor "0", o que significa que não está contando tarefas corretamente conforme abaixo: 
    <Proxy_Name>:~ # systemctl status avagent.service
  avagent.service - Avamar Unix backup/restore agent (avagent)
   Loaded: loaded (/usr/lib/systemd/system/avagent.service; enabled; vendor preset: disabled)
   Active: active (exited) since <Day> <yyyy-mm-dd hh:mm:ss UTC; # ago
 Main PID: 1286 (code=exited, status=0/SUCCESS)
    Tasks: 0
   CGroup: /system.slice/avagent.service
             1476 /usr/local/avamarclient/bin/avagent.bin --listenport=28009 ...

Resolution

  1. No proxy, verifique se o valor de "TasksMax" está definido como "infinito" no arquivo "/etc/systemd/system/multi-user.target.wants/avagent.service", conforme abaixo: 
    <Proxy_Name>:~ # less /etc/systemd/system/multi-user.target.wants/avagent.service
.
[Service]
ExecStart=/etc/init.d/avagent start
ExecStop=/etc/init.d/avagent stop
KillMode=process
Restart=on-abort
RemainAfterExit=yes
TasksMax=infinity
  2. Ative o serviço "vami-sfcb" no proxy conforme abaixo: 
    <Proxy_Name>:~ # systemctl enable vami-sfcb
Synchronizing state of vami-sfcb.service with SysV init with /usr/lib/systemd/systemd-sysv-install...
Executing /usr/lib/systemd/systemd-sysv-install enable vami-sfcb
Created symlink from /etc/systemd/system/multi-user.target.wants/vami-sfcb.service to /usr/lib/systemd/system/vami-sfcb.service.
  3. Reinicialize o proxy usando o comando "reboot".
  4. Verifique se o serviço "avagent.service" está mostrando a contagem de tarefas correta e não zero , como abaixo: 
    <Proxy_Name>:~ # systemctl status avagent.service
  avagent.service - Avamar Unix backup/restore agent (avagent)
   Loaded: loaded (/usr/lib/systemd/system/avagent.service; enabled; vendor preset: disabled)
   Active: active (exited) since <Day> <yyyy-mm-dd hh:mm:ss UTC; # ago
 Main PID: 1286 (code=exited, status=0/SUCCESS)
    Tasks: 16
   CGroup: /system.slice/avagent.service
             1476 /usr/local/avamarclient/bin/avagent.bin --listenport=28009 ...

Affected Products

Avamar

Products

Avamar, Avamar Client for VMware
Article Properties
Article Number: 000173642
Article Type: Solution
Last Modified: 07 Nov 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.