on proxmox node System-->corosyn -->status dead--> unit enabled

[s_karthi]

Hi ,

After fresh installation of proxmox (did muntilple time) -- i went to the node and i see system all services are running. only corosyn status is dead.
plesae check the attached screen. Below are error messages.


ar 16 22:53:37 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:32 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:38 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:43 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:46 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
-- Boot fc03d0aa00564cfe8920fd1d0b5a5d4a --
Mar 16 23:20:25 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
-- Boot 3110fe3d26ef4bafabbe7336f1575ed3 --
Mar 17 09:36:03 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 17 15:37:54 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 17 15:59:16 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).


Thanks
Karthik

 

[fba]

Hi,
no worries, this is on purpose as the log entries you posted tell. There is no config file for the corosync.service and therefore it doesn't get started.
Corosync is needed in a cluster only, not on single nodes like yours.

 

[aabraham]

Hi ,

After fresh installation of proxmox (did muntilple time) -- i went to the node and i see system all services are running. only corosyn status is dead.
plesae check the attached screen. Below are error messages.


ar 16 22:53:37 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:32 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:38 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:43 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 16 22:57:46 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
-- Boot fc03d0aa00564cfe8920fd1d0b5a5d4a --
Mar 16 23:20:25 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
-- Boot 3110fe3d26ef4bafabbe7336f1575ed3 --
Mar 17 09:36:03 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 17 15:37:54 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 17 15:59:16 pvemac systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).


Thanks
Karthik

Are you running a cluster consisting of multiple nodes? Is the machine you are experiencing this error on part of the cluster? As "fba" mentioned, the configuration file for corosync does not exist (Path: /etc/corosync/corosync.conf).

 

[s_karthi]

Hi fba/aabraham,

I did fresh installation, So my question 1. corosync.conf no file generatated ? Question 2. corosync status is dead in fresh install.

Thanks
Karthik

 

[fba]

On a fresh system without cluster the corosync.conf does not exists. That's on purpose, I think. Corosync therefore hasn't died, even so the status indicates this, it didn't get started due to a failing redundancy check.
But I agree, that the description "dead" is misleading. You can circumvent it by issuing systemctl mask corosync.service on the node's shell.
Make sure to unmask the service before you want to use the node in a cluster.