david.barron@zencos.com wrote:
> I've got this sudden problem with WebSphere 6.1 and I am not finding anything on the web that is helpful.
>
> I login and execute /opt/IBM/WebSphere/AppServer/bin/startManager.sh. That seems to work fine. Now, of course I want to start up nodeagent so I execute /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/startNode.sh and that's when the fun starts. The output is:
> ADMU0116I: Tool information is being logged in file
> /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/startServer.log
> ADMU0128I: Starting tool with the AppSrv01 profile
> ADMU3100I: Reading configuration for server: nodeagent
> ADMU3200I: Server launched. Waiting for initialization status.
> ADMU3011E: Server launched but failed initialization. startServer.log,
> SystemOut.log(or job log in zOS) and other log files under
> /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent should
> contain failure information.
>
> First, there's is no SystemOut.log file there, so that's no help.
> Second, the only log that is generated, startServer.log, doesn't give any more information so I'm stuck.
>
> I've tried syncNode.sh as suggested elsewhere but that makes no difference at all.
>
> Is there anyone or anything that can help me?

Sounds like it might be a permissions problem, or a directory exists
with that name or something odd like that.

Ken

No sure if it will help, there are some logs scatter around. just wonder if that helps in anyway e.g.

/logs/activity.log
/logs/ffdc/

help it helps.

regards,
KJ

serverindex.xml may be corrupt or other configuration XML file issue.

2. Host entr

2. Host Entry is a common issue where nodeagent fails to start.
-- Ensure that you have the correct hostname and ip

I've looked at the logs mentioned and there isn't any information there either.
The hosts file contains the following:

#
# Internet host table
#
127.0.0.1 localhost
10.0.0.11 zendevsun01 loghost

which is correct.

I am seeing something in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/server1/startServer.log that I just noticed:

[3/11/09 14:38:25:489 EDT] 0000000a AdminTool A ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.NoServerDef inedException: No configuration defined for server: server1
at com.ibm.ws.management.launcher.LaunchCommand.(Laun chCommand.java:165)
at com.ibm.ws.management.tools.WsServerLauncher.initi alizeRepositoryAndLauncher(WsServerLauncher.java:3 82)
at com.ibm.ws.management.tools.WsServerLauncher.runTo ol(WsServerLauncher.java:257)
at com.ibm.ws.management.tools.AdminTool.executeUtili ty(AdminTool.java:261)
at com.ibm.ws.management.tools.WsServerLauncher.main( WsServerLauncher.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:263)

[3/11/09 14:38:25:492 EDT] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 111
[3/11/09 14:38:25:493 EDT] 0000000a AdminTool A ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/server1/startServer.log
[3/11/09 14:38:25:495 EDT] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 211
[3/11/09 14:38:25:496 EDT] 0000000a AdminTool 3 Returning from executeUtility method with return code: -1


Could this be related?

check out native_stderr and native_stdout logs under /logs directory it should contains some additional failure information.

Thanks,

I noticed those log files, they are both empty.

Maybe some new information though. In researching the NoServerDefinedException I found this:

http://www-01.ibm.com/support/docvie...id=swg21176517

When I try the syncNode.sh command as shown there I'm getting this:

ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/syncNode.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU0401I: Begin syncNode operation for node zendevsun01CellManager01 with
Deployment Manager zendevsun01: 8879
ADMU0111E: Program exiting with error: java.io.FileNotFoundException:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/zendevsun01Cell01/nodes/zendevsun01CellManager01/servers/nodeagent/server.xml
(No such file or directory)
ADMU0211I: Error details may be seen in the file:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/syncNode.log


The syncNode.log file says more or less the same thing. The directory
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/zendevsun01Cell01/nodes/zendevsun01CellManager01/servers
is missing the nodeagent directory.
I assume I don't just manually create the directory, so there must be a command to build it.

Thanks

david.barron@zencos.com wrote:
> I noticed those log files, they are both empty.
>
> Maybe some new information though. In researching the NoServerDefinedException I found this:
>
> http://www-01.ibm.com/support/docvie...id=swg21176517
>
> When I try the syncNode.sh command as shown there I'm getting this:
>
> ADMU0116I: Tool information is being logged in file
> /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/syncNode.log
> ADMU0128I: Starting tool with the Dmgr01 profile
> ADMU0401I: Begin syncNode operation for node zendevsun01CellManager01 with
> Deployment Manager zendevsun01: 8879
> ADMU0111E: Program exiting with error: java.io.FileNotFoundException:
> /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/zendevsun01Cell01/nodes/zendevsun01CellManager01/servers/nodeagent/server.xml
> (No such file or directory)
> ADMU0211I: Error details may be seen in the file:
> /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/syncNode.log
>
>
> The syncNode.log file says more or less the same thing. The directory
> /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/zendevsun01Cell01/nodes/zendevsun01CellManager01/servers
> is missing the nodeagent directory.
> I assume I don't just manually create the directory, so there must be a command to build it.
>
> Thanks

Are you in the right directory to start running the nodeagent? you're in
the dmgr profile's directory.

Ken