LO81574: OS CLOCK MOVING TO BE NON-CONCURRENT AND TSSDATE IN THE FUTURE MAY CAUSE HA SERVERS TO BE MARKED AS NOT ALIVE
Closed as program error.
If the OS clock on a Traveler HA server is moving such that it becomes more than a few seconds out of time sync with the other servers in a pool (and the enterprise DB servers) AND some data in the internal logon path with TSSDate is sufficiently far in the future, the Heartbeat logic will mark servers as not being alive because the Heartbeat time will not be within the specified time period (normally 1 minute).
The OS clock should not be moving very much, so the system itself should be changed to use a time service (such as NTP) to keep the clocks in sync across the servers. If the OS clock is moved and you start getting load balancing errors or all your servers are marked as not alive because of the heartbeat value when they really are alive and have heartbeated within the past minutes, you can workaround the issue by restarting the Traveler and HTTP tasks (or the whole Domino server). Before you restarting, you should fix the OS clock, but that is not known to be required (just recommended).
This is not at all common, but if the System clock wanders on a Traveler server it could result in the server being marked as not available to the other Traveler servers in the HA Pool.
The Notes Traveler server has been updated to be more tollerant of a changing system clock, though in general it is best to use a time service to ensure accurate time is kept on the servers.
This fix is included in Notes Traveler 8.5.3 UP2 IF7, 22.214.171.124 If7 and 9.0.1 IF6 and will be included in any future releases. See this technote for the latest maintenance infomation: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels