aspose file tools*
The moose likes BEA/Weblogic and the fly likes Unable to start AdminServer with nmStart('AdminServer') command Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Unable to start AdminServer with nmStart( Watch "Unable to start AdminServer with nmStart( New topic
Author

Unable to start AdminServer with nmStart('AdminServer') command

Javian Berts
Greenhorn

Joined: May 08, 2009
Posts: 15
Hi,

I tried to start the AdminServer with the node manager using the nmStart('AdminServer') command but got the following error:

Error starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer': java.io.IOException: Server failed to start up. See server output log for more details.

As I investigate further, I found the following error message in the AdminServer.log file:

####<Dec 22, 2010 2:58:58 PM GMT+08:00> <Critical> <WebLogicServer> <Alpha002> <AdminServer> <main> <<WLS Kernel>> <1293001138031> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:947)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)


####<Dec 22, 2010 2:58:58 PM GMT+08:00> <Notice> <WebLogicServer> <Alpha002> <AdminServer> <main> <<WLS Kernel>> <1293001138094> <BEA-000365> <Server state changed to FAILED>
####<Dec 22, 2010 2:58:58 PM GMT+08:00> <Error> <WebLogicServer> <Alpha002> <AdminServer> <main> <<WLS Kernel>> <1293001138094> <BEA-000383>
####<Dec 22, 2010 2:58:58 PM GMT+08:00> <Notice> <WebLogicServer> <Alpha002> <AdminServer> <main> <<WLS Kernel>> <1293001138110> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Dec 22, 2010 2:58:58 PM GMT+08:00> <Info> <WebLogicServer> <Alpha002> <AdminServer> <main> <<WLS Kernel>> <1293001138266> <BEA-000236> <Stopping execute threads.>

Any idea what went wrong? Thanks in advance.

(P.S. I am using Weblogic 9.2)
Javian Berts
Greenhorn

Joined: May 08, 2009
Posts: 15
Anyone?
robin patel
Greenhorn

Joined: Jan 03, 2011
Posts: 16
Hi ,

Can you please check whether "nm_password.properties" file contains the correct username and password?

If you edit nm_password.properties manually, you must restart Node Manager in order for the changes to take effect.

Below link will help:
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13740/nodemgr_config.htm#i1100227

Also try one more suggestion

Did you check if you have a boot.properties file in this location:
/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain/servers/AdminServer/data/nodemanager folder ?

If not create a plain text file called boot.properties with contents:

username=<WLS Username>
password=<WLS Password>

Check if this resolves your issue


I think you need a valid boot.properties under
/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain/servers/AdminServer/data/nodemanager

Node manager should be able to detect boot.properties under any of these folders.


Regards,
Rob
Javian Berts
Greenhorn

Joined: May 08, 2009
Posts: 15
Hi Robin,

My nm_properties.properties only contains a hashed value similar to the one below:

hashed=IG/maAinUALfq6613A4YYv8Cyu\=

Is it correct if I simply add:

username=<WLS Username>
password=<WLS Password>


to it? And also, will it be stored as a clear text? If so, that might pose another problem, security wise.

Besides that, I have also created a boot.properties file at the location that you suggested with the username and password but that did not resolve the problem. Any other suggestions?

Thanks again.

Regards,
Javian
robin patel
Greenhorn

Joined: Jan 03, 2011
Posts: 16
Hi Javian,

Please take a back up of your current m_properties.properties file

Once done, please enter your credentials in plain text

username=<WLS Username>
password=<WLS Password>

restart Node Manager in order for the changes to take effect.

You will see that the credential will be encrypted. There are no security issues in this.

Let me know if this works for you or not.

If not, kindly upload the NodeManger.properties file and the config.xml


Regards,
Rob
Javian Berts
Greenhorn

Joined: May 08, 2009
Posts: 15
Hi Robin,

It works! Anyway, I think the reason that it did not work previously is because I did not stop the adminserver before I started it again with the nodemanager...my mistake. Anyway, I also noticed that modifying the nm_password.properties file may not required. I replaced the edited version of the nm_password.properties file with the original one (without username and password) and that still works.

Once again, thanks for your help. Really appreciate it.

Regards,
Javian
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Unable to start AdminServer with nmStart('AdminServer') command
 
Similar Threads
Authentication Denied after WLI Domain Creation
Authentication for user weblogic denied
Problem in starting Weblogic server 11g
node manager can't start weblogic server in cluster
weblogic startup