Avamar:Avamar VMware 备份随机失败并显示错误:0237 无法创建线程 (11) 资源暂时不可用

Summary: Avamar VMware 备份随机失败并显示错误:0237 无法创建线程 (11) 升级到代理 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.

Symptoms

  • 使用代理部署管理器部署代理版本 19.3。


  • 使用代理版本 19.3 时,随机虚拟机映像备份失败,并显示以下错误消息:
    [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

  • 代理任务计数超出了为“TasksMax”设置的值 (512),即使该值在文件“/etc/systemd/system/multi-user.target.wants/avagent.service”中设置为“infinity”,如下所示:
    <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
    	
  • 此外,在从服务“vami-sfcb.service”检查任务计数时,它显示正确的任务计数,如下所示:
    <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...
    	
  • 但是,当从“avagent.service”检查任务计数数时,它显示“0”值,这意味着它没有正确计数任务,如下所示:
    <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. 在代理上,验证文件“/etc/systemd/system/multi-user.target.wants/avagent.service”中的“TasksMax”值设置为“infinity”,如下所示:
    <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. 在代理上启用服务“vami-sfcb”,如下所示:
    <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. 使用“reboot”命令重新启动代理。
  4. 验证服务“avagent.service”是否显示正确的任务计数,而不是 ,如下所示:
    <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.