OAC-Classic : OAC VM Clock Out of Sync Giving "unsynchronised" as Output for ntpstat Command Causing Dual Login Page to be Displayed when accessing OAC URL
(Doc ID 2541586.1)
Last updated on OCTOBER 10, 2019
Applies to:Oracle Analytics Cloud - Classic - Version 17.4.5 and later
Information in this document applies to any platform.
Issue Seen :
OAC Instance Was Created Using Private IP Network . When accessing the OAC dv/ui URL it brings the IDCS Login Page, but once credentials are entered, it brings up the OAC login page again instead of logging in the user directly to OAC.
This issue gets fixed once OAC is restarted.
The above behavior can happen when the OAC Classic Instances VM Clock gets out of sync causing IDCS and OAC clock to be out of sync. This makes the IDCS session expire causing the second login page to appear. You can verify if the VM clock is out of sync using following steps :
[root@<hostname> ~]# ntpstat
polling server every 8 s
If output is shown as unsynchronised, then you know the VM clock is not in sync.
The VM Clock normally gets synced up with NTP Server. By default the public servers from the pool.ntp.org project is used as ntpserver as defined in /etc/ntp.conf file
However if the OAC instance is created using Private IP Network, then most likely these default NTP Server will be not reachable from the OAC VM. In this scenario , a local NTP Server(residing with customers own network) has to be defined and the VPN routes have to be set such that it allows Connection from the OAC VM to the Local NTP Server.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document