ELAP syscheck: FAILURE:: CRITICAL::1000000000010000 -- Server's Time Has Gone Backwards

Asset ID:	1-72-2335598.1
Update Date:	2017-12-11
Keywords:

Solution Type Problem Resolution Sure

Solution 2335598.1 : ELAP syscheck: FAILURE:: CRITICAL::1000000000010000 -- Server's Time Has Gone Backwards

Applies to:

Oracle Communications EAGLE (Software) - Version ELAP 10.1 and later
Information in this document applies to any platform.

Symptoms

The ELAP syscheck results reported critical alarm "Server's Time Has Gone Backwards".

[root@elap-b]# syscheck proc
Running modules in class proc...
* ntp: FAILURE:: CRITICAL::1000000000010000 -- Server's Time Has Gone Backwards
* ntp: FAILURE:: Current time 1512097631 precedes last good time 1512169753

Manually adjusted the server clock did not clear the alarm

Cause

The server's time is correct but syscheck is getting an alarm. Issue is due to the residual alarm which sometimes left in an alarm cache.

In this case, the related cache file is "/var/TKLC/log/syscheck/ntp_last_good_time"

Solution

To clear the alarm "Server's Time Has Gone Backwards", execute the following steps to clear the alarm cache.

1. Logon ELAP server as user "root".

2. Enter the following command to remove the cache file.

# rm /var/TKLC/log/syscheck/ntp_last_good_time

3. New cache file will be automatically created.

4. Verify alarm status.

Attachments

This solution has no attachment