[ClusterLabs] Antw: Re: Antw: [EXT] Systemd resource started on node after reboot before cluster is stable ?

[Ulrich Windl]

>>> Adam Cecile <acecile at le-vert.net> schrieb am 16.02.2023 um 11:13 in Nachricht
<4f0c1203-fd4b-a1cc-4e2f-44384c7205c6 at le-vert.net>:

> On 2/16/23 07:57, Ulrich Windl wrote:
>>>>> Adam Cecile<acecile at le-vert.net>  schrieb am 15.02.2023 um 10:49 in
>> Nachricht
>> <b4f1f2f1-66fe-ca62-ff4f-708d781a507c at le-vert.net>:

[...]
>>> Any idea why this happened ?
>> Your journal (syslog) should tell you!
> 
> Indeed, I overlooked yesterday... But it says it's pacemaker that 
> decided to start it:
> 
> 
[...]
> Feb 15 09:43:26 server3 pacemaker-controld[862]:  warning: Another DC 
> detected: server2 (op=noop)

This does not look OK! Does it happen all the time?


> Feb 15 09:43:26 server3 pacemaker-fenced[858]:  notice: Node server2 
> state is now member
> Feb 15 09:43:26 server3 pacemaker-controld[862]:  notice: State 
> transition S_ELECTION -> S_RELEASE_DC
> Feb 15 09:43:26 server3 pacemaker-controld[862]:  warning: Cancelling 
> timer for action 12 (src=67)
> Feb 15 09:43:26 server3 pacemaker-controld[862]:  notice: No need to 
> invoke the TE (A_TE_HALT) in state S_RELEASE_DC
> Feb 15 09:43:26 server3 pacemaker-attrd[860]:  notice: Node server2 
> state is now member
> Feb 15 09:43:26 server3 pacemaker-controld[862]:  notice: State 
> transition S_PENDING -> S_NOT_DC
> Feb 15 09:43:27 server3 pacemaker-attrd[860]:  notice: Setting 
> #attrd-protocol[server1]: (unset) -> 2
> Feb 15 09:43:27 server3 pacemaker-attrd[860]:  notice: Detected another 
> attribute writer (server2), starting new election
> Feb 15 09:43:27 server3 pacemaker-attrd[860]:  notice: Setting 
> #attrd-protocol[server2]: (unset) -> 2
> Feb 15 09:43:27 server3 IPaddr2(Shared-IPv4)[1258]: INFO:
> Feb 15 09:43:27 server3 ntpd[602]: Listen normally on 8 eth0 10.13.68.12:123
> Feb 15 09:43:27 server3 ntpd[602]: new interface(s) found: waking up 
> resolver
> => Feb 15 09:43:28 server3 pacemaker-controld[862]:  notice: Result of 
> start operation for tomcat9 on server3: ok
> Feb 15 09:43:29 server3 corosync[568]:   [KNET  ] pmtud: PMTUD link 
> change for host: 2 link: 0 from 485 to 1397
> Feb 15 09:43:29 server3 corosync[568]:   [KNET  ] pmtud: PMTUD link 
> change for host: 1 link: 0 from 485 to 1397
> Feb 15 09:43:29 server3 corosync[568]:   [KNET  ] pmtud: Global data MTU 
> changed to: 1397
> => Feb 15 09:43:29 server3 pacemaker-controld[862]:  notice: Requesting 
> local execution of stop operation for tomcat9 on server3
> 
> 
> Any idea ?