Hi Erman,
If nodemanager is down,can adstrtall script start admin and managed servers? Thanks in advance |
Administrator
|
No.. It uses WLST commands to start the managed servers.
You get the following type of errors, if you try to start the managed servers when your node manager is not up.. WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager . However, what you need to see in the logs is the following ; Checking if the Node Manager is already up.. Connecting to Node Manager ... Successfully Connected to Node Manager. Connecting to t3://somehost.somedomain:7001 with userid weblogic ... Successfully connected to Admin Server 'AdminServer' that belongs to domain 'EBS_domain_VIS'. Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead. Starting server oacore_server1 ... Successfully started server oacore_server1 ... Started up the Managed Server oacore_server1 admanagedsrvctl.sh: exiting with status 0 |
In reply to this post by raam
Hi Erman,
Is this applies for admin server as well?I mean, can adstrtall.sh script start admin server when node manager is down? Also,As you have updated when node manager is down,adstrtall.sh script cannot start managed servers.In this case,will we be able to start managed servers with admanagedsrvtl script? |
Administrator
|
your node manager should be up. 27 Mar 2017 20:35 tarihinde "satish [via Erman Arslan's Oracle Forum]" <[hidden email]> yazdı: Hi Erman, |
Hi Erman,
It is confusion to many of us and ur blog really helps. To conclude,without node manager,either adatrtall.ah or adadminsrvctl.sh/admanagedsrvctl.sh cannot start admin and managed servers.pls correct if it is wrong. Also in this case,can we start them using native weblogic scripts under domain home bin,I dont think nomanager is needed here Thank you |
Administrator
|
The lines that are used for starting the admin server, in the adadminsrvctl script is as follows;
printf "Starting WLS Admin Server...\n" fi { echo $wlspass; } | perl /u01/install/APPS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/adProvisionEBS.pl -contextfile=/u01/install/APPS/fs2/inst/apps/ORAPROD_daroraappsrv1/appl/admin/ORAPROD_daroraappsrv1.xml ebs-nmstart-adminsrv -wlsadminuser=weblogic -wlsadminport=7002 -domain=EBS_domain_ORAPROD -domainhome="/u01/install/APPS/fs2/FMW_Home/user_projects/domains/EBS_domain_ORAPROD" -nmhome="/u01/install/APPS/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1" -nmport=5557 -nmtype=plain -machinelistenaddress="ERMANSRV" -promptmsg=hide -serverstartargs="-XX:PermSize=128m -XX:MaxPermSize=384m -Xms1024m So, as you see, it takes the Node manager arguments there. adadminsrvctl.sh itself starts the node manager if it is not up. so the answer for your question is; " node manager must not be up, but it is able to be up, when the adadminsrvctl.sh starts) Note: This is EBS and we don't use weblogic scripts or Weblogic console (these are last resorts really). |
Administrator
|
Here is the proof for you..
I just move the nm_password.properties file(node manager's password config file) and try to start the admin server using adadminsrvctl.sh and as you below, adadminsrvctl.sh returns error. (status 1) So ,as I said.. It is dependent to the node manager by design. WARNING: I/O error while reading domain directory NMProcess: java.io.FileNotFoundException: Node manager user properties file '/u01/install/APPS/fs2/FMW_Home/user_projects/domains/EBS_domain_ORATEST/config/nodemanager/nm_password.properties' not found NMProcess: at weblogic.nodemanager.server.DomainManager.loadUserInfo(DomainManager.java:136) NMProcess: at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:90) NMProcess: at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:60) NMProcess: at weblogic.nodemanager.server.NMServer.findOrCreateDomainManager(NMServer.java:284) NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:273) NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:235) NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:117) NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:73) NMProcess: at java.lang.Thread.run(Thread.java:724) NMProcess: Refer /u01/install/APPS/fs2/inst/apps/ORATEST_ermansrv/logs/appl/admin/log/adadminsrvctl.txt for details adadminsrvctl.sh: exiting with status 1 |
Free forum by Nabble | Edit this page |