I just installed the XSIBACKUP-FREE and tried to run it but received the following error:
/vmfs/volumes/datastore1/xsi-dir/xsibackup: line 490: syntax error: unexpected "&"
This is on a fresh ESXi 6.7 U2
Last edited by CharlieUk (2019-04-25 08:34:30)
Same error today. Must be ESXI 6.7 U2 i installed. A couple of days ago i was running backups just fine on U1.
Last edited by fuzzyduck (2019-04-25 08:51:42)
Thanks for mentioning the "U2" rather important detail, I forgot to mention it. Edited.
There's what seems to be a bug in the bash interpreter shipped with ESXi 6.7 U2. We have developed a solution as XSIBackup-Pro 11.3.0, but it's still in validation phase. In this post we treat the matter and offer a workaround.
We recommend that you avoid ESXi 6.7.0 U2 until VMWare releases a patch. If you can't skip this build and you are a Pro user, you can try XSIBACKUP-PRO 11.3.0, it's working quite well for us so far. Write to support to ask for it.
Thanks, sadly I am not a Pro user and cannot revert back to U1 because I installed U2 as fresh install so I guess I am out of luck.
Thank you anyways.
is it a certain VIB from U2 we can roll-back?
You can't just download a binary and put it into your ESXi server. Please download latest version to fix your issue.
Thank you for the reply.
As a terminal novice i give up for now. Ill wait for a bugfix.
Why don't you just use a more stable ESXi version: 5.5, 6.0, 6.5, 6.7 U1
i just got in at 6.7. Patched to U1 and U2 now. I have never noticed anything unstable.
I could roll back to U1 though.
in my case, is there a way to go to U1 without a complete reinstall?
As you dont have a previous build to roll back to, i dont think so. But better let someone answer with more experience than me
Well, there isn't really something that could be considered a "complex install". ESXi installs in some minutes. If you have some config backup (XSIBackup does them by default), you just need to reinstall ESXi preserving your datastores, then just unzip the contents of the server config backup and overwrite the /etc directory, that's all.
You can also use the built in commands. Copy the config backup to the temp dir and use the vim-cmd utility to restore it:
vim-cmd hostsvc/firmware/restore_config /tmp/backup-file.tgz
It's a pretty straight procedure that works like a charm. Just as long as you install the same ESXi version that the backup corresponds to, you won't have any problem.
Thank you very much.
I'll have to tread carefully here since it's a downgrade and not an upgrade. And of course, I do not have a backup in case things go nasty.
Also, an update came out today but I do not think it addresses the issue: (c)VMWare (c)ESXi 6.7 U2 patch
i rolled back to U1 and xsi is working again.
thx for the help.
VMWare released a patch for this bug.
(c)VMWare patch for the Bash interpreter
Nevertheless, for goodness sake!, don't use in production some OS that just came out...
We sometimes use metaphores, gags or funny stories like being the "Caesars food taster", but this is something serious.
Nobody with some minimum experience and know how will put into production some OS that has been released "the day before".
Use some stable and well known version, most stable ESXi version from our experience is 5.5, although 6.0 and 6.5 have been out long enought to have some guaratees about its stability too.
This is a general comment, if you were just testing 6.7.0 U2, then this is obviously not for you.
Dont worry, Im just a parttime geek with a homebrew esxi server running on a consumer board with non ECC-RAM
Honestly, I had to reinstall ESXi and completely dismissed the fact the U2 is so young. Kind of a click download, install approach. I get to pay the price for not being more diligent.
That said, this is a home lab machine so I suppose I will need to reinstall ESXi completely with U1 as suggested to get this working.
By the way, I tried installing the latest patch (Build 13473784) and unfortunately that made no difference.
Last edited by CharlieUk (2019-05-03 05:59:48)
Pro users may write to support to request a working version, which basically consists in XSIBackup running on its own shell. Free users should not worry much, just wait for VMWare to fix the issue.
ESXi is still the best hypervisor by far, but this guys at VMWare are going downhill lately, you can tell a "disturbance in the force" at their tech HQ ;-)
Not fixed in Build 13644319 (4/15) either. I don't think VMware will consider this as a bug - at least not an important one. Are you releasing a new XSIBackup version soon, to workaround the issue then?
Yes, we will have no other choice than releasing a new version with some older version of the very ESXi Hypervisor shell interpreter. We have tested it for quite a long time now and it works well with ESXi 6.7.0 U2.
Nevertheless using a version with a patch for an underlying bug is not something that we'll recommend our users doing. Not because XSIBackup won't work well, which we have tested quite thoroughly so far, but because that bug may be the source of other problems.
Taking on account that v. 6.7.0 U2 has accumulated a number of critical bugs and a high number of patches so far and that some are still pending, anybody using this version in production is playing russian roulette.
Previous versions from 5.5 are quite stable, especially 5.5, and more recommendable than 6.7.0 U2, it makes no sense using 6.7.0 U2 in production
For whatever it's worth, I've installed the latest vmware esxi patchset (ESXi670-201906002) and it had no impact on the 'line 490: syntax error: unexpected "&"' error. The error still happens.
Also, it's worth noting that even using the latest busybox build binary (1.31), from busybox.net, the same error happens. Given that this is even newer than the 1.29 version that ships with ESXi 6.7 U2, to me it indicates that this isn't a bug, but rather the "intended functionality" of busybox.
It could be a bug that propagated from busybox to ESXi bundle.
A $ sign token between double quotes must never be interpreted as an escapable literal but as the start token of a variable that must then be expanded inside the double quoted text.