Monday, April 19, 2010

[A search for "Check the add node log for details." returned very little, hence this entry..]

When adding the first node to a cluster,all the configuration and applications are retrieved from it.This may take a while. The output you see in the Node Deployment Manager console looks like this:

ADMU0001I: Begin federation of node node01 with Deployment Manager at mgrnode.company.org:8879.ADMU0009I: Successfully connected to Deployment Manager Server: mgrnode.company.org:8879ADMU0505I: Servers found in configuration:ADMU0506I: Server name: server1ADMU0506I: Server name: webserver01ADMU0506I: Server name: WebSphere_PortalADMU2010I: Stopping all server processes for node node01ADMU0510I: Server server1 is now STOPPEDADMU0510I: Server WebSphere_Portal is now STOPPEDADMU0024I: Deleting the old backup directory.ADMU0015I: Backing up the original cell repository.ADMU0012I: Creating Node Agent configuration for node: node01ADMU0120I: isclite.ear will not be uploaded since it already exists in the target repository.ADMU0120I: isclite.ear will not be uploaded since it already exists in the target repository.ADMU0014I: Adding node node01 configuration to cell: mgrnodeCell01The console has not received information on the add operation in a timely manner. The state of the operation is indeterminate. Check the add node log for details.

The addNode.log file is on the server you added to the cluster, in ...\WebSphere\wp_profile\logs\addNode.log.

About Me

I have worked mostly with small companies / start-ups, building whatever is required and chasing moving targets. I still do some of this, keeping up on technology, tools, and trying to stay bleeding edge. (There's too many edges though.)

I like to know how things work, including the internet, physics, science, chemistry, biology.