Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

wowbagger

Member

Registered: 2017-05-11

Posts: 41

remote ssh

Hi,

I'm running a crontab on a server that remotely executes a xsibackup script but it generates this error:

seq: invalid option -- '1'
BusyBox v1.20.2 (2012-12-11 11:54:28 PST) multi-call binary.

Usage: seq [-w] [-s SEP] [FIRST [INC]] LAST

Print numbers from FIRST to LAST, in steps of INC.
FIRST, INC default to 1.

        -w      Pad to last with leading zeros
        -s SEP  String separator

Needed room: 164 Gb.
Available room: 618 Gb.
seq: invalid option -- '1'
BusyBox v1.20.2 (2012-12-11 11:54:28 PST) multi-call binary.

Usage: seq [-w] [-s SEP] [FIRST [INC]] LAST

Print numbers from FIRST to LAST, in steps of INC.
FIRST, INC default to 1.

        -w      Pad to last with leading zeros
        -s SEP  String separator

It does work and it backup up the VM's but I'm not sure if I am doing it correctly and never saw that error before.

On ESX host I have a backup_all_vms.sh in the xsi-dir:

./xsibackup \
--backup-type=all \
--backup-point=/vmfs/volumes/ESX_BACKUPS/COBWEB \
--mail-from=email@net.com \
--mail-to=email@net.com \
--subject=Full-Daily-Backup-cobweb\
--smtp-srv=192.168.0.5 \
--smtp-port=25 \
--smtp-auth=none

Executing that on ESX works perfectly.

On a remote host I have a script that does:

ssh -tt -vv -i /home/backup_user/.ssh/id_rsa -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no backup_user@esxhost '/vmfs/volumes/datastore1/xsi-dir/backup_all_vms.sh' >> /root/scripts/logs/backup_esxhost_$DATE.log

When I execute that script while I'm logged on the remote host it works perfectly.
When I schedule it from crontab like that I get the seq error.

Anyone any idea?
Thanks!

Last edited by wowbagger (2017-08-27 17:25:36)

admin

Administrator

Registered: 2017-04-21

Posts: 2,055

Re: remote ssh

Use ssh -v and observe what is in the end being parsed and executed in the remote host, you might need escaping some characters.

zarthan

Member

Registered: 2018-02-25

Posts: 37

Re: remote ssh

Add nohup in front of the ssh command