[PVE-User] cluster node issue after upgrade (1.3 -> 1.5)

[Dietmar Maurer]

Does the ssh connection work? Simply do a:

# ssh 192.168.1.36    

that should get you to the node without prompting for anything?

- Dietmar

> -----Original Message-----
> From: pve-user-bounces at pve.proxmox.com [mailto:pve-user-
> bounces at pve.proxmox.com] On Behalf Of Gwenn Gueguen
> Sent: Mittwoch, 21. Juli 2010 10:01
> To: pve-user at pve.proxmox.com
> Subject: [PVE-User] cluster node issue after upgrade (1.3 -> 1.5)
> 
> Hi,
> 
> After upgrading a 5 nodes cluster from pve 1.3 to pve 1.5, i have an
> issue with one of the nodes. Master can't get information from it.
> 
> On master:
> ==========
> 
> # pveca -l
> ID----IPADDRESS----ROLE-STATE--------UPTIME---LOAD----MEM---DISK
>  1 : 192.168.1.32    M     S           21:20   0.29    59%    21%
>  2 : 192.168.1.33    N     A           21:14   1.02    28%     8%
>  5 : 192.168.1.34    N     A           20:59   4.95    47%     1%
>  6 : 192.168.1.36    N     ERROR: 500 Server closed connection without
> sending any data back
> 
>  7 : 192.168.1.89    N     A           21:14   0.17    19%     3%
> 
> # pveversion -v
> pve-manager: 1.5-10 (pve-manager/1.5/4822)
> running kernel: 2.6.24-11-pve
> proxmox-ve-2.6.24: 1.5-23
> pve-kernel-2.6.24-11-pve: 2.6.24-23
> pve-kernel-2.6.24-7-pve: 2.6.24-11
> pve-kernel-2.6.24-1-pve: 2.6.24-4
> pve-kernel-2.6.24-5-pve: 2.6.24-6
> pve-kernel-2.6.24-2-pve: 2.6.24-5
> qemu-server: 1.1-16
> pve-firmware: 1.0-5
> libpve-storage-perl: 1.0-13
> vncterm: 0.9-2
> vzctl: 3.0.23-1pve11
> vzdump: 1.2-5
> vzprocps: 2.0.11-1dso2
> vzquota: 3.0.11-1
> pve-qemu-kvm: 0.12.4-1
> 
> Jul 21 09:54:35 arrouya pvemirror[22416]: starting cluster
> syncronization
> Jul 21 09:54:36 arrouya pvemirror[22416]: syncing vzlist from
> '192.168.1.36' failed: 500 Server closed connection without sending any
> data back
> Jul 21 09:54:36 arrouya pvemirror[22416]: syncing templates
> Jul 21 09:54:36 arrouya pvemirror[22416]: cluster syncronization
> finished (0.35 seconds (files 0.00, config 0.00))
> 
> 
> On the node:
> ============
> 
> # pveca -l
> CID----IPADDRESS----ROLE-STATE--------UPTIME---LOAD----MEM---DISK
>  1 : 192.168.1.32    M     S           21:20   0.34    59%    21%
>  2 : 192.168.1.33    N     A           21:13   1.02    28%     8%
>  5 : 192.168.1.34    N     A           20:59   5.49    47%     1%
>  6 : 192.168.1.36    N     A           00:23   0.00     5%     3%
>  7 : 192.168.1.89    N     A           21:14   0.11    19%     3%
> 
> # pveversion -v
> pve-manager: 1.5-10 (pve-manager/1.5/4822)
> running kernel: 2.6.24-11-pve
> proxmox-ve-2.6.24: 1.5-23
> pve-kernel-2.6.24-11-pve: 2.6.24-23
> pve-kernel-2.6.24-7-pve: 2.6.24-11
> qemu-server: 1.1-16
> pve-firmware: 1.0-5
> libpve-storage-perl: 1.0-13
> vncterm: 0.9-2
> vzctl: 3.0.23-1pve11
> vzdump: 1.2-5
> vzprocps: 2.0.11-1dso2
> vzquota: 3.0.11-1
> pve-qemu-kvm: 0.12.4-1
> 
> The node seems to synchronize successfully with the master:
> Jul 21 09:34:04 verdal pvemirror[4332]: syncing master configuration
> from '192.168.1.32'
> Jul 21 09:34:05 verdal pvemirror[4332]: syncing templates
> Jul 21 09:34:05 verdal pvemirror[4332]: cluster syncronization finished
> (0.53 seconds (files 0.00, config 0.13))
> 
> 
> Any idea about what can be wrong?
> 
> --
> Gwenn
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user