Solaris Cluster "pm_tick delay of xxxx ms exceeds 2147 ms" is Continuously Logged in /var/adm/messages (Doc ID 2094234.1)

Last updated on APRIL 27, 2017

Applies to:

Solaris Cluster Geographic Edition - Version 3.1x to 4.3 [Release 3.1 to 4.3]
Solaris Cluster - Version 3.1x to 4.3 [Release 3.1 to 4.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)

Symptoms

The message "pm_tick delay of xxxx ms exceeds 2147 ms" is continuously written in the file /var/adm/messages since several days. The delay number reported (here xxxx) could be variable.
This message is printed thousands of times and the size of the messages files is growing but there is no other impact or symptom on the cluster nodes.

The key symptom is the fact the same message is repeated over time but the delays reported are bounded and almost the same over time rather than showing increasing delays.
In other words the delays are not getting worse.

For example, checking in /var/adm/messages you could see:

This message was printed a lot of times and the delay is now stable

/explorer.12345678.node1-2016.01.04.12.56/messages/--> grep -c pm_tick messages
3112523

/explorer.12345678.node1-2016.01.04.12.56/messages/--> grep pm_tick messages |awk '{print $13}' | sort -u
3549 <========= this is the lowest delay
3550
3551
3589 <========= this is the highest delay

/explorer.12345678.node1-2016.01.04.12.56/messages/--> grep pm_tick messages |awk '{print $13}' | grep -c 3550
1555990

/explorer.12345678.node1-2016.01.04.12.56/messages/--> grep pm_tick messages |awk '{print $13}' | grep -c 3549
1556529

It is clear that the delay is not getting worse: the majority of times we see  delays of 3549 and 3550 seconds and the delay range is bounded.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms