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

[Thomas Lamprecht]

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?