Error code 162 during backup

mvfid · 2021-05-04 06:29:18

I get the following error
::: detail ::: 13.63% done | block 13117 out of 96256 | Done 41.99%
2021-05-03T12:17:25 | Error code 162 at file signal.c, line 162 | Error description: raised SIGTERM (13) (4) in job, num of errors: 13, check error.log
-----------------------------------------------------------------------------------------------------------
Removed current target dir: /volume1/esxi-backups/20210503080422/TH-Procura-W7-DXE10-Dev
-----------------------------------------------------------------------------------------------------------
SIGTERM (13) condition was trapped: check logs for more details
-----------------------------------------------------------------------------------------------------------
Cleaning up...

the /vmfs/volumes/5670f39a-4ffdf3c1-2dfb-0015174b3091/XSI/XSIBackup-DC/var/log/error.log file contains just the line with the error code from above, nothing else related to this VM.

This esxi server does have some HDD issues, data recovery undergoing for those HDDs and as a result 7 VMs are missing files. This is not one of those. So I do have 7 errors above this one like the following
Error code 439 at file esxi.c, line 439 | Error description: .vmx file not present at: /vmfs/volumes/5671067a-3d6f31ef-56ab-0015174b3091/DB-MsSqlServerExpress-19/DB-MsSqlServerExpress-19.vmx, did you delete the VM files?, please fix that

But these are expected for now. I'm in the process of backing up the other VMs but now with this error I am worried that maybe other HDDs/SSDs have data issues as well, so can someone please explain what that error code means?
And if there are any other log files to get more info from? Or things to enable to get extra details?

Thank you.

admin · 2021-05-04 10:08:12

SIGTERM (13) is a BROKEN PIPE error. It means it was the remote side that requested the SSH tunnel to be closed, thus you must inspect the remote side's error log to find out which was the exact cause why the tunnel was shut down.

If you get many of these errors, then that is a sign that your link is not stable. The remote replica or backup are deleted to prevent storing garbage.

(c)XSIBackup does some high level checks on the state of the VMs and will return errors for the most obvious ones. You should keep your server in a good working condition before attempting to perform any kind of backup.

Error 439 in your case, error codes might change, as they are related to the line where they were raised, means that you removed some VM directory manually but you forgot to unregister the VM from the inventory, thus you now have a ghost VM registry pointing nowhere.

mvfid · 2021-05-04 10:50:41

Thank you for the details. I think I know what happened. Checking the synology logs I see that the station entered suspend mode. I have configured it to auto shutdown after 30 mins of inactivity and apparently the backup took longer with no changed chunks to send. I will need to write a script to keep the station "alive" during the backup.

Thanks.

admin · 2021-05-04 11:36:13

You can just make sure that the SSH tunnel keeps open with the SSH Keep Alive options in sshd_config
[url=https://patrickmn.com/aside/how-to-keep-alive-ssh-sessions/]OpenSSH Keep Alive options[/url]

mvfid · 2021-05-04 11:39:26

Thank you, I will try that first.

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

#1 2021-05-04 06:29:18

Error code 162 during backup

#2 2021-05-04 10:08:12

Re: Error code 162 during backup

#3 2021-05-04 10:50:41

Re: Error code 162 during backup

#4 2021-05-04 11:36:13

Re: Error code 162 during backup

#5 2021-05-04 11:39:26

Re: Error code 162 during backup

Board footer