1 2 Previous Next 20 Replies Latest reply on Apr 28, 2017 8:52 AM by Martien van den Akker

    WebLogic Server 'AdminServer' is not currently running

    TJCHAD

      Hello All,

       

      Product  OSB 12.2.1.2

       

      Followed Darwin-IT: Scripted Domain Creation for SOA/BPM, OSB 12.2.1 and successfully to create a domain. I am able to start Admin and manageServer using weblogic start up script startWeblogic.sh and startManagerServer.sh.


      However when i tried to start the server using wlst command startNodeManager getting below error.

       

       

      Error Stack

      =========

       

      ls:/offline> nmConnect('nodeadmin','s0cO@ih17','gaxgpoa261vd','5556','custsvc_osb','/oraapp/config/domains/custsvc_osb','ssl')

      Connecting to Node Manager ...

      Successfully Connected to Node Manager.

      wls:/nm/custsvc_osb> nmKill('AdminServer')

      Killing server AdminServer ...

      Traceback (innermost last):

        File "<console>", line 1, in ?

        File "<iostream>", line 150, in nmKill

        File "<iostream>", line 553, in raiseWLSTException

      WLSTException: Error occurred while performing nmKill : Error killing server AdminServer : Received error message from Node Manager Server: [WebLogic Server 'AdminServer' is not currently running]. Please check Node Manager log for details.

      Use dumpStack() to view the full stacktrace :

      wls:/nm/custsvc_osb> dumpStack()

      This Exception occurred at Tue Apr 18 12:11:58 EDT 2017.

      weblogic.nodemanager.NMException: Received error message from Node Manager Server: [WebLogic Server 'AdminServer' is not currently running]. Please check Node Manager log for details.

              at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:857)

              at weblogic.nodemanager.client.NMServerClient.kill(NMServerClient.java:142)

              at weblogic.nodemanager.client.DefaultSSLClient.kill(DefaultSSLClient.java:14)

              at weblogic.management.scripting.core.NodeManagerCoreService.nmKill(NodeManagerCoreService.java:425)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:498)

              at org.python.core.PyReflectedFunction.__call__(Unknown Source)

              at org.python.core.PyMethod.__call__(Unknown Source)

              at org.python.core.PyObject.__call__(Unknown Source)

              at org.python.core.PyObject.invoke(Unknown Source)

              at org.python.pycode._pyx3.nmKill$4(<iostream>:145)

              at org.python.pycode._pyx3.call_function(<iostream>)

              at org.python.core.PyTableCode.call(Unknown Source)

              at org.python.core.PyTableCode.call(Unknown Source)

              at org.python.core.PyTableCode.call(Unknown Source)

              at org.python.core.PyFunction.__call__(Unknown Source)

              at org.python.pycode._pyx124.f$0(<console>:1)

              at org.python.pycode._pyx124.call_function(<console>)

              at org.python.core.PyTableCode.call(Unknown Source)

              at org.python.core.PyCode.call(Unknown Source)

              at org.python.core.Py.runCode(Unknown Source)

              at org.python.core.Py.exec(Unknown Source)

              at org.python.util.PythonInterpreter.exec(Unknown Source)

              at org.python.util.InteractiveInterpreter.runcode(Unknown Source)

              at org.python.util.InteractiveInterpreter.runsource(Unknown Source)

              at org.python.util.InteractiveInterpreter.runsource(Unknown Source)

              at weblogic.management.scripting.utils.WLSTInterpreter.runsource(WLSTInterpreter.java:1095)

              at weblogic.management.scripting.WLST.main(WLST.java:227)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:498)

              at weblogic.WLST.main(WLST.java:47)

       

      Any help appreciated.

       

      Regards,

      TJ.

        • 1. Re: WebLogic Server 'AdminServer' is not currently running
          MichelSchildmeijer

          Hi

          Have you checked the nodemanager logs

          Usually this is a result of the fact that the nodemanager credentials are different from your WebLogic Admin credentials

           

          kind regards

          Michel

          • 2. Re: WebLogic Server 'AdminServer' is not currently running
            TJCHAD

            thanks Michel for the response. I tried changing the credential and unfortunately still getting the same error.

             

            This is the only error message 'weblogic.nodemanager.NMException: Received error message from Node Manager Server: [WebLogic Server 'AdminServer' is not currently running]. Please check Node Manager log for details.' i see it in nodemanager log

             

            Regards,

            TJ.

            • 3. Re: WebLogic Server 'AdminServer' is not currently running
              amey g

              Hello,

               

              Problem occurred sometime if you are using non certified java version. Please use JDK 1.8 with 12c OHS.

               

              To further debug enable the OHS logs at finest level

              Refer: https://docs.oracle.com/cd/E28280_01/web.1111/e10144/man_logs.htm

               

              Thanks,

              Amey

              • 4. Re: WebLogic Server 'AdminServer' is not currently running
                MichelSchildmeijer

                I  haven't seen any reference of the use of OHS or JDK version. This post is dealing about WebLogic 12.2.1 and OSB

                 

                Did you apply the nmEnroll command after changing and a restart of the AdminServer?

                • 5. Re: WebLogic Server 'AdminServer' is not currently running
                  TJCHAD

                  thanks Amey, yes i am using Jdk 1.8 and NO OHS.

                  • 6. Re: WebLogic Server 'AdminServer' is not currently running
                    TJCHAD

                    Hello Michel,

                     

                    we are using JDK 1.8. Yes i have applied nmEnroll on all the machines.

                    • 7. Re: WebLogic Server 'AdminServer' is not currently running
                      MichelSchildmeijer

                      Hi

                      Can you do an nmConnect and then an nmStart of the AdminServer

                      Because you used the startscript, the nodemanager probably doesnt know the healthstate of the AdminServer

                       

                      kind regards

                      Michel

                      • 8. Re: WebLogic Server 'AdminServer' is not currently running
                        TJCHAD

                        Hello Michel,

                         

                        I tried the same but no luck.

                        startNodeManager(verbose='true',NodeManagerHome='/oraapp/config/domains/custsvc_osb/nodemanager', ListenPort='5556',ListenAddress='GAXGPOA261VD')

                        Launching NodeManager ...

                        Running startNodeManager.sh from the directory /oraapp/config/domains/custsvc_osb/bin

                        NMProcess: + /oraapp/java/jdk1.8.0_112/bin/java -server -Xms32m -Xmx200m -Dcoherence.home=/oraapp/product/fmw/wlserver/../coherence -Dbea.home=/oraapp/product/fmw/wlserver/.. -DListenAddress=GAXGPOA261VD -DNodeManagerHome=/oraapp/config/domains/custsvc_osb/nodemanager -DQuitEnabled=true -DListenPort=5556 -Dweblogic.RootDirectory=/oraapp/config/domains/custsvc_osb -Doracle.security.jps.config=/oraapp/config/domains/custsvc_osb/config/fmwconfig/jps-config-jse.xml -Dcommon.components.home=/oraapp/product/fmw/oracle_common -Dopss.version=12.2.1.2 -Dweblogic.RootDirectory=/oraapp/config/domains/custsvc_osb -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -Djava.security.policy=/oraapp/product/fmw/wlserver/server/lib/weblogic.policy -Dweblogic.nodemanager.JavaHome=/oraapp/java/jdk1.8.0_112 weblogic.NodeManager -v

                        NMProcess: NODEMGR_HOME is already set to /oraapp/config/domains/custsvc_osb/nodemanager

                        NMProcess: CLASSPATH=/oraapp/java/jdk1.8.0_112/lib/tools.jar:/oraapp/product/fmw/wlserver/server/lib/weblogic.jar:/oraapp/product/fmw/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-contrib.jar:/oraapp/product/fmw/wlserver/modules/features/oracle.wls.common.nodemanager.jar::/oraapp/java/jdk1.8.0_112/lib/tools.jar:/oraapp/product/fmw/wlserver/modules/features/wlst.wls.classpath.jar:/oraapp/product/fmw/wlserver/..

                        NMProcess: <Apr 25, 2017 8:52:28 AM EDT> <INFO> <Loading domains file: /oraapp/config/domains/custsvc_osb/nodemanager/nodemanager.domains>

                        The Node Manager is launched.

                        The Node Manager process is running independent of the WLST process.

                        Exiting WLST will not stop the Node Manager process. Please refer to the Node Manager logs for more information.

                        The Node Manager logs will be under /oraapp/config/domains/custsvc_osb/nodemanager

                        Launching Node Manager is completed.

                        NMProcess: Apr 25, 2017 8:54:17 AM oracle.security.opss.internal.runtime.ServiceContextManagerImpl getContext

                        NMProcess: WARNING: Bootstrap services are used by OPSS internally and clients should never need to directly read/write bootstrap credentials. If required, use Wlst or configuration management interfaces.

                        NMProcess: <Apr 25, 2017 8:54:17 AM EDT> <INFO> <Loaded NodeManager configuration properties from '/oraapp/config/domains/custsvc_osb/nodemanager/nodemanager.properties'>

                        NMProcess: Node manager v12.2.1.2.0

                        NMProcess:

                        NMProcess: Configuration settings:

                        NMProcess:

                        NMProcess: DomainsFile=/oraapp/config/domains/custsvc_osb/nodemanager/nodemanager.domains

                        NMProcess: LogLimit=0

                        NMProcess: DomainsDirRemoteSharingEnabled=false

                        NMProcess: AuthenticationEnabled=true

                        NMProcess: LogLevel=INFO

                        NMProcess: DomainsFileEnabled=true

                        NMProcess: ListenAddress=GAXGPOA261VD

                        NMProcess: NativeVersionEnabled=true

                        NMProcess: ProcessDestroyTimeout=20000

                        NMProcess: ListenPort=5556

                        NMProcess: LogToStderr=true

                        NMProcess: weblogic.StartScriptName=startWebLogic.sh

                        NMProcess: SecureListener=true

                        NMProcess: LogCount=1

                        NMProcess: QuitEnabled=true

                        NMProcess: LogAppend=true

                        NMProcess: weblogic.StopScriptEnabled=false

                        NMProcess: StateCheckInterval=500

                        NMProcess: CrashRecoveryEnabled=false

                        NMProcess: weblogic.StartScriptEnabled=true

                        NMProcess: LogFile=/oraapp/config/domains/custsvc_osb/nodemanager/nodemanager.log

                        NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter

                        NMProcess: coherence.StartScriptEnabled=false

                        NMProcess: ListenBacklog=50

                        NMProcess: NodeManagerHome=/oraapp/config/domains/custsvc_osb/nodemanager

                        NMProcess: weblogic.startup.JavaHome=/oraapp/java/jdk1.8.0_112

                        NMProcess: weblogic.startup.MW_Home=

                        NMProcess: coherence.startup.JavaHome=/oraapp/java/jdk1.8.0_112

                        NMProcess: coherence.startup.MW_Home=

                        NMProcess:

                        NMProcess: Domain name mappings:

                        NMProcess:

                        NMProcess: custsvc_osb -> /oraapp/config/domains/custsvc_osb

                        NMProcess:

                        NMProcess: <Apr 25, 2017 8:54:17 AM EDT> <INFO> <12.2.1.2.0>

                        NMProcess: <Apr 25, 2017 8:54:17 AM EDT> <INFO> <custsvc_osb> <AdminServer> <Startup configuration properties loaded from "/oraapp/config/domains/custsvc_osb/servers/AdminServer/data/nodemanager/startup.properties">

                        NMProcess: <Apr 25, 2017 8:54:17 AM EDT> <INFO> <Secure socket listener started on port 5556, host GAXGPOA261VD/xx.xx.xx.xxx>

                        ===================================================================================================================

                        wls:/offline> nmConnect('nodeadmin','s0cO@ih17','gaxgpoa261vd','5556','custsvc_osb','/oraapp/config/domains/custsvc_osb','ssl')

                        Connecting to Node Manager ...

                        Successfully Connected to Node Manager.

                        wls:/nm/custsvc_osb> nmStart('AdminServer')

                        Starting server AdminServer ...

                        NMProcess: <Apr 25, 2017 8:56:22 AM EDT> <WARNING> <Server start command for WebLogic server 'AdminServer' failed due to: [No such file or directory]. Please check Node Manager log and/or server 'AdminServer' log for detailed information.>

                        Traceback (innermost last):

                          File "<console>", line 1, in ?

                          File "<iostream>", line 188, in nmStart

                          File "<iostream>", line 553, in raiseWLSTException

                        WLSTException: Error occurred while performing nmStart : Error Starting server AdminServer : Received error message from Node Manager Server: [Server start command for WebLogic server 'AdminServer' failed due to: [No such file or directory]. Please check Node Manager log and/or server 'AdminServer' log for detailed information.]. Please check Node Manager log for details.

                        Use dumpStack() to view the full stacktrace :

                        wls:/nm/custsvc_osb>

                         

                         

                        Regards,

                        Tarak.

                        • 9. Re: WebLogic Server 'AdminServer' is not currently running
                          MichelSchildmeijer

                          Can you do nmstart('Adminserver')? I seem to remember this could be a spelling issue Do clean cache and tmp of the AdminServer upfront

                          • 10. Re: WebLogic Server 'AdminServer' is not currently running
                            TJCHAD

                            Hello Michel,

                             

                            Your answer is helpful. I am able to make it progress but ended up with some errors.

                             

                            I have few questions here

                             

                            1) Why i am getting name conflict error? When i create domain in GUI mode i dont have any issues with admin server name..it works well with the name AdminServer.

                            2) How to resolve it?

                             

                            Also to add, when i run nmStart('Adminserver') its altogether creating new server folder.

                            error :-

                            ===================

                            <Apr 25, 2017 9:49:16 AM EDT> <Info> <RCM> <BEA-2165021> <"ResourceManagement" is not enabled in this JVM. Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.>

                            <Apr 25, 2017 9:49:16 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.2.1.2.0 Mon Oct  3 04:35:36 PDT 2016 1827450>

                            <Apr 25, 2017 9:51:07 AM EDT> <Info> <Management> <BEA-141223> <The server name Adminserver specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer,custsvc_osb_server1}.>

                            <Apr 25, 2017 9:51:07 AM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

                             

                             

                            There are 1 nested errors:

                             

                             

                            weblogic.management.ManagementException: [Management:141223]The server name Adminserver specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer,custsvc_osb_server1}.

                                    at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(RuntimeAccessImpl.java:436)

                                    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:72)

                                    at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:76)

                                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

                                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                                    at java.lang.reflect.Method.invoke(Method.java:498)

                                    at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1262)

                                    at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:332)

                                    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:374)

                                    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)

                                    at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:232)

                                    at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)

                                    at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2020)

                                    at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)

                                    at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:693)

                                    at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:78)

                                    at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:211)

                                    at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:234)

                                    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:357)

                                    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)

                                    at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:232)

                                    at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)

                                    at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2020)

                                    at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)

                                    at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:693)

                                    at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:78)

                                    at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:211)

                                    at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:234)

                                    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:357)

                                    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)

                                    at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:232)

                                    at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)

                                    at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2020)

                                    at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)

                                    at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:693)

                                    at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:78)

                                    at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:211)

                                    at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:234)

                                    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:357)

                                    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)

                                    at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:232)

                                    at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)

                                    at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2020)

                                    at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)

                                    at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:88)

                                    at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1213)

                                    at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1144)

                                    at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$UpOneLevel.run(CurrentTaskFuture.java:762)

                                    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

                                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

                                    at java.lang.Thread.run(Thread.java:745)

                            • 11. Re: WebLogic Server 'AdminServer' is not currently running
                              MichelSchildmeijer

                              How is the name of the AdminServer defined in your domain creation script?

                              • 12. Re: WebLogic Server 'AdminServer' is not currently running
                                Martien van den Akker

                                Hi TJChad,

                                 

                                Nice that you used my script.

                                There is however one tiny, nasty  problem with it: It sets java-args properties for the managed server. Should remove that from the script.

                                The thing is that when setting those java-args you should also set the arguments to the sysout and syserr streams. But those require a full, absolute path. And the script sets it as a relative path, hence the 'no such file or directory' message.

                                 

                                The AdminServer can be started with the startWeblogic.sh script. Could you try to do so and in the console remove the java arguments on the Server Start tab on all the managed servers? Then stop the AdminServer and try to start it using the nodemanager. This might solve the trick.

                                 

                                Then remove in the script the lines

                                 

                                  print ('. Set Arguments to: '+javaArgs)

                                  set('Arguments' , javaArgs)

                                For both the managed servers and admin server.

                                 

                                Regards,
                                Martien

                                • 14. Re: WebLogic Server 'AdminServer' is not currently running
                                  Martien van den Akker

                                  There was indeed a misspelling of the Adminserver name earlier.

                                   

                                  What you can check out is to do the following in wlst:

                                  readDomain('YourDomainLocation')

                                  ls()

                                   

                                  Check the adminserver name in the properties.

                                   

                                  Regards,
                                  Martien

                                  1 2 Previous Next