My Oracle Support Banner

13.4 Additional OMS Failed to Start With Error "private key mismatch or clock skew between servers" (Doc ID 2725622.1)

Last updated on NOVEMBER 11, 2020

Applies to:

Enterprise Manager Base Platform - Version and later
Information in this document applies to any platform.


3 Node 13.4 OMS
OMS on node 3 failed to start.
Observed below errors from OMS logs:


Nov 02, 2020 3:49:11 AM oracle.sysman.eml.sec.auth.provider.repos.EMReposLoginModuleImpl login
WARNING: Authentication failed for user: weblogic Invalid username/password provided
<Nov 2, 2020 3:49:11,668 AM EST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file ( is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>



<Nov 2, 2020 5:50:57,769 AM EST> <Error> <Management> <node name> <EMGC_ADMINSERVER> <[ACTIVE] ExecuteThread: '111' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <ff5f4b1f-2689-4c4c-a6d7-fb0b4d1bc34e-0000117b> <1604314257769> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-141149> <An invalid attempt was made to connect to the Administration Server with a salt of YhUdChueNPfUAySxTuGwJg== and a signature of l7J6IPrVxaffA30N8ACvg+aVldEq3glzcwwPL7VZHEs=, likely due to private key mismatch or clock skew between servers.>





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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.