Challenges‎ > ‎

Server Not Starting


Boot identity not valid

Reset WebLogic Server Credentials

Many times we may want to alter the WebLogic Admin Username and passwords on a routine basis. Because that is, one of the best practices.
 
If you want to reset the WebLogic Username and Password then you just follow these Steps mentioned below:
 
Step 1) Open a command prompt and then run “setDomainEnv.sh” or “setDomainEnv.cmd”.
 
Step 2) Just for Safety Take a Backup of (user_home\domains\your_Domain\security\*DefaultAuthenticatorInit.ldift*) file use / for UNIX systems because in the next command which we are going to run is going to Create a New File “DefaultAuthenticatorInit.ldift”.
 
Step 3) In the Command Window Move inside your Domain’s Security Directory…And then Run the Following Command:


 
Syntax:

java weblogic.security.utils.AdminAccount <NewAdminUserName> <NewAdminPassword> .
 
Example: user_home\domains\your_domain\security>java weblogic.security.utils.AdminAccount newAdmin newPassword .
 

NOTE:- Here is a . (DOT) at the end of the above command which represents the current directory. Here you can see that after this command Executes A new “DefaultAuthenticatorInit.ldift” file will be created in the current directory.
 
Step 4) In the same command prompt move inside the admin server folder inside your domain. And then just remname the “data” folder to something else like “data_OLD” this is a way of taking safe backup….
 
Example:  user_home\domains\your_domain\servers\AdminServer> rename data data_OLD
 mv data data_OLD (for UNIX)
 
Step 5) Now Similarly rename the boot.properties as well to an other File
 
Example: user_home\domains\your_domain\servers\AdminServer\security> rename boot.properties boot.properties_OLD

if you don't find the boot.properties file or security folder in the admin directory, then you can do the following.

Create the 'security' folder under adminServer and create the boot.properties file with clear text username, password values. When the server start automatically encrypts these values.

Example boot.properties file as follows:
username=system
password=weblogic

 
Step 6) Now start The Admin Server….
 
While starting it will ask for the UserName and Password to be entered as ..we have not created any “boot.properties” file at present. But it is always recommended that u create the “boot.properties” file on your own …to prevent WebLogic Prompting you for Admin Username & Passwords while starting the Server.
 
————> At the End Login to Admin Console with the New Useraname and Password—–> Check the Users in Security realms …you will not find any user with name “weblogic” There….
 
Step 7)  To import other User Data back Please do the following:
 
Login to Admin Console
Security Realms—> myrealm(Your realm Name)—> Migration(Tab)—> Import (Tab)
 
Now provide the folder Name where u have all the above files:
DefaultAuthenticator.dat
DefaultCredentialMapper.dat
exportIndex.dat
XACMLAuthorizer.dat
XACMLRoleMapper.dat
 
This is undocumented so I found this on a WebLogic forum, I am updating here easy reference to feature WebLogic Admins.

 

Admin server not starting


<Mar 21, 2012 5:41:34 AM EDT> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) 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.>
<Mar 21, 2012 5:41:34 AM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) 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.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) 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.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
        at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    …..

<Mar 21, 2012 5:41:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Autonomy engine processes stoppe

Investigation:

Please check are there any Recent Changes happened :One of the possible change could be  DataBase hosting server migration that means the JDBC connection pool URL. Verify the same with dbping command utility to confirm the DB URL working fine or not.

 
Work around:
Please update the changed DB hostname and port details in the WebLogic Domain configuruation directory that contains urdomain/config/ separate XML file in jdbc/datasourcename_xml
 

Unchanged STARTING state

While starting the weblogic server it is not initializing the security realm so no servers are starting on the machine. The tailing of logs is showing the following after that weblogic server got into STARTING state no new state coming...
<Mar 16, 2012 1:14:26 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
 
Workaround:
Step 1: Make sure that server is already down. if not find the process associated with that WebLogic instance (java process) and kill it with -9 option.

Step 2: Go to that domains/urdomain/servers/mgserver/ look for ldap directory
remove it, then start the server.This will removes the combusion happen for the security realm will be cleared by removing ldap directory. WebLogic Server instance look for the existing ldap for boot identity matching if it is not found then it will automatically creates it.

WebLogic Server 10g Console Issue

WebLogic Server 10g has flaw on the administartion conosole when You try to do the Shutdown from the Control page, it cannot be ready to accept the shutdown requrest for the AdminServer this is after managed servers already came to SHUTDOWN state you are in the Control page only.
 
To resolve this, you need to click on the "Configure" button and come back and click on "Control" button. Now you are allowed to hit Shutdown button.
Note this WebLogic Server 11g onwards the issue is fixed no problem on  the Administration console.
 

Comments