IBM Support

LO81574: OS CLOCK MOVING TO BE NON-CONCURRENT AND TSSDATE IN THE FUTURE MAY CAUSE HA SERVERS TO BE MARKED AS NOT ALIVE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • 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).
    

Local fix

  • 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).
    

Problem summary

  • 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.
    

Problem conclusion

  • 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.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO81574

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    853

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-08-12

  • Closed date

    2014-09-14

  • Last modified date

    2014-09-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R853 PSY

       UP

  • R900 PSY

       UP

  • R901 PSY

       UP



Document information

More support for: IBM Traveler

Software version: 8.5.3

Reference #: LO81574

Modified date: 14 September 2014