[pve-devel] problem with add new node to cluster proxmox4.

[Eduard Ahmatgareev]

proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)
pve-kernel-4.2.6-1-pve: 4.2.6-34
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-31
qemu-server: 4.0-49
pve-firmware: 1.1-7
libpve-common-perl: 4.0-45
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-3
pve-container: 1.0-39
pve-firewall: 2.0-15
pve-ha-manager: 1.0-19
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-6
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie



from iso:
proxmox-ve_4.1-2f9650d4-21.iso


2016-02-04 12:01 GMT+02:00 Thomas Lamprecht <t.lamprecht at proxmox.com>:

>
>
> On 02/04/2016 10:58 AM, Eduard Ahmatgareev wrote:
>
>> I tried add new node to proxmox cluster and had problem:
>>
>>
>>
>> pvecm add cluster_ip --force
>> Are you sure you want to continue connecting (yes/no)? yes
>> node cluster-2-4 already defined
>> copy corosync auth key
>> stopping pve-cluster service
>> backup old database
>> Job for corosync.service failed. See 'systemctl status corosync.service'
>> and 'journalctl -xn' for details.
>> waiting for quorum...
>>
>> and nothing, on other console:
>>
>>
>> sytemctl status corosync.service
>> ● corosync.service - Corosync Cluster Engine
>>    Loaded: loaded (/lib/systemd/system/corosync.service; enabled)
>>    Active: failed (Result: exit-code) since Wed 2016-02-03 17:16:43 EET;
>> 3min 55s ago
>>   Process: 3657 ExecStart=/usr/share/corosync/corosync start
>> (code=exited, status=1/FAILURE)
>>
>> Feb 03 17:16:43 cluster-2-4 corosync[3664]: parse error in config: Can't
>> open logfile '/var/log/cluster/corosync.log' for reason: No such file or
>> directory (2).
>> Feb 03 17:16:43 cluster-2-4 corosync[3657]: Starting Corosync Cluster
>> Engine (corosync): [FAILED]
>> Feb 03 17:16:43 cluster-2-4 systemd[1]: corosync.service: control process
>> exited, code=exited status=1
>> Feb 03 17:16:43 cluster-2-4 systemd[1]: Failed to start Corosync Cluster
>> Engine.
>> Feb 03 17:16:43 cluster-2-4 systemd[1]: Unit corosync.service entered
>> failed state.
>>
>>
>> ok, I ran command: mkdir /var/log/cluster
>> and I was happy, because on other console saw:
>>
>> OK
>> generating node certificates
>> merge known_hosts file
>> restart services
>> successfully added node 'cluster-2-4' to cluster.
>> root at cluster-2-4:~#
>>
>>
>> This problem with /var/log/cluster  appeared from version 4.2, can you
>> fix this in install scripts?
>>
>
>
> Version 4.2 of what? There is no PVE 4.2, yet.
> Whats the output of:
>
> # pveversion -v
>
> ?
>
> And is this from a PVE iso installer or from PVE on debian?
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20160204/e37f1234/attachment.htm>