We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

node agent issue + websphere 6.1 ND

Medium Priority
1,956 Views
Last Modified: 2013-12-10
I have two linux machines A and B. on machine A,i have installed a deployment mgr and a custom node and on machine B I have installed a custom node. custom node on machine B got sucessfully federated with deployment manager and is running fine but its status from console is topped.
Comment
Watch Question

Author

Commented:
any update
Software Engineer
CERTIFIED EXPERT
Commented:
As part of the federation, a stand-alone application server will be stopped, and
a node agent will be created, and started.

So, from the deployment manager admin console, you can now select the server, and "start" it (by clicking on the start button), or

you can issue a "startServer <serverName>" command from the profile/<profileName>/bin directory (./startServer.sh on linux),

or, you could use a wsadmin script to start the federated server.

What is your choice?

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
when i start federated node from console i get message that its node agent is not active inspite of the fact that its running. same case with wsaadmin script command.
HonorGodSoftware Engineer
CERTIFIED EXPERT

Commented:
Ah, but the federation was successful?  That's interesting.

Do you have security enabled on your DM?
Did you have it enabled on your AppServer before the federation step?

If so, were the security type, and userid/password the same for both the DM and the AppServer?

Please:
- Stop all servers
- Clear the logs directories for each profile
- Start the DM (using the startManager command line script)
- Start the nodeagent (using the startNode command line script)
- Start the AppServer (using the startServer command line script)

Zip up each "profiles/<ProfileName>/logs/<ServerName>" directories, and attach them here.

For example, I just started my DM, and the "profiles\Dmgr01\logs\dmgr" directory contains the following files:

dmgr.pid
native_stderr.log
native_stdout.log
startServer.log
SystemErr.log
SystemOut.log

Thanks

Commented:
Hello,

Could you provide me the SystemOut.log fromthe DMGR logs and Full zip of the Nodeagent logs

Thanks
HonorGodSoftware Engineer
CERTIFIED EXPERT

Commented:
dipinci:  How does you request differ from mine?

Author

Commented:
Please close this question
HonorGodSoftware Engineer
CERTIFIED EXPERT

Commented:
No justification for closure has been provided.
If they order of startup was the issue, then the answer provided above

http://www.experts-exchange.com/Q_24136630.html#a23629098

was the solution.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.