MX RE reporting below logs continuously.

Jun 28 22:50:37 mcontrol_ore_alive_set: other RE is not alive

Jun 28 22:50:37 mcontrol_ore_alive_set: other RE is alive

Jun 28 23:54:51 mcontrol_ore_alive_set: other RE is not alive

Jun 28 23:54:51 mcontrol_ore_alive_set: other RE is alive

Jun 29 03:41:06 mcontrol_ore_alive_set: other RE is not alive

Jun 29 03:41:06 mcontrol_ore_alive_set: other RE is alive

Jun 29 09:08:47 mcontrol_ore_alive_set: other RE is not alive

Jun 29 09:08:47 mcontrol_ore_alive_set: other RE is alive

Jun 29 09:38:31 mcontrol_ore_alive_set: other RE is not alive

We get the message: “mcontrol_ore_alive_set: other RE is (not) alive” because of periodic check by mcontrol_periodic() function getting invoked every second and it checks keepalive threshold value, and throws this warning messages if threshold is crossed 

Master RE expects Other RE to send hello message every 20 seconds. And in case of not receiving IPC message consecutively, it may trigger fail-over. This will also have warning message as shown below:

>>>“failed to receive keepalives from other RE for the last <20> sec”

>>> "time left until automatic failover %d sec"

This is a warning message, “mcontrol_ore_alive_set: other RE is not alive”: This message indicates issue with chassisd “mcontrol-thread” which is not able to process keepalive message from backup RE,

but at the same time “mcontrol_ore_alive_set: other RE is alive” this message indicates that the issue is recovered at the same time.