Recently we had to reset weblogic passwords on several environments. These weblogic environments are all managed by nodemanagers. We changed the weblogic passwords in the console. Logging in at the console with the new passwords went well, so we knew that the password reset was succesfull.
We then recreated the entries in the $DOMAIN_HOME/AdminServer/security/boot.properties.
Starting the AdminServer with the $DOMAIN_HOME/startWeblogic.sh script went fine, without asking for credentials. This confirmed that the boot.properties file was working with the new password.
Still, there was an error when starting the AdminServer with the nodemanager. When starting, the AdminServer logs stated that the user weblogic from the boot.properties was denied access!!! ....
The problem was that the AdminServer (as well as all other managed servers) are using a different boot.properties file, when starting with the nodemanager. This file is located in $DOMAIN_HOME/servers/AdminServer/data/nodemanager/boot.properties This file contains the old values at this moment!
When this file is present, the nodemanager will use this file to boot up the AdminServer. When it is not present, the nodemanager loads a new one.
So, just stop the AdminServer (as well as any other managed servers if present). Stop the nodemanager. Then, delete the boot.properties file from $DOMAIN_HOME/servers/AdminServer/data/nodemanager/.
Now, start the nodemanager. A new boot.properties file will be loaded into $DOMAIN_HOME/servers/AdminServer/data/nodemanager/ and the nodemanager will be able to start the AdminServer.
good to know this article!!
ReplyDelete