How to Fix "ABORTING: bad system date." During prod.start ?

Asset ID:	1-71-1993526.1
Update Date:	2017-05-29
Keywords:

Solution Type Technical Instruction Sure

Solution 1993526.1 : How to Fix "ABORTING: bad system date." During prod.start ?

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 4.1 and later
Information in this document applies to any platform.

Goal

prod.start command is reporting "ABORTING: bad system date." during IDB startup sequence . How can this be fixed ?

Solution

The "ABORTING: bad system date." error is reported during prod.start when the last IDB startup date and time stored in /var/TKLC/ixp/run/timestamp differs too much from the current date and time.

To fix this, the /var/TKLC/ixp/run/timestamp has to be manually reset to the current date and time, this can be done with the re.timestamp command:

On the impacted server (XMF or IXP), log as cfguser and run the following command:

[cfguser@ixp0001-1b ~]$ re.timestamp
[cfguser@ixp0001-1b ~]$

Start the XMF or IXP application with prod.start

Attachments

This solution has no attachment