#1 2017-06-13 21:25:10

wowbagger
Member
Registered: 2017-05-11
Posts: 23

Exitcode 137 but seems ok?

Hi,

When running a backup the exit code is 137. I also notice the "killed" output right at the end.

Output:

[admin@pollux:/vmfs/volumes/56a64f9f-a754d740-20c1-000af78e7284/xsi-dir] ./xsibackup --backup-point=/vmfs/volumes/datastore1/ESX_BACKUP_LOCAL/  --backup-how=cold  --backup-type=custom  --backup-vms="DILEWEB0001" --date-dir=no

#####################################################################################
#                                                                                   #
#  (c) XSIBACKUP-FREE 9.0.1 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com   #
#                                                                                   #
#####################################################################################

XSIBackup PID: 1810763                                      pollux.intra.*****.com
Tue, 13 Jun 2017 19:49:41 +0000                    IPv4: 192.168.20.50/255.255.255.0
VMware ESXi 6.0.0 build-2494585                   (c) Rsync 3.1.0 as opt. dependency

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Found --backup-point at [ /vmfs/volumes/datastore1/ESX_BACKUP_LOCAL/]
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
E-mail Warnings
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The e-mail report will not be sent because of the followig reasons:
The --mail-from string has not been set
The --mail-to string has not been set
The --smtp-srv string has not been set
The --smtp-port string has not been set
The --smtp-usr string has not been set, you need --smtp-usr if --smtp-auth is other than -none-
The --smtp-pwd string has not been set, you need --smtp-pwd if --smtp-auth is other than -none-
Getting list of all VMs...
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
186    DILEWEB0001             [datastore1] DILEWEB0001_1/DILEWEB0001_1.vmx                   windows7Server64Guest   vmx-11    Application & Webserver (ACC + PRD)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
VMs to backup:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
186    DILEWEB0001             [datastore1] DILEWEB0001_1/DILEWEB0001_1.vmx                   windows7Server64Guest   vmx-11    Application & Webserver (ACC + PRD)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Needed room: 80 Gb.
Available room: 102 Gb.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Excerpt
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
VM [DILEWEB0001] was already in an Off state
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Alert: Windows 64 bit OS detected on MBR partition, quiescing disabled
Alert: double check that your backups are being made properly if you use Windows Server
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Syncronizing config files
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Backing up virtual disks...
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
scsi0:0.fileName = "/vmfs/volumes/56a64f9f-a754d740-20c1-000af78e7284/DILEWEB0001/DILEWEB0001.vmdk"
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/56a64f9f-a754d740-20c1-000af78e7284/DILEWEB0001/DILEWEB0001.vmdk'...
Clone: 100% done.
The ESXi configuration was saved to "/vmfs/volumes/datastore1/ESX_BACKUP_LOCAL/"
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No errors detected in backup
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Backup finished
Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup
Killed
[admin@pollux:/vmfs/volumes/56a64f9f-a754d740-20c1-000af78e7284/xsi-dir] echo $?
137
[admin@pollux:/vmfs/volumes/56a64f9f-a754d740-20c1-000af78e7284/xsi-dir]

Offline

#2 2017-06-13 21:46:20

Daniel
Moderator
Registered: 2017-04-22
Posts: 60

Re: Exitcode 137 but seems ok?

XSIBackup uses a function to terminate itself and make sure no remains or children processes are left in memory. Return codes above 128 refer to signalling thus, that return code probably has to do with the kill -9 signalling. I used the word probably, because ESXi is a propietary system, and although it resembles Linux and other *NIX systems, things don't necessarily are they way they seem to be, in this case it is highly probable though.

Offline

#3 2017-06-13 21:59:38

wowbagger
Member
Registered: 2017-05-11
Posts: 23

Re: Exitcode 137 but seems ok?

Ok, I understand. Generating errors by hand always returns exitcode 137 so I think I cannot get the actual code like this.
I'll process the last lines of the output to catch possible errors.

Thanks!

Offline

#4 2017-06-13 22:49:55

Daniel
Moderator
Registered: 2017-04-22
Posts: 60

Re: Exitcode 137 but seems ok?

XSIBackup catches almost any possible error, at least any relevant error in order to ensure a reliable backup. You can be sure that if anything goes wrong during the backup process, you'll have it reflected in the e-mail report.

You can also use XSIBACKUP-PRO's --certify-backup option, which will calculate and compare checksums of every disk, that will give you 100% confidence.

Offline

Board footer