After successfully adding a node to a remote deployment manager, I somehow f
ailed to get the node running.

After several attempts of activating it, I've decided to remove the node and
 do it all over again, but eventually the same error occurred.

An attempt to start the remote node from dmgr console ended up with this err
or:
"The node agent on node anacondaNode01 must be started to perform the restar
t operation. Node agents in stopped state can not be started from the consol
e."

An attempt to start the remote node agent locally is a success:

C:\Program  Files\IBM\WebSphere\AppServer\profiles\A
ppSrv03\bin>startnode
ADMU0116I: Tool information is being logged in file C:\Program
 Files\IBM\WebSphere\AppServer\profiles\A
ppSrv03\logs\nodeagent\startS
erver.log
ADMU0128I: Starting tool with the AppSrv03 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 2180


After refreshing the dmgr console several times, the node agent is still not
 active.

Are there any steps that I'm missing out?

Please help.

Thanks.

[ Post a follow-up to this message ]

You don't say what version you're on, but the first thing I would do is
apply an fix packs that you don't have ...

gadidot@gmail.com wrote:
> After successfully adding a node to a remote deployment manager, I somehow
 failed to get the node running.
>
> After several attempts of activating it, I've decided to remove the node a
nd do it all over again, but eventually the same error occurred.
>
> An attempt to start the remote node from dmgr console ended up with this e
rror:
> "The node agent on node anacondaNode01 must be started to perform the rest
art operation. Node agents in stopped state can not be started from the cons
ole."
>
> An attempt to start the remote node agent locally is a success:
>
> C:\Program  Files\IBM\WebSphere\AppServer\profiles\A
ppSrv03\bin>startnode
> ADMU0116I: Tool information is being logged in file C:\Program
>  Files\IBM\WebSphere\AppServer\profiles\A
ppSrv03\logs\nodeagent\startS
> erver.log
> ADMU0128I: Starting tool with the AppSrv03 profile
> ADMU3100I: Reading configuration for server: nodeagent
> ADMU3200I: Server launched. Waiting for initialization status.
> ADMU3000I: Server nodeagent open for e-business; process id is 2180
>
>
> After refreshing the dmgr console several times, the node agent is still n
ot active.
>
> Are there any steps that I'm missing out?
>
> Please help.
>
> Thanks.

[ Post a follow-up to this message ]

Dmgr<->nodeagent communication problems?... The things I would check:

Is the "...\profiles\AppSrv03\logs\addNode.log" clean? Are there any excepti
ons/warnings?

Did you try "...\profiles\AppSrv03\bin\syncNode.bat" (with following inspect
ion of the syncNode.log)?

Were any changes in the network made after you've added the node? Like firew
all between dmgr's host
and node's host was setup or reconfigured (if any already exists)

After you start the nodeagent, what does netstat say on both - dmgr and node
 - boxes? Are the proper
IP connections established between dmgr process and nodeagent process?

[ Post a follow-up to this message ]

Paul Ilechko:
"You don't say what version you're on, but the first thing I would do is
apply an fix packs that you don't have ..."
Sorry, it's WASND 6.0.0.1. And I haven't applied any fix packs. Am very new 
to websphere and sometimes I tend to forget the crucial stuff. Thanks for po
inting this out.


Yuriy Petrov:
"Is the "...\profiles\AppSrv03\logs\addNode.log" clean? Are there any except
ions/warnings?"
The log is clean. Please see the attachment(I copied a portion of the log). 
Just in case if I missed out anything.

"Did you try "...\profiles\AppSrv03\bin\syncNode.bat" (with following inspec
tion of the syncNode.log)?"
Yes I did, and it was a success. No error. Even the log is clean (I copied a
 portion of the log).

"Were any changes in the network made after you've added the node? Like fire
wall between dmgr's host and node's host was setup or reconfigured (if any a
lready exists)"
Windows firewall only running on the machine with the deployment manager. Th
e other machine doesn't run any firewall. Hosts file on both machines have b
een edited by adding each machine's IP address and host name. Both machine c
an ping each other using ho
st name.

"After you start the nodeagent, what does netstat say on both - dmgr and nod
e - boxes? Are the proper IP connections established between dmgr process an
d nodeagent process?"
No connection established.

From machine running the AppSrv:
C:\>netstat -an | find /i "10.8.8.22"
TCP    10.8.8.167:9354        10.8.8.22:19829        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19831        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19839        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19841        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19842        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19844        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19845        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19846        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19847        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19849        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19851        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19854        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19855        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19858        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19859        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19860        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19863        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19865        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19867        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19870        TIME_WAIT
TCP    10.8.8.167:9354        10.8.8.22:19871        TIME_WAIT

[ Post a follow-up to this message ]

Uhmm.. or at least if anyone can tell if what I've done is correct:

Machine A: WASND with deployment manager and application server.
Machine B: WASND with a custom profile (empty node, federated to Dmgr in Mac
hine A)

No error during the addnode process.

Node federation (addnode) was done separately from the profile creation as I
 have enabled the security feature in Dmgr.

The only problem is I failed to activate it (activation was done from Machin
e B via command startnode/startserver nodeagent). As I have mentioned in my 
earlier post, the server status will show no server is active despite the su
ccess of the command execut
ion. Repeated command execution will end up with an error.

startnode/startserver nodeagent is not listed as windows services.

Thanks in advance.

[ Post a follow-up to this message ]

hi
try to restart the Dmgr..sometimes the changes may get effected when u resta
rt the dmgr only.

madhu

[ Post a follow-up to this message ]

Tried that and it didn't work.

[ Post a follow-up to this message ]

"Machine A: WASND with deployment manager and application server.
Machine B: WASND with a custom profile (empty node, federated to Dmgr in Mac
hine A)"

Just figured that machine B was infected with w32.fujacks.b worm.

According to symantec, the worm ends some security-related processes and ser
vices.
<http://www.symantec.com/security_re...t
abid=1>

I created an application server profile, list the nodeagent as a windows ser
vices and add the node to machine A.

In my previous post, I have mentioned that after the nodeagent has been star
ted successfully, the server status will still show that its status as 'stop
'. I did try starting the nodeagent from windows services. It started, befor
e it stopped after a few se
conds. Could this be due to the infection?

Any idea, anyone?

Thanks.

[ Post a follow-up to this message ]