ssh_exchange_identification: Connection closed by remote host

valshare

Renowned Member
Jun 2, 2009
257
2
83
Germany
Hello,

today i want login into one of our OpenVZ Container. SSH login failed. The i want to login into our PVE Server, but login failed, too with the error message:

Code:
ssh_exchange_identification: Connection closed by remote host

After login failed with ssh, i try to login via http on the server. The Master Server shows: no sync.

In the PVE in Log:

Code:
Sep  8 16:18:49 pvemirror4305 cluster syncronization finished (0.08 seconds (files 0.00, config 0.00))
Sep  8 16:19:49 pvemirror4305 starting cluster syncronization
Sep  8 16:19:49 pvemirror4305 syncing master configuration from '192.168.1.2'
Sep  8 16:19:49 pvemirror4305 syncing master configuration from '192.168.1.2' failed (4 ms) : syncing master configuration from '192.168.1.2' failed (rsync --rsh=ssh -l root -o BatchMode=yes -lpgoq 192.168.1.2:/etc/pve/* /etc/cron.d/vzdump /etc/pve/master/ --exclude *~) : command 'rsync --rsh=ssh -l root -o BatchMode=yes -lpgoq 192.168.1.2:/etc/pve/* /etc/cron.d/vzdump /etc/pve/master/ --exclude *~' failed with exit code 14:#012rsync: pipe: Cannot allocate memory (12)#012rsync error: error in IPC code (code 14) at pipe.c(57) [receiver=3.0.3]#012
Sep  8 16:19:50 pvemirror4305 syncing templates
I dont want to restart the PVE with all the OpenVZ Containers only if this is the only wait.

Migrating to one of the other machines failed too.

Code:
/usr/bin/ssh -t -t -n -o BatchMode=yes 192.168.1.3 /usr/sbin/vzmigrate --online 192.168.1.2 211
tcgetattr: Inappropriate ioctl for device
OPT:--online 
OPT:192.168.1.2 
Starting online migration of CT 211 to 192.168.1.2 
Preparing remote node 
Initializing remote quota 
Syncing private 
rsync: pipe: Cannot allocate memory (12) 
rsync error: error in IPC code (code 14) at pipe.c(57) [sender=3.0.3] 
Live migrating container... 
rsync: pipe: Cannot allocate memory (12) 
rsync error: error in IPC code (code 14) at pipe.c(57) [sender=3.0.3] 
Error: Failed to sync container private areas 
Connection to 192.168.1.3 closed. 
VM 211 migration failed -

Anyone can help?

Regards, Valle
 
Last edited:
Do you have resource shortage (ram)? 'Cannot allocate memory'
 
Hi,

there are 16 GB of RAM in the PVE with 8 Machines. 7 Machines with 512 MB RAM assigned and one machine with 2 GB assigned.

But i think now there is a other problem. Have shut down all machines remotely and wanted to reboot the server. Server didn´t fired up. Now i must start my reserve machine manuell and mount the iscsi-storage on this machine. Hope it works. ;-)

Can look tomorrow, what happend to the PVE Server.

Regards, Valle
 
Hi,

today i have looked for the error. It was a memory hardware defect.

Thanx and a good day....

Regards, Valle
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!