Unsolved
14 Posts
0
635
Avamar image backups fails with error non-zero exit status 'code 205: plugin error 05
Hi,
All the backup jobs are failing with error code 10055. When checking on the Avamar proxy we are seeing the below errors.
We tried enabling the --debug flag in avvcbimage.cmd and avvcbimageAll.cmd with no much further information. We can ping from proxy to Vcentre and each hosts in vcenter. Also the proxy can reach the avamar server. When the backup jobs are running we can see the snapshot is taken and within few seconds snapshot is removed from the VM as well and failing.. We could see the below from /usr/local/avamarclient/var/avagent.log.
Any idea on what could be wrong here ?
--------------------------
2022-06-14 05:58:09 avagent Info <5964>: Requesting work from
2022-06-14 05:58:09 avagent Info <6686>: Process 6042 (/usr/local/avamarclient/bin/avvcbimage) for workorder XXX_VM_BACKUP-1655186237874 started
2022-06-14 05:58:09 avagent Info <18950>: Starting workorder
2022-06-14 05:58:09 avagent Info <10684>: Setting ctl message version to 3 (from 1)
2022-06-14 05:58:09 avagent Info <16136>: Setting ctl max message size to 268435456
2022-06-14 05:58:19 avagent Info <5964>: Requesting work from
2022-06-14 05:58:19 avagent Info <5264>: Workorder received: sleep
2022-06-14 05:58:19 avagent Info <5996>: Sleeping 60 seconds
2022-06-14 05:58:23 avagent Info <6688>: Process 6042 (/usr/local/avamarclient/bin/avvcbimage) finished (code 205: plugin error 05)
2022-06-14 05:58:23 avagent Warning <6690>: CTL workorder "XXX_VM_BACKUP-1655186237874" non-zero exit status 'code 205: plugin error 05'
2022-06-14 05:58:23 avagent Info <14836>: Unable to find manager for (1001-progress-XXX_VM_BACKUP-1655186237874-e785048e87df26e25a346f2f5eea8e3e8091bd28) while processing stop
2022-06-14 05:59:19 avagent Info <5964>: Requesting work from
2022-06-14 05:59:19 avagent Info <5264>: Workorder received: sleep
2022-06-14 05:59:19 avagent Info <5996>: Sleeping 60 seconds
-------------------
iamtheroot
14 Posts
0
June 14th, 2022 20:00
@ionthegeek Any idea on this ? Unfortunately we don't have an active support for this environment and just need to run for another couple of months.