Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

Thunderbyte

Member

Registered: 2017-10-05

Posts: 6

arithmetic syntax error

Hi all

I get the following error both when running cron or command directly

Command from CRON:

/vmfs/volumes/Datastore1/xsi-dir/xsibackup --time="Mon 20:00|Tue 20:00|Wed 20:00|Thu 20:00|Fri 20:00|Sat 20:00" --backup-point=/vmfs/volumes/Backup --backup-type=running --date-dir=yes --mail-from=xx@xx.xx --mail-to=xx@xx.xx --smtp-srv=mail.xx.xx --smtp-port=587 --smtp-usr=xx --smtp-pwd=xx

Cron Log:
2018-05-15T20:00:06|  --backup-point found at [1m/vmfs/volumes/Backup[0m
---------------------------------------------------------------------------------------------------------------------------------
2018-05-15T20:00:06|  Getting list of all VMs...
---------------------------------------------------------------------------------------------------------------------------------
2018-05-15T20:00:06|  1      SERVER.xx.local   [Datastore1] SERVER.xx.local/SERVER.xx.local.vmx   windows7Server64Guest   vmx-13             
---------------------------------------------------------------------------------------------------------------------------------
2018-05-15T20:00:08|  VMs to backup:
---------------------------------------------------------------------------------------------------------------------------------
2018-05-15T20:00:08|  1      SERVER.xx.local   [Datastore1] SERVER.xx.local/SERVER.xx.local.vmx   windows7Server64Guest   vmx-13             
---------------------------------------------------------------------------------------------------------------------------------
ls: /vmfs/volumes/406984e4-03e13517-bd9f-97387cb15ab7: Input/output error
ls: /vmfs/volumes/5acf14db-5a4338e1-ca54-509a4c7ebfdb: Input/output error
ls: /vmfs/volumes/db650dec-b44f9b39-938a-58ef2d0a6d43: Input/output error
vmfs/volumes/Datastore1/xsi-dir/xsibackup: line 3445: arithmetic syntax error

I get what the error means, datastores mentioned is not accessible. BUT here it comes, I only have theese two Datastores:

/vmfs/volumes/5acf5920-2027ac1b-faef-509a4c7ebfdb     (Datastore1)
/vmfs/volumes/5acf592d-9192fd4e-9148-509a4c7ebfdb    (Backup)

Where does XSI gets these Datastores from?

I rebooted the Server completly and re-installed XSI backup twice. The only thing I can think of is completly reinstalling vmware esxi. But wanted to ask here first if theres a solution to this

Last edited by Thunderbyte (2018-05-16 08:46:59)

admin

Administrator

Registered: 2017-04-21

Posts: 2,072

Re: arithmetic syntax error

You are considering a derived error as the most significant one, when it's right the opposite.
Your datastores are disconnected from the host, and you are getting this errors:

ls: /vmfs/volumes/406984e4-03e13517-bd9f-97387cb15ab7: Input/output error
ls: /vmfs/volumes/5acf14db-5a4338e1-ca54-509a4c7ebfdb: Input/output error
ls: /vmfs/volumes/db650dec-b44f9b39-938a-58ef2d0a6d43: Input/output error

The arithmetic syntax error is just a consequence of your devices being offline, check your switch and cables.

Thunderbyte

Member

Registered: 2017-10-05

Posts: 6

Re: arithmetic syntax error

ls: /vmfs/volumes/406984e4-03e13517-bd9f-97387cb15ab7: Input/output error
ls: /vmfs/volumes/5acf14db-5a4338e1-ca54-509a4c7ebfdb: Input/output error
ls: /vmfs/volumes/db650dec-b44f9b39-938a-58ef2d0a6d43: Input/output error

theese datastores ID's do not exist, I only have two

/vmfs/volumes/5acf5920-2027ac1b-faef-509a4c7ebfdb     (Datastore1)
/vmfs/volumes/5acf592d-9192fd4e-9148-509a4c7ebfdb    (Backup)

And theese two are surely not offline. The VM is up and running from one and with WinSCP I can browse the Backup one perfectly (including creating and deleting files I upload with WinSCP)..

[img=WinSCP]https://www.thunderbyte.ch/esxi_datastores.png[/img]

Last edited by Thunderbyte (2018-05-16 09:37:48)

admin

Administrator

Registered: 2017-04-21

Posts: 2,072

Re: arithmetic syntax error

You are getting some nasty gross errors from your server. This uncontrolled errors are affecting XSIBackup execution. If you think everything is OK with your ESXi host, then we have nothing else to say.

Thunderbyte

Member

Registered: 2017-10-05

Posts: 6

Re: arithmetic syntax error

I could finally resolve the issue:

cd /vmfs/volumes
ls

-> Resulted in the same error:
ls: /vmfs/volumes/406984e4-03e13517-bd9f-97387cb15ab7: Input/output error
ls: /vmfs/volumes/5acf14db-5a4338e1-ca54-509a4c7ebfdb: Input/output error
ls: /vmfs/volumes/db650dec-b44f9b39-938a-58ef2d0a6d43: Input/output error

esxcli storage filesystem list
-> Resulted also in an error, without displaying the list:
Cannot open volume:

Running this command fixed everything:
esxcli storage filesystem rescan

Both, "esxcli storage filesystem list" and "ls" resulted in no errors afterwards and XSI Backup started to work again too

Last edited by Thunderbyte (2018-08-07 08:48:03)

admin

Administrator

Registered: 2017-04-21

Posts: 2,072

Re: arithmetic syntax error

Thank you for the feedback.
You are the only user reporting this error. You probably removed some device/s and you didn't refresh from the vSphere Client.
We will nevertheless consider adding this command into XSIBackup to prevent this situation.

Thunderbyte

Member

Registered: 2017-10-05

Posts: 6

Re: arithmetic syntax error

I did a search before posting this but did not find a solution in the two posts describing the same error

[url]https://33hops.com/forum/viewtopic.php?id=106[/url]
[url]https://33hops.com/forum/viewtopic.php?id=129[/url]

I honestly cannot tell what exactly caused the issue, as the server never had 3 datastores. However I'm glad I could fix it without reinstalling everything

admin

Administrator

Registered: 2017-04-21

Posts: 2,072

Re: arithmetic syntax error

The "arithmetic syntax error" is a symptom, not the disease, just as coughing is not a disease on its own. Those two posts are treating different issues from older versions.

We will try to work this eventual kind of issues around by silently making XSIBackup rescan datastores, although this could be a drawback for most users not having this issue due to the time the rescan might take to complete.

Things don't pop out of nowhere and computers are still not smart enough to cheat us, so that must have come from some previous operation.