puppetlabs-corosync with debian9

journal output

Dec 12 22:26:38 debian9-64-1 systemd[1]: Starting Corosync Cluster Engine...
Dec 12 22:26:38 debian9-64-1 corosync[2812]:  [MAIN  ] Corosync Cluster Engine ('2.4.2'): started and ready to provide service.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [MAIN  ] Corosync Cluster Engine ('2.4.2'): started and ready to provide service.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [MAIN  ] Corosync built-in features: dbus rdma monitoring watchdog augeas systemd upstart xmlconf qdevices qnetd snmp pie relro b
indnow
Dec 12 22:26:38 debian9-64-1 corosync[2812]:  [MAIN  ] Corosync built-in features: dbus rdma monitoring watchdog augeas systemd upstart xmlconf qdevices qnetd snmp pie relro bindnow
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [TOTEM ] Initializing transport (UDP/IP Multicast).
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [TOTEM ] Initializing transport (UDP/IP Multicast).
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [TOTEM ] The network interface [127.0.0.1] is now up.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync configuration map access [0]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [QB    ] server name: cmap
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync configuration service [1]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [TOTEM ] The network interface [127.0.0.1] is now up.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [QB    ] server name: cfg
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [QB    ] server name: cpg
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync profile loading service [4]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync resource monitoring service [6]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [WD    ] Watchdog /dev/watchdog is now been tickled by corosync.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: warning [WD    ] resource load_15min missing a recovery key.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: warning [WD    ] resource memory_used missing a recovery key.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [WD    ] no resources configured.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync watchdog service [7]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [QUORUM] Using quorum provider corosync_votequorum
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [QUORUM] This node is within the primary component and will provide service.
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [QUORUM] Members[0]:
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [QB    ] server name: votequorum
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: info    [QB    ] server name: quorum
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync configuration map access [0]
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [TOTEM ] A new membership (127.0.0.1:12) was formed. Members joined: 1
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [QUORUM] Members[1]: 1
Dec 12 22:26:39 debian9-64-1 corosync[2812]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Dec 12 22:26:39 debian9-64-1 systemd[1]: Started Corosync Cluster Engine.
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QB    ] server name: cmap
Dec 12 22:26:39 debian9-64-1 systemd[1]: Started Pacemaker High Availability Cluster Manager.
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync configuration service [1]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QB    ] server name: cfg
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QB    ] server name: cpg
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync profile loading service [4]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync resource monitoring service [6]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [WD    ] Watchdog /dev/watchdog is now been tickled by corosync.
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [WD    ] resource load_15min missing a recovery key.
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [WD    ] resource memory_used missing a recovery key.
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [WD    ] no resources configured.
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync watchdog service [7]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QUORUM] Using quorum provider corosync_votequorum
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QUORUM] This node is within the primary component and will provide service.
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QUORUM] Members[0]:
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QB    ] server name: votequorum
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QB    ] server name: quorum
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [TOTEM ] A new membership (127.0.0.1:12) was formed. Members joined: 1
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [QUORUM] Members[1]: 1
Dec 12 22:26:39 debian9-64-1 corosync[2812]:  [MAIN  ] Completed service synchronization, ready to provide service.
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Additional logging available in /var/log/pacemaker.log
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Starting Pacemaker 1.1.16
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Could not obtain a node name for corosync nodeid 1
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Quorum acquired
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Could not obtain a node name for corosync nodeid 1
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Node debian9-64-1 state is now member
Dec 12 22:26:39 debian9-64-1 systemd[1]: Stopping Pacemaker High Availability Cluster Manager...
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Caught 'Terminated' signal
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Shutting down Pacemaker
Dec 12 22:26:39 debian9-64-1 pacemakerd[2814]:   notice: Stopping crmd
Dec 12 22:26:39 debian9-64-1 cib[2827]:   notice: Additional logging available in /var/log/pacemaker.log
Dec 12 22:26:40 debian9-64-1 stonith-ng[2828]:   notice: Additional logging available in /var/log/pacemaker.log
Dec 12 22:26:40 debian9-64-1 stonith-ng[2828]:   notice: Connecting to cluster infrastructure: corosync
Dec 12 22:26:40 debian9-64-1 stonith-ng[2828]:   notice: Could not obtain a node name for corosync nodeid 1
Dec 12 22:26:40 debian9-64-1 stonith-ng[2828]:   notice: Node (null) state is now member
Dec 12 22:26:40 debian9-64-1 stonith-ng[2828]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:26:40 debian9-64-1 cib[2827]:   notice: Connecting to cluster infrastructure: corosync
Dec 12 22:26:40 debian9-64-1 stonith-ng[2828]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:26:40 debian9-64-1 cib[2827]:   notice: Could not obtain a node name for corosync nodeid 1
Dec 12 22:26:40 debian9-64-1 cib[2827]:   notice: Node (null) state is now member
Dec 12 22:26:40 debian9-64-1 cib[2827]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:26:40 debian9-64-1 lrmd[2829]:   notice: Additional logging available in /var/log/pacemaker.log
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: Additional logging available in /var/log/pacemaker.log
Dec 12 22:26:40 debian9-64-1 pengine[2831]:   notice: Additional logging available in /var/log/pacemaker.log
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: Connecting to cluster infrastructure: corosync
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: Could not obtain a node name for corosync nodeid 1
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: Quorum acquired
Dec 12 22:26:40 debian9-64-1 cib[2827]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: Node debian9-64-1 state is now member
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:26:40 debian9-64-1 attrd[2830]:   notice: Additional logging available in /var/log/pacemaker.log
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: The local CRM is operational
Dec 12 22:26:40 debian9-64-1 crmd[2832]:   notice: State transition S_STARTING -> S_PENDING
Dec 12 22:26:40 debian9-64-1 attrd[2830]:   notice: Connecting to cluster infrastructure: corosync
Dec 12 22:26:40 debian9-64-1 attrd[2830]:   notice: Could not obtain a node name for corosync nodeid 1
Dec 12 22:26:40 debian9-64-1 attrd[2830]:   notice: Node (null) state is now member
Dec 12 22:26:40 debian9-64-1 attrd[2830]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:27:01 debian9-64-1 crmd[2832]:  warning: Input I_DC_TIMEOUT received in state S_PENDING from crm_timer_popped
Dec 12 22:27:01 debian9-64-1 crmd[2832]:   notice: State transition S_ELECTION -> S_INTEGRATION
Dec 12 22:27:01 debian9-64-1 crmd[2832]:  warning: Input I_ELECTION_DC received in state S_INTEGRATION from do_election_check
Dec 12 22:27:01 debian9-64-1 attrd[2830]:   notice: Defaulting to uname -n for the local corosync node name
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: Resource start-up disabled since no STONITH resources have been defined
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: Either configure some or disable STONITH with the stonith-enabled option
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: NOTE: Clusters with shared data need STONITH to ensure data integrity
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Delaying fencing operations until there are resources to manage
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Calculated transition 0, saving inputs in /var/lib/pacemaker/pengine/pe-input-4.bz2
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Configuration ERRORs found during PE processing.  Please run "crm_verify -L" to identify issues.
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: Resource start-up disabled since no STONITH resources have been defined
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: Either configure some or disable STONITH with the stonith-enabled option
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: NOTE: Clusters with shared data need STONITH to ensure data integrity
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Delaying fencing operations until there are resources to manage
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Calculated transition 1, saving inputs in /var/lib/pacemaker/pengine/pe-input-5.bz2
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Configuration ERRORs found during PE processing.  Please run "crm_verify -L" to identify issues.
Dec 12 22:27:01 debian9-64-1 crmd[2832]:   notice: Transition 1 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-5.bz2): C
omplete
Dec 12 22:27:01 debian9-64-1 crmd[2832]:   notice: State transition S_TRANSITION_ENGINE -> S_IDLE
root@debian9-64-1:/#
root@debian9-64-1:/# systemctl status pacemaker
● pacemaker.service - Pacemaker High Availability Cluster Manager
   Loaded: loaded (/lib/systemd/system/pacemaker.service; enabled; vendor preset: enabled)
   Active: deactivating (stop-sigterm) since Wed 2018-12-12 22:26:39 UTC; 1min 45s ago
     Docs: man:pacemakerd
           http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/index.html
 Main PID: 2814 (pacemakerd)
    Tasks: 7 (limit: 4915)
   CGroup: /docker/9e4ade2c2540f97750ca536e205bfa7cae95217b31d526baa46d48add6593d5c/system.slice/pacemaker.service
           ├─2814 /usr/sbin/pacemakerd -f
           ├─2827 /usr/lib/pacemaker/cib
           ├─2828 /usr/lib/pacemaker/stonithd
           ├─2829 /usr/lib/pacemaker/lrmd
           ├─2830 /usr/lib/pacemaker/attrd
           ├─2831 /usr/lib/pacemaker/pengine
           └─2832 /usr/lib/pacemaker/crmd

Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Calculated transition 0, saving inputs in /var/lib/pacemaker/pengine/pe-input-4.bz2
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Configuration ERRORs found during PE processing.  Please run "crm_verify -L" to identify issues.
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: Resource start-up disabled since no STONITH resources have been defined
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: Either configure some or disable STONITH with the stonith-enabled option
Dec 12 22:27:01 debian9-64-1 pengine[2831]:    error: NOTE: Clusters with shared data need STONITH to ensure data integrity
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Delaying fencing operations until there are resources to manage
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Calculated transition 1, saving inputs in /var/lib/pacemaker/pengine/pe-input-5.bz2
Dec 12 22:27:01 debian9-64-1 pengine[2831]:   notice: Configuration ERRORs found during PE processing.  Please run "crm_verify -L" to identify issues.
Dec 12 22:27:01 debian9-64-1 crmd[2832]:   notice: Transition 1 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-5.bz2): Complete
Dec 12 22:27:01 debian9-64-1 crmd[2832]:   notice: State transition S_TRANSITION_ENGINE -> S_IDLE