#1 2017-06-05 06:56:58

kadarpik
Member
Registered: 2017-05-10
Posts: 7

rsync: connection unexpectedly closed (0 bytes received so far)

./xsibackup --backup-point=10.0.1.150:22:/vmfs/volumes/BACKUP:F --backup-type=custom --backup
-how=cold  --backup-vms="TULEMYYR" --backup-prog=rsync --mail-from=info@3kgroup.ee --mail-to=tom@3kgroup.ee --smtp-srv=smtp.elisa.ee --smtp-port=25 --smt
p-auth="none" 



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

XSIBackup PID: 135874159                                        localhost.localdomain
Fri, 02 Jun 2017 11:40:05 +0000                    IPv4: 172.17.249.45/255.255.255.0
VMware ESXi 5.5.0 build-1331820                   (c) Rsync 3.1.0 as opt. dependency

--------------------------------------------------------------------------------------------------------------------------------------------------------
Service OpenSSH ready at server 10.0.1.150:22
--------------------------------------------------------------------------------------------------------------------------------------------------------
Warning: Identity file /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa not accessible: No such file or directory.
Warning: Identity file /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa not accessible: No such file or directory.
Mirroring to server 10.0.1.150 port 22
Checking Rsync exists on the other side...
xsibackup-rsync found on the other end (/vmfs/volumes/datastore1/xsi-dir/bin/xsibackup-rsync) and same version. Continuing IP mirror backup...



Info: transfering file [ /vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/TULEMYYR/TULEMYYR.vmdk ]
[TULEMYYR] error: Warning: Identity file /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa not accessible: No such file or directory.
Segmentation fault
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
Removing unused blocks, please wait...
vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576
Hole Punching: 100% done.
Info: transfering file [ /vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/TULEMYYR/TULEMYYR-flat.vmdk ]
Warning: Identity file /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa not accessible: No such file or directory.
Segmentation fault
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
--------------------------------------------------------------------------------------------------------------------------------------------------------
[TULEMYYR] info: bringing VM up again

Offline

#2 2017-06-06 15:19:10

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

Re: rsync: connection unexpectedly closed (0 bytes received so far)

Well, the problem is clear:

Warning: Identity file /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa not accessible: No such file or directory

Have you linked servers via the --link-srv command?

Offline

#3 2017-06-07 09:10:01

kadarpik
Member
Registered: 2017-05-10
Posts: 7

Re: rsync: connection unexpectedly closed (0 bytes received so far)

My servers have RSA keys already generated befor for SSH, is that not enough and should I still use --link-srv command ?

Offline

#4 2017-06-07 10:24:38

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

Re: rsync: connection unexpectedly closed (0 bytes received so far)

You have a missconception about how XSIBACKUP keys work:

- XSIBACKUP uses its own key pair.
- You can use a as many key pairs as you whish for any given server. You could in fact use 10 different applications, each using a different key pair.

So, you must generate XSIBACKUP's key pair by first using the --link-srv=[IP of second server] command

Offline

#5 2017-06-08 06:31:14

kadarpik
Member
Registered: 2017-05-10
Posts: 7

Re: rsync: connection unexpectedly closed (0 bytes received so far)

Key generation was successful, but still get the same error

Info: transfering file [ /vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/TULEMYYR/TULEMYYR.vmdk ]
[TULEMYYR] error: Segmentation fault
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
Removing unused blocks, please wait...
vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576
Hole Punching: 100% done.
Info: transfering file [ /vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/TULEMYYR/TULEMYYR-flat.vmdk ]
Segmentation fault
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 139) at io.c(226) [sender=3.1.0]
--------------------------------------------------------------------------------------------------------------------------------------------------------
[TULEMYYR] info: bringing VM up again


./xsibackup --link-srv=10.0.1.150

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

XSIBackup PID: 137391955                                        localhost.localdomain
No RSA public key found, we will generate one...
The RSA key has been generated.
Enter the remote server root password when prompted.
The RSA key has been added to the authorized_keys file at 10.0.1.150.
Rebooting local SSH service...
SSH login disabled
SSH login enabled
Rebooting remote SSH service...
SSH login disabled
SSH login enabled
Killed

Offline

#6 2017-06-08 12:11:36

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

Re: rsync: connection unexpectedly closed (0 bytes received so far)

Since you were first getting this error:

[TULEMYYR] error: Warning: Identity file /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa not accessible: No such file or directory.

It was totally impossible at that point that Rsync could work over SSH without entering a password.
If you did link servers, Rsync should work. What is the ESXi host version on the other side?, or what kind of server is 10.0.1.150?, can you reach it via SSH?.

The most probable cause for your error is that SSH is simply not working, so please, follow the appropiate steps to verify you do have a working SSH service running on the other end and that you can reach it.

nc 10.0.1.150 22

Should return something like

SSH-2.0-OpenSSH_7.3

If you don't see that response, then your SSH server is not reachable on the other side. If you do receive the adequate response from the SSH service, then connect to the other side by using your XSIBackup RSA key. CD to your xsi-dir directory and run this:

ssh -o StrictHostKeyChecking=no -i xsibackup_id_rsa 10.0.1.150 "echo HELLO WORLD!"

If you don't see a response like this:

HELLO WORLD!

Then, something is blocking your SSH port or the SSH service is down on the other end.

Last edited by Daniel (2017-06-08 15:26:13)

Offline

#7 2017-06-08 16:50:36

kadarpik
Member
Registered: 2017-05-10
Posts: 7

Re: rsync: connection unexpectedly closed (0 bytes received so far)

ssh -o StrictHostKeyChecking=no -i xsibackup_id_rsa 10.0.1.150 "echo HELLO WORLD!"
HELLO WORLD!
/vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/xsi-dir #

This works perfectly!

Offline

#8 2017-06-13 12:50:27

kadarpik
Member
Registered: 2017-05-10
Posts: 7

Re: rsync: connection unexpectedly closed (0 bytes received so far)

Still no solution to get backup working, only ssh works.

Offline

#9 2017-06-13 18:00:16

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

Re: rsync: connection unexpectedly closed (0 bytes received so far)

O.K., let's start again.
When you first said it wasn't working, you were expecting your server key to act as the XSIBackup key, which was not the case, so you were getting this message:

Warning: Identity file /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa not accessible: No such file or directory.

Perfectly normal. After that you corrected the situation and generated a key pair for XSIBackup, right?. We then suggested that you tried your XSIBackup key pair, and you did so, confirming that the the key was working, great!.

Could you explain what is the message error that you are receiving now?, cause the situation has changed since you first posed your question.

Last edited by Daniel (2017-06-13 18:00:56)

Offline

#10 2017-06-14 02:07:00

kadarpik
Member
Registered: 2017-05-10
Posts: 7

Re: rsync: connection unexpectedly closed (0 bytes received so far)

Stopping VM [TULEMYYR]
Powering off VM:
No VMware Tools detected in VM: [TULEMYYR], power-off issued
Sleeping :-o 30 s, waiting for VM to be off
------------------------------------------------------------------------------------------------------------------------------------
Syncronizing config files
------------------------------------------------------------------------------------------------------------------------------------
Remote dir /vmfs/volumes/BACKUP/TULEMYYR deleted to make full backup
[TULEMYYR] info: VMX file copied succesfully
[TULEMYYR] info: VMSD file copied succesfully
[TULEMYYR] info: VMXF file copied succesfully.
[TULEMYYR] info: NVRAM file copied succesfully.
------------------------------------------------------------------------------------------------------------------------------------
Backing up virtual disks...
------------------------------------------------------------------------------------------------------------------------------------
DISK=/vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/TULEMYYR/TULEMYYR.vmdk
------------------------------------------------------------------------------------------------------------------------------------

Info: transfering file [ /vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/TULEMYYR/TULEMYYR.vmdk ]
[TULEMYYR] error: Segmentation fault
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
Removing unused blocks, please wait...
vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576
Hole Punching: 100% done.
Info: transfering file [ /vmfs/volumes/521fe3da-4601510f-cc34-a0481cb86e58/TULEMYYR/TULEMYYR-flat.vmdk ]
Segmentation fault
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 139) at io.c(226) [sender=3.1.0]
------------------------------------------------------------------------------------------------------------------------------------
[TULEMYYR] info: bringing VM up again
------------------------------------------------------------------------------------------------------------------------------------
The ESXi configuration was saved to "10.0.1.150:22:/vmfs/volumes/BACKUP:F"
------------------------------------------------------------------------------------------------------------------------------------
Errors detected in backup, check logs

Offline

#11 2017-06-14 05:33:34

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

Re: rsync: connection unexpectedly closed (0 bytes received so far)

You are getting a plain Rsync error. What is 10.0.1.150?, is it another ESXi host?, can you find this lines at the beggining of your log?

Checking Rsync exists on the other side...
xsibackup-rsync found on the other end (/vmfs/volumes/datastore1/xsi-dir/bin/xsibackup-rsync) and same version. Continuing IP mirror backup...

SSH is working well, as config files are being copied without any error

[TULEMYYR] info: VMX file copied succesfully
[TULEMYYR] info: VMSD file copied succesfully
[TULEMYYR] info: VMXF file copied succesfully.
[TULEMYYR] info: NVRAM file copied succesfully.

Error messages above 128 are related to signalling, error 139 corresponds to SEGFAULT, which means Rsync cannot allocate memory. I would start by rebooting both servers and make sure there isn't any other software that might be making use of the shell memory, which is limited and can get exhausted if running other stuff. You can also increase the stack memory by running this code:

ulimit -s 1024

This other command will return the configured stack memory:

ulimit -a | grep stack

Last edited by Daniel (2017-06-14 05:40:32)

Offline

Board footer