How to “start a node agent” in Websphere?

Question

How do you "start a node agent" in Websphere ? The error message is: "Server cannot be started because the node agent for server x_server on node wasdev1Node01 is not active." (I am on the dev server.)

Also, the app logon procedure errored because of "Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. ". While trying to start the JINDY I got the node server message.

When I try to start the application server:

"Server cannot be started because the node agent for server wasdev1 on node wasdev1Node01 is not active."

Starting the Node Agent from the console: "The node agent on node wasdev1Node01 must be started to perform the restart operation. Node agents in stopped state can not be started from the console."

You would need to start the node agent from command line as below.

WAS_HOME/profiles/YOUR_PROFILE_NAME/bin/startNode.cmd (I do not have this command.)

Answer 1

You would have the startNode.sh or startNode.cmd command linked in your profile's bin directory if your profile was created from a Network Deployment installation and your node had been federated into a cell. If your profile is a standalone application profile that has not been federated, there should not be a startNode command available.

Answer 2

Looking at the error you are running ND not standalone/base version. You cannot start the nodeagent from the console (only stop and restart. startNode.sh(.bat) from command line to start the nodeagent. Make sure nodeagent process/pid is not present. As for the applicatin servers defined under the node, they need Location Daemon Service running on the node to start.

Answer 3

Yes if the error appears only thing you need to start nodeagent from your appsrv profile/bin with command prompt only if you install on windows environment.

you should open as command prompt as administrator privileges and then go to profile path and run startNode.bat or .sh .