Can't set time on Replica Instance

[BillHagen]

I have a primary instance (SecurID) currently setup. I created a replica package and then spun up a replica instance. I attempted to attach it to the primary, but got the message "Cannot attach this replica instance. The time difference between the primary and replica instances is more than 10 minutes."

I know the primary instance time is correct, so I figured I just messed up when setting the time on the replica. So I deleted it and started over. I set the time on the replica correctly: America, Los Angeles. Added my NTP server and checked the date/time. It was absolutely correct. Tried to attach this new, correct install to the primary, and got the exact same error.

Even stranger, somehow both the replica's I built were/are 9 1/2 hours faster than the primary. ??? That doesn't even make sense.

I attempted to console into the replica and change the time, but the "rsaadmin" user doesn't have permissions to change the date/time.

What's going on here? How do I fix this?

Thanks!

[BillHagen · Accepted solution]

I answered my own question. Page 408 of the Administrator's Guide gave me a hint. It says:

– In a command prompt, log on as rsaadmin and enter the operating system account password.

– Type the following command to log on as the root user and press ENTER: sudo su -

– When prompted, type the operating system account password, and press ENTER.

I did this, then typed: date Of course the date was wrong. Then typed: date -s "27 April 2016 10:53:00"

Typed: date and the date was correct.

Attempted to attach the replica to the primary...SUCCESS.

Thanks for reading...you may now go back to your regular life, already in progress. 🙂

[EdwardDavis]

What matters most is, when you do a date -u, does it really show actual UTC time ?

and to set date (as root)

date MMDDHHHHYYYY

where HHHH is the 24hour clock

and you set time in your local timezone, then recheck date -u again to verify UTC time is correct.

Tokencode authentication is always based on UTC.