[SOLVED] Cannot initialize CMAP service after enabling vtx

[Aaron_b]

Hello today i came on after the host enabled vtx and no nodes will start
pvecm status

Cannot initialize CMAP service

journalctl -b -u corosync

-- Logs begin at Fri 2018-11-16 12:24:42 GMT, end at Fri 2018-11-16 12:39:24 GMT. --
Nov 16 12:24:49 185-177-22-22 systemd[1]: Starting Corosync Cluster Engine...
Nov 16 12:24:49 185-177-22-22 corosync[1465]:  [MAIN  ] Corosync Cluster Engine ('2.4.2-dirty'): started and ready to provide service.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [MAIN  ] Corosync Cluster Engine ('2.4.2-dirty'): started and ready to provide service.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: info    [MAIN  ] Corosync built-in features: dbus rdma monitoring watchdog augeas systemd upstart xmlconf qd
Nov 16 12:24:49 185-177-22-22 corosync[1465]:  [MAIN  ] Corosync built-in features: dbus rdma monitoring watchdog augeas systemd upstart xmlconf qdevices
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [TOTEM ] Initializing transport (UDP/IP Multicast).
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
Nov 16 12:24:49 185-177-22-22 corosync[1465]:  [TOTEM ] Initializing transport (UDP/IP Multicast).
Nov 16 12:24:49 185-177-22-22 corosync[1465]:  [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [TOTEM ] The network interface is down.
Nov 16 12:24:49 185-177-22-22 corosync[1465]:  [TOTEM ] The network interface is down.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [SERV  ] Service engine loaded: corosync configuration map access [0]
Nov 16 12:24:49 185-177-22-22 corosync[1465]: info    [QB    ] server name: cmap
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [SERV  ] Service engine loaded: corosync configuration service [1]
Nov 16 12:24:49 185-177-22-22 corosync[1465]: info    [QB    ] server name: cfg
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Nov 16 12:24:49 185-177-22-22 corosync[1465]: info    [QB    ] server name: cpg
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [SERV  ] Service engine loaded: corosync profile loading service [4]
Nov 16 12:24:49 185-177-22-22 corosync[1465]:  [SERV  ] Service engine loaded: corosync configuration map access [0]
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [SERV  ] Service engine loaded: corosync resource monitoring service [6]
Nov 16 12:24:49 185-177-22-22 corosync[1465]: warning [WD    ] Watchdog /dev/watchdog exists but couldn't be opened.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: warning [WD    ] resource load_15min missing a recovery key.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: warning [WD    ] resource memory_used missing a recovery key.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: info    [WD    ] no resources configured.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [SERV  ] Service engine loaded: corosync watchdog service [7]
Nov 16 12:24:49 185-177-22-22 corosync[1465]: notice  [QUORUM] Using quorum provider corosync_votequorum
Nov 16 12:24:49 185-177-22-22 corosync[1465]: crit    [QUORUM] Quorum provider: corosync_votequorum failed to initialize.
Nov 16 12:24:49 185-177-22-22 corosync[1465]: error   [SERV  ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist o
Nov 16 12:24:49 185-177-22-22 corosync[1465]: error   [MAIN  ] Corosync Cluster Engine exiting with status 20 at service.c:356.
Nov 16 12:24:49 185-177-22-22 systemd[1]: corosync.service: Main process exited, code=exited, status=20/n/a
Nov 16 12:24:49 185-177-22-22 systemd[1]: Failed to start Corosync Cluster Engine.
Nov 16 12:24:49 185-177-22-22 systemd[1]: corosync.service: Unit entered failed state.
Nov 16 12:24:49 185-177-22-22 systemd[1]: corosync.service: Failed with result 'exit-code'.
Nov 16 12:37:28 185-177-22-22 systemd[1]: Starting Corosync Cluster Engine...
Nov 16 12:37:28 185-177-22-22 corosync[2895]:  [MAIN  ] Corosync Cluster Engine ('2.4.2-dirty'): started and ready to provide service.
Nov 16 12:37:28 185-177-22-22 corosync[2895]: notice  [MAIN  ] Corosync Cluster Engine ('2.4.2-dirty'): started and ready to provide service.
Nov 16 12:37:28 185-177-22-22 corosync[2895]: info    [MAIN  ] Corosync built-in features: dbus rdma monitoring watchdog augeas systemd upstart xmlconf qd
Nov 16 12:37:28 185-177-22-22 corosync[2895]:  [MAIN  ] Corosync built-in features: dbus rdma monitoring watchdog augeas systemd upstart xmlconf qdevices
Nov 16 12:37:28 185-177-22-22 corosync[2895]: notice  [TOTEM ] Initializing transport (UDP/IP Multicast).
Nov 16 12:37:28 185-177-22-22 corosync[2895]: notice  [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1

 

[Stoiko Ivanov]

Is this a cluster or a single node (on a single node corosync need not run).

if its a cluster:

[TOTEM ] The network interface is down.

might give an indication

check your /etc/corosync/corosync.conf (all hostnames present there need to be resolvable (preferably by having them in /etc/hosts)) , and of course all ips need to be present and reachable

 

[Aaron_b]

All sorted now thanks for the reply