WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

change primary administration user ldap not propagating to second node

  • 1.  change primary administration user ldap not propagating to second node

    Posted Thu August 23, 2012 05:35 PM
    Hello,

    I went through a basic ND install into a 2 node environment of Application server. Intially I set up any admin users just as "admin." Once I had everything set up and running I went to set up ldap. With this I just changed my primary admin user from "admin" to a service account that authenticates with ldap. So then I go to restart everything for the change to take effect after syncing everything. Well it takes effect just fine but then i check my nodes and they are out of sync. I try to sync them and my 02 node has authentication errors. I cannot start any app servers or sync my nodes now. Is there something else I need to edit? What am I doing wrong?

    Thanks,
    tj 


  • 2.  change primary administration user ldap not propagating to second node

    Posted Fri August 24, 2012 10:28 AM
    Hi TJ.

    From my experience it's likely something with the synchNode command.  Below is a link with the syntax you should be following.

    pic.dhe.ibm.com/infocenter/wasinfo/v7r0/...

    You access the remote host where Node 2 resides.
    Issue the synchNode command from the BIN directory for the profile.
    Enter the username and password (unless you put it in the command line)

    The synchNode command should provide feedback to the console indicating any errors. 

    If you encounter issues, please copy and paste the console commands and output (removing sensative information.) as well as the relavent information from the nodeagent systemOut.log

    Good luck,
    Erik