1 2 Previous Next 17 Replies Latest reply on Aug 26, 2015 3:10 AM by Ramaraju

    adnodemgrctl.sh: exiting with status 1 in EBS R12.2

    Ramaraju

      HI all,

      While bring up the R12.2.4 instance getting below error.

      adnodemgrctl.sh: exiting with status 1

      Error in log file:

      WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at vzgaswini.srisys.com:5556.

      Please help on this.

       

      Thanks,

      Ramaraju

        • 1. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
          Ramaraju

          Anyone can help on this issue. We are still getting same issue.

          When I check the status of node manager it running, but While bringing up all the application services it is failed.

          sh adnodemgrctl.sh status

          You are running adnodemgrctl.sh version 120.11.12020000.11

          Enter the WebLogic Admin password:

          The Node Manager is running

          adnodemgrctl.sh: exiting with status 0

           

          Thanks,

          Ramaraju.

          • 2. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
            2645656

            Hi,

             

            Please review Preclone Is Not Generating Moveplan.xml Files While Creating Patch File System (Doc ID 1615332.1)


            and perform the steps as described in the note.


            Regards,

            Harsha

            • 3. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
              Pravin Takpire

              Check this metalink note

               

              11g
              Grid Control Failed To Start With Error
              'weblogic.nodemanager.NMConnectException: Connection refused. Could not
              connect to NodeManager.' (Doc ID 1555341.1)

               

              regards

              Pravin

              • 4. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                Ramaraju

                Hi,

                Which managed servers I can delete as per the given Doc ID 1615332.1 2. Under the Domain Structure section, select Environment > Servers. Click on the Lock & Edit button in the 'Change Center' panel and delete the managed servers whose machine is configured as <hostname>_<offset>. For example, managed servers corresponding to your source secondary nodes. Click on the Activate Changes button in the 'Change Center' panel to activate the changes after deletion.

                Please see below

                Name Sorted Ascending Cluster Machine State Health Listen Port
                AdminServer(admin)myhostRUNNINGhttp://hydaswini.srisys.com:7006/console/images/checkmark_status.gif OK7006
                forms-c4ws_server1forms-c4ws_cluster1myhostRUNNINGhttp://hydaswini.srisys.com:7006/console/images/checkmark_status.gif OK7806
                forms_server1forms_cluster1myhostRUNNINGhttp://hydaswini.srisys.com:7006/console/images/checkmark_status.gif OK7406
                oacore_server1oacore_cluster1myhostRUNNINGhttp://hydaswini.srisys.com:7006/console/images/checkmark_status.gif OK7206
                oafm_server1oafm_cluster1myhostRUNNINGhttp://hydaswini.srisys.com:7006/console/images/checkmark_status.gif OK7606

                 

                Thanks,

                Ramaraju

                • 5. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                  2645656

                  This could be even due to the node manager password being corrupt.

                  Can you change the node manager password and re-test the issue.

                   

                  Regards,

                  Harsha

                  • 6. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                    Ramaraju

                    How can we know that node manager password corrupt ? And how can I change node manager password ?

                    • 7. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                      Ramaraju

                      I found below error in adnodemgrctl.txt file.

                      Connecting to Node Manager ...

                      Traceback (innermost last):

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

                        File "<iostream>", line 123, in nmConnect

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

                      WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at hydaswini.srisys.com:5561.

                      Use dumpStack() to view the full stacktrace

                       

                      Thanks,

                      Ramaraju

                      • 8. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                        Pravin Takpire

                        Check for below

                         

                        After installing the software and before starting the deployment

                        update :
                        ${ORACLE_HOME}/provisioning/idm-provisioning-build/templates/wait_for_nodemanager_template.py

                        replace
                          java.Thread.sleep(1000 * 10)
                        with
                          java.Thread.sleep(10000 * 60)

                         

                        Search for file wait_for_nodemanager_template.py and change.

                         

                        regards

                        Pravin

                        • 9. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                          Ramaraju

                          I didn't find wait_for_nodemanager_template.py file in my instance. If you know the location please tell me.

                           

                          Thanks,

                          Ramaraju

                          • 10. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                            Ramaraju

                            Anyone please advice on this. We are getting this issue while starting application services, after that checking status of node manager it is showing running state.

                             

                            Thanks,

                            Ramaraju.

                            • 11. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                              Ramaraju

                              Hi,

                              I have changed the node manager password but still I am facing same issue.

                              The following is the node manager dnodemgrctl.txt file

                               

                              07/17/15-01:08:19 :: adnodemgrctl.sh version 120.11.12020000.11

                              Calling txkChkEBSDependecies.pl to perform dependency checks for ALL MANAGED SERVERS

                              Program : /u02/oracle/VISMA/fs1/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkChkEBSDependecies.pl started @ Fri Jul 17 01:08:21 2015

                              *** Log File = /u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/logs/appl/rgf/TXK/txkChkEBSDependecies_Fri_Jul_17_01_08_21_2015/txkChkEBSDependecies_Fri_Jul_17_01_08_21_2015.log

                              Perl script txkChkEBSDependecies.pl got executed successfully

                              Validated the passed arguments for the option ebs-get-nmstatus

                              Traceback (innermost last):

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

                                File "<iostream>", line 123, in nmConnect

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

                              WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at hydaswini.srisys.com:5561.

                              Use dumpStack() to view the full stacktrace

                              Connecting to Node Manager ...

                              The Node Manager is not up.

                              Validated the passed arguments for the option ebs-start-nm

                              Checking if the Node Manager is already up..

                              Traceback (innermost last):

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

                                File "<iostream>", line 123, in nmConnect

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

                              WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at hydaswini.srisys.com:5561.

                              Use dumpStack() to view the full stacktrace

                              Connecting to Node Manager ...

                              Launching NodeManager ...

                              Properties: {Arguments=-Djava.security.egd=file:/dev/./urandom,JavaHome=/u02/oracle/VISMA/fs1/EBSapps/comn/util/jdk64,ListenAddress=hydaswini.srisys.com,ListenPort=5561,LogAppend=false,NodeManagerHome=/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1,SecureListener=false,StartScriptEnabled=false,StartScriptName=startWebLogic.sh,}

                              Command: /u02/oracle/VISMA/fs1/EBSapps/comn/util/jdk64/jre/bin/java -classpath /u02/oracle/VISMA/fs1/EBSapps/comn/util/jdk64/jre/lib/rt.jar:/u02/oracle/VISMA/fs1/EBSapps/comn/util/jdk64/jre/lib/i18n.jar:/u02/oracle/VISMA/fs1/FMW_Home/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u02/oracle/VISMA/fs1/EBSapps/comn/util/jdk64/lib/tools.jar:/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic_sp.jar:/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u02/oracle/VISMA/fs1/FMW_Home/modules/features/weblogic.server.modules_10.3.6.0.jar:/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/server/lib/webservices.jar:/u02/oracle/VISMA/fs1/FMW_Home/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/u02/oracle/VISMA/fs1/FMW_Home/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/u02/oracle/VISMA/fs1/FMW_Home/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/u02/oracle/VISMA/fs1/FMW_Home/oracle_common/webcenter/modules/oracle.portlet.server_11.1.1/oracle-portlet-api.jar:/u02/oracle/VISMA/fs1/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbyclient.jar:/u02/oracle/VISMA/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u02/oracle/VISMA/fs1/EBSapps/comn/java/classes/oracle/apps/fnd/jar/adall.jar weblogic.NodeManager -v

                              Successfully launched the Node Manager.

                              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 /u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1

                              Node Manager starting in the background

                              Traceback (innermost last):

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

                                File "<iostream>", line 123, in nmConnect

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

                              WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at hydaswini.srisys.com:5561.

                              Use dumpStack() to view the full stacktrace

                              Connecting to Node Manager ...

                              Traceback (innermost last):

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

                                File "<iostream>", line 123, in nmConnect

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

                              WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at hydaswini.srisys.com:5561.

                              Use dumpStack() to view the full stacktrace

                              Connecting to Node Manager ...

                              Traceback (innermost last):

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

                                File "<iostream>", line 123, in nmConnect

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

                              WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at hydaswini.srisys.com:5561.

                              Use dumpStack() to view the full stacktrace

                              Connecting to Node Manager ...

                              NMProcess: <Jul 17, 2015 1:08:38 AM> <INFO> <Loading domains file: /u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.domains>

                              NMProcess: Jul 17, 2015 1:08:38 AM weblogic.nodemanager.server.NMServerConfig initDomainsMap

                              NMProcess: INFO: Loading domains file: /u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.domains

                              NMProcess: <Jul 17, 2015 1:08:38 AM> <INFO> <Loaded node manager configuration properties from '/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.properties'>

                              NMProcess: Jul 17, 2015 1:08:38 AM weblogic.nodemanager.server.NMServer <init>

                              NMProcess: INFO: Loaded node manager configuration properties from '/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.properties'

                              NMProcess: Node manager v10.3

                              NMProcess:

                              NMProcess: Configuration settings:

                              NMProcess:

                              NMProcess: NodeManagerHome=/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1

                              NMProcess: ListenAddress=hydaswini.srisys.com

                              NMProcess: ListenPort=5561

                              NMProcess: ListenBacklog=50

                              NMProcess: SecureListener=false

                              NMProcess: AuthenticationEnabled=true

                              NMProcess: NativeVersionEnabled=true

                              NMProcess: CrashRecoveryEnabled=false

                              NMProcess: JavaHome=/u02/oracle/VISMA/fs1/EBSapps/comn/util/jdk64

                              NMProcess: StartScriptEnabled=false

                              NMProcess: StopScriptEnabled=false

                              NMProcess: StartScriptName=startWebLogic.sh

                              NMProcess: StopScriptName=

                              NMProcess: LogFile=/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.log

                              NMProcess: LogLevel=INFO

                              NMProcess: LogLimit=0

                              NMProcess: LogCount=1

                              NMProcess: LogAppend=false

                              NMProcess: LogToStderr=true

                              NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter

                              NMProcess: DomainsFile=/u02/oracle/VISMA/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.domains

                              NMProcess: DomainsFileEnabled=true

                              NMProcess: StateCheckInterval=500

                              NMProcess: QuitEnabled=true

                              .end std out.

                              .end err out.

                              07/17/15-01:09:18 :: adnodemgrctl.sh: exiting with status 1

                               

                              Thanks,

                              Ramaraju

                              • 12. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                                2754670

                                Hi Ramaraju,

                                 

                                Have your issue resolved? Is there any workaround for above issue?. We are also facing the same issue.

                                 

                                Thanks

                                • 13. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                                  Ramaraju

                                  Not yet. But it not cause any issue with us. Just check with adnodemgrctl.sh status, it is running.

                                   

                                  Thanks,

                                  Ramaraju

                                  • 14. Re: adnodemgrctl.sh: exiting with status 1 in EBS R12.2
                                    Pravin Takpire

                                    as you say node manager is running, can you check below

                                     

                                    telnet server 5556

                                     

                                    regards

                                    Pravin

                                    1 2 Previous Next