Invalid literal for int() with base 10: ''

Hi,

logged in on ESX-Host as root. Outbound SSH enabled.
Im trying to do the init. Tested with 2 different remote Hosts. One is an old Filer with Scientific Linux 6.8 (SL). The other is a CentOS7.1.1. Both are physical.

At first i tried it with the SL-Host.
Error:
[root@esxi1:/vmfs/volumes/5666f2f6-a0f0b88e-483b-141877458e2c] ./vertical init esx1 sftp://root@10.0.1.61:/var/www/verticalbackup
Vertical Backup 0.3.1
Traceback (most recent call last):
File “”, line 135, in
File “/root/verticalbackup/build/vertical_main/out00-PYZ.pyz/vertical_backup”, line 357, in initCommand
File “/root/verticalbackup/build/vertical_main/out00-PYZ.pyz/vertical_storage”, line 27, in createStorage
ValueError: invalid literal for int() with base 10: ‘’

Then i thought maybe the OS is too old, so i tried the CentOS Host.
Same error:
[root@esxi1:/vmfs/volumes/5666f2f6-a0f0b88e-483b-141877458e2c] ./vertical init esx1 sftp://root@xh02:/var/verticalbackup
Vertical Backup 0.3.1
Traceback (most recent call last):
File “”, line 135, in
File “/root/verticalbackup/build/vertical_main/out00-PYZ.pyz/vertical_backup”, line 357, in initCommand
File “/root/verticalbackup/build/vertical_main/out00-PYZ.pyz/vertical_storage”, line 27, in createStorage

edit: Its ESX 6.0 and we are using the Essentials Plus Kit

Kind regards
RG

Just did a test with a ubuntu14.04 Host. Same error

The format of the storage url is slightly different than that of scp – the colon : is used to specify the port number.

So in your case it should be:

sftp://root@10.0.1.61/var/www/verticalbackup

Use a colon only if the server is running sshd on a different port:

sftp://root@10.0.1.61:222/var/www/verticalbackup

That being said, it should have given a more helpful error message when this happens. I’ll make a fix soon.

Alright, that works. One thing i noticed is that you have to use 2 / at the beginning of the path. So in my example i have to use: sftp://root@10.0.1.61//var/www/verticalbackup but maybe that is normal for sftp.

Thank you very much!

Right, if there is a single / then the remote directory is relative to the home directory. So for an absolute directory you’ll need to use 2.

This bug has been fixed in version 0.3.3.