5 Replies Latest reply: Mar 29, 2012 12:28 PM by AlissonSilva RSS

    Unable to start node manager

    Haasini
      Hi Experts & Gurus,

      I am facing the issue while starting the node manager.

      I am able to see the following while connecting to the node manager : nmConnect(...)

      WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : [Security:090476]Invalid/unknown SSL header was received from peer **** during SSL handshake.


      I am able to see the following while startNodeManager():

      wls:/idm1_domain/serverConfig> NMProcess: <Dec 23, 2011 4:23:24 AM> <WARNING> <Configuration error while reading domain directory>
      NMProcess: weblogic.nodemanager.common.ConfigException: The domain 'idm1_domain' at 'null' was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file.
      NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:254)
      NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
      NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
      NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:71)
      NMProcess: at java.lang.Thread.run(Thread.java:662)
      NMProcess:
      NMProcess: Dec 23, 2011 4:23:24 AM weblogic.nodemanager.server.Handler handleDomain
      NMProcess: WARNING: Configuration error while reading domain directory
      NMProcess: weblogic.nodemanager.common.ConfigException: The domain 'idm1_domain' at 'null' was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file.
      NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:254)
      NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
      NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
      NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:71)
      NMProcess: at java.lang.Thread.run(Thread.java:662)

      From these logs i understand that this is throwing exception while registering the domain by looking at the nodemanager.domains file which already has the following values in it...(the file is already under D:\Oracle\Middleware\wlserver_10.3\common\nodemanager\nodemanager.domains)

      idm1_domain=D\:\\Oracle\\Middleware\\user_projects\\domains\\idm1_domain
      bifoundation_domain=D\:\\Oracle\\Middleware\\user_projects\\domains\\bifoundation_domain


      Please help.

      Many Thanks .
        • 1. Re: Unable to start node manager
          Haasini
          Any Suggestions on this is highly appreciated...Thanks.
          • 2. Re: Unable to start node manager
            918153
            Hi,

            I had the same error, got it fixed? What did you do?
            • 3. Re: Unable to start node manager
              Faisal Khan
              Kindly verify your configuration once again


              http://weblogic-wonders.com/weblogic/2010/11/12/weblogic-setup-in-distributed-environment-with-node-manager/

              If you get SSL Exceptions, you can refer this

              http://weblogic-wonders.com/weblogic/2010/03/03/ssl-exceptions-in-admin-server-and-node-manager/
              • 4. Re: Unable to start node manager
                emil bolokanov
                Hello,

                Are you sure that the domain is registered ? Have you done an nmEnroll() ?

                Using nmConnect() in a Production Environment

                By default, the nmConnect() command cannot be used in a production environment. You must perform the following procedures to use nmConnect in a production environment.
                Start the administration server.
                Using the Administration Console update the Node Manager credentials from the Advanced options under domain_name—>Security—>General.
                Start WLST in online mode.
                Run nmEnroll() using the following as an example:

                nmEnroll('C:/bea/user_projects/domains/prod_domain',
                'C:/bea/wlserver_10.0/common/nodemanager')

                Running nmEnroll() ensures that the correct NodeManager user and password token are supplied to each managed server. Once these are available for each managed server, you can use nmConnect() in a production environment.
                Note:     You must run nmEnroll() on each machine that is running a managed server. Additionally, you should run nmEnroll() for each domain directory on each machine.
                • 5. Re: Unable to start node manager
                  AlissonSilva
                  Change SecureListener to false at <installation_dir>./wlserver_10.3/common/nodemanager/nodemanager.properties
                  Change machine configuration at admin "console > machine > (each machine name) > configuration > Node Manager > Type" to plain.
                  Restart admin and nodemanager.
                  To check if it "console > machine > (each machine name) > monitoring > Node Manager Status" Status is equal Reachable.