注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

mylotustips的博客

IBM Lotus协作产品家族经验分享

 
 
 

日志

 
 
关于我

欢迎大家使用SR向IBM800提交问题http://www.ibm.com/support/servicerequest 可以随时查看问题状态,上传文件

网易考拉推荐

通过WAS管理控制台ISC无法启动Nodeagent  

2014-11-11 17:29:04|  分类: SocialBusiness |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |

问题:通过ISC无法启动Nodeagent,显示为红色

解决:

在日志logs\ffdc\dmgr_31405a70_14.11.08_17.42.12.3488072783210507226705

.txt中看到ADMU3027E可能由于此前启动的Nodeagent未关闭,导致Nodeagent检测到还有开启的进程因而启动失败。

[14-11-8 17:42:12:348 CST] FFDC

Exception:javax.management.MBeanException

SourceId:com.ibm.ws.management.AdminServiceImpl.invoke ProbeId:679

Reporter:com.ibm.ws.management.AdminServiceImpl$1@aa08bfb6

javax.management.MBeanException: Exception thrown in RequiredModelMBean

while trying to invoke operation launchProcess

at

javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredMode

lMBean.java:1112)

at

javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean

.java:966)

at

com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBea

nServerInterceptor.java:848)

at

com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)

at

com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1335)

at

com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.

java:118)

at

com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1228

)

at

com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServic

eDelegator.java:181)

at

com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter.java:247

)

at

com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doWork(IPCCo

nnectorInboundLink.java:360)

at

com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPCConnector

ReadCallback.complete(IPCConnectorInboundLink.java:602)

at

com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallba

ck.complete(SSLReadServiceContext.java:1784)

at

com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(Ai

oReadCompletionListener.java:165)

at

com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.

java:217)

at

com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFu

ture.java:161)

at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

at

com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java

:775)

at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)

Caused by: com.ibm.websphere.management.exception.AdminException:

Process lccluster_server1 failed to launch:

com.ibm.websphere.management.exception.AdminException: ADMU3027E

at

com.ibm.ws.management.nodeagent.NodeAgent.launchProcessPrivate(NodeAgent

.java:1470)

at

com.ibm.ws.management.nodeagent.NodeAgent.launchProcess(NodeAgent.java:1

217)

at

com.ibm.ws.management.nodeagent.NodeAgent.launchProcess(NodeAgent.java:1

188)

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

at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav

a:60)

at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor

Impl.java:37)

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

at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:49)

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

at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav

a:60)

at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor

Impl.java:37)

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

at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:256)

at

javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredMode

lMBean.java:1085)

... 19 more

Caused by: com.ibm.websphere.management.exception.AdminException:

ADMU3027E

at

com.ibm.ws.management.nodeagent.NodeAgent.launchProcessPrivate(NodeAgent

.java:1346)

... 32 more

 

建议将OS重启后,依次运行:

 

a. Start DMGR: ./startManager.bat

from D:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin

b. Start nodeagent: ./startNode.bat

from D:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin

c. Start Connections node: ./startServer.bat lccluster_server1

from D:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin

 

如果还是有问题,建议客户再按照以下步骤收集日志

 

MustGather: Nodeagent and Deployment Manager discovery problems

http://www-01.ibm.com/support/docview.wss?uid=swg21196220

 

In the administrative console under System Administration > Nodes, the node in question has a status of Unknown, or it is using wsadmin and is not able to get the $AdminControl MBean object for the nodeagent. However, the nodeagent and the Deployment Manager are running. 

The nodeagent and Deployment Manager must discover each other to have synchronization and administrative commands work properly on the base node. There are multiple reasons why the nodeagent and the Deployment Manager might not be able to talk to each other correctly. 

  • Tracing the discovery process on the nodeagent and dmgr:
    • Stop all Application Server processes (no Java processes).
    • Modify the server.xml files for both nodeagent and dmgr:
      • Enable discovery tracing on the dmgr:
        • Edit the server.xml file for the dmgr located in the following directory:
          ND_PROFILE/config/cells/cell_name/nodes/node_name/servers/dmgr

          D:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\WIN-Cell01\nodes\WIN-CellManager01\servers\dmgr\server.xml

        • Find the TraceService XML tag section.
        • Modify the startupTraceSpecification entry to look like the following:
          • com.ibm.ws.management.*=all
        • Make sure enable is set to true.
      • Enable discovery tracing on the nodeagent:
        • Edit the server.xml file for the nodeagent located in the following directory:

          BASE_PROFILE/config/cells/cell_name/nodes/node_name/servers/nodeagent
          D:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\WIN-Cell01\nodes\WIN-CellManager01\servers\nodeagent\server.xml
        • Find the TraceService XML tag section.
        • Modify the startupTraceSpecification entry to look like the following:
          • com.ibm.ws.management.*=all
        • Make sure enable is set to true.
    • Clear all the files in the following directories:



      BASE_PROFILE/logs

      D:\IBM\WebSphere\AppServer\profiles\logs

      ND_PROFILE/logs

      D:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs

    • Issue the following command:

      netstat -an > before.txt
    • Start the nodeagent and dmgr.
    • Open the administrative console and navigate to System administration > Nodes to see if the node still has a status of Unknown.
    • Issue the following command:

      netstat -an > after.txt
    • Stop the nodeagent and dmgr.
    • Run the collector tool on both Network Deployment and base.
  评论这张
 
阅读(2525)| 评论(0)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2017