1 Reply Latest reply on Apr 12, 2016 9:11 PM by cesar.advincula.o

    Unable to start Nodemanager

    User571494

      I am unable to start nodemanager, can anyone help ? It is failing with the below error:

       

      <Apr 12, 2016 12:23:34 PM> <SEVERE> <Fatal error in node manager server>

      java.lang.NullPointerException

          at java.util.Hashtable.containsKey(Hashtable.java:307)

          at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServerConfig.java:491)

          at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServerConfig.java:481)

          at weblogic.nodemanager.server.NMServerConfig.print(NMServerConfig.java:599)

          at weblogic.nodemanager.server.NMServerConfig.print(NMServerConfig.java:561)

          at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:166)

          at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)

          at weblogic.NodeManager.main(NodeManager.java:31)

        • 1. Re: Unable to start Nodemanager
          cesar.advincula.o

          Hello,

           

          Could your configuration settings:

           

           

           

          NodeManagerHome=

          ListenAddress=

          ListenPort=5556

          ListenBacklog=50

          SecureListener=true

          AuthenticationEnabled=true

          NativeVersionEnabled=true

          CrashRecoveryEnabled=false

          JavaHome=C:\PROGRA~1\Java\JROCKI~1.1\jre

          StartScriptEnabled=true

          StopScriptEnabled=true

          StartScriptName=startWebLogic.cmd

          StopScriptName=

          LogFile=

          LogLevel=INFO

          LogLimit=0

          LogCount=1

          LogAppend=true

          LogToStderr=true

          LogFormatter=weblogic.nodemanager.server.LogFormatter

          DomainsFile=

          DomainsFileEnabled=true

          StateCheckInterval=500

           

          ??

           

          - Do you have your loopback adapter?

          - There were an installation or another thing that you do to get this issue?

          - Do you start node manager with the user that you install (not root)?

           

          Kind Regards,