Jeevan Patnaik <g1patn...@gmail.com> writes: > <wf...@niif.hu> writes: > >> Jeevan Patnaik <g1patn...@gmail.com> writes: >> >>> [16187] node1 corosyncwarning [MAIN ] Corosync main process was not >>> scheduled for 2889.8477 ms (threshold is 800.0000 ms). Consider token >>> timeout increase. >>> [...] >>> 2. How to fix this? We have not much load on the nodes, the corosync is >>> already running with RT priority. >> >> Does your corosync daemon use a watchdog device? (See in the startup >> logs.) Watchdog interaction can be *slow*. > > Watchdog is disabled in pacemaker.
Cool, but I'd recommend checking the corosync startup logs. -- Regards, Feri _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
