ConfigEngine.bat cluster-node-config-cluster-setup failed in Portal6.1.0.1 - Websphere

This is a discussion on ConfigEngine.bat cluster-node-config-cluster-setup failed in Portal6.1.0.1 - Websphere ; Hi, I am having an issue while running "*ConfigEngine.bat cluster-node-config-cluster-setup*" in WebSphere Portal 6.1.0.1. The below tasks are completed successfully: ------------------------------------------------------------------------------------ *ConfigEngine.bat cluster-node-config-pre-federation -DDMgrUserid=uid= ,o=defaultWIMFileBasedRealm -DDMgrPassword= * WasUserId= WasPassword= CellName= *ConfigEngine.bat cluster-node-config-post-federation* ------------------------------------------------------------------------------------ The below config task is failed as ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: ConfigEngine.bat cluster-node-config-cluster-setup failed in Portal6.1.0.1

  1. ConfigEngine.bat cluster-node-config-cluster-setup failed in Portal6.1.0.1

    Hi,

    I am having an issue while running "*ConfigEngine.bat cluster-node-config-cluster-setup*" in WebSphere Portal 6.1.0.1.

    The below tasks are completed successfully:
    ------------------------------------------------------------------------------------
    *ConfigEngine.bat cluster-node-config-pre-federation -DDMgrUserid=uid= ,o=defaultWIMFileBasedRealm -DDMgrPassword= *

    WasUserId=
    WasPassword=
    CellName=

    *ConfigEngine.bat cluster-node-config-post-federation*
    ------------------------------------------------------------------------------------

    The below config task is failed as per the issue.

    *ConfigEngine.bat cluster-node-config-cluster-setup*

    ------------------------------------------------------------------------------------
    action-cluster-sync-node:
    [wplc-cluster-sync-single-node] Task parameters:
    [wplc-cluster-sync-single-node] Global attributes:
    [wplc-cluster-sync-single-node] cell=""
    [wplc-cluster-sync-single-node] engineinstalllocation="C:/IBM1/WebSphere/wp_profile/ConfigEngine"
    [wplc-cluster-sync-single-node] pathseparator=";"
    [wplc-cluster-sync-single-node] osarch="x86"
    [wplc-cluster-sync-single-node] node=""
    [wplc-cluster-sync-single-node] server=""

    [wplc-cluster-sync-single-node] Instance attributes (Set 1 of 1):
    [wplc-cluster-sync-single-node] syncNode="wpnode01"
    [wplc-cluster-sync-single-node] server name is dmgr
    [wplc-cluster-sync-single-node] server type is DEPLOYMENT_MANAGER
    [wplc-cluster-sync-single-node] server name is nodeagent
    [wplc-cluster-sync-single-node] server type is NODE_AGENT
    [wplc-cluster-sync-single-node] server name is server1
    [wplc-cluster-sync-single-node] server type is APPLICATION_SERVER
    [wplc-cluster-sync-single-node] server name is WebSphere_Portal
    [wplc-cluster-sync-single-node] server type is APPLICATION_SERVER
    [wplc-cluster-sync-single-node] ConfigRepository handle WebSphere:name=repository,process=dmgr,platform=co mmon,node=portalclusterCellManager01,version=5.0,t ype=ConfigRepository,mbeanIdentifier=repository,ce ll=portalclusterCell01,spec=1.0
    [wplc-cluster-sync-single-node] refreshRepositoryEpoch ...
    [wplc-cluster-sync-single-node] refreshRepositoryEpoch result : 1238796377328
    Target finished: action-cluster-sync-node
    Target finished: cluster-node-config-cluster-setup

    BUILD FAILED
    C:\IBM1\WebSphere\PortalServer\installer\wp.config \config\includes\wp_cluster_cfg.xml:405: The following error occurred while executing this line:
    C:\IBM1\WebSphere\PortalServer\installer\wp.config \config\includes\wp_cluster_cfg.xml:1399: java.lang.NullPointerException
    -------------------------------------------------------------------------------------

    Any help is greatly appreciated.

    Thanks,
    Sreenivas

  2. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    That error usually means there was a problem with the nodeagent connecting to the DMGR. Was the nodeagent running at this time?

    Could you upload the SystemOut.log files for the nodeagent and the dmgr?

    /logs/nodeagent/SystemOut.log
    /logs/dmgr/SystemOut.log

    ~HT
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM

  3. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    Have you found a solution to this problem, as i am having the exact same issue. The NodeAgent, server1 and WebSphere_Portal are all running on this node when i run the command.

  4. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    thanks for the quick reply, this is greatly appreciated - here are the relevant files.

  5. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    Please Note, that as i have standalone ldap configured i do not perform the previous step 'wp-change-portal-admin-user' as per the instructions:

    Important: If standalone LDAP security is already enabled on the Deployment Manager cell, delay running the wp-change-portal-admin-user task until after the cluster-node-config-cluster-setup task completes. After running the wp-change-portal-admin-user task, start or restart the WebSphere_Portal server to use the updated administrator user ID.

  6. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    Hi bligsc,

    Thank you for sending the logs. The only notable issue I see is that your DMGR keeps getting CPU Starvation exceptions each time this sync is executed:

    ===============================
    [6/04/09 11:46:23:416 EST] 00000031 CoordinatorCo W HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 6 seconds.
    [6/04/09 11:47:23:418 EST] 00000031 CoordinatorCo W HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 6 seconds.
    [6/04/09 11:48:23:419 EST] 00000031 CoordinatorCo W HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 6 seconds.
    [6/04/09 11:49:26:807 EST] 00000031 CoordinatorCo W HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 10 seconds.
    ===============================

    The NodeAgent has similar problems at first but then these eventually stop occurring.

    Overall, this sync node is the last thing the cluster-setup script does and because your nodeagent has autosync enabled, I can see that synchronization has completed successfully numerous times since then. That is to say, I suspect your cluster is fine as is.

    However, if you want to determine why this is failing, you may need to open a PMR for further investigation.

    ~HT
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM

  7. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    huntman25,

    Thanks for the reply to my initial question. I observed that even though I seen the task as Failed, but I can still see PortalCluster is created with the primary Portal's JVM and its working fine. I didn't have the logs which you are asking me.

    Also, I could able to add Portal Secondary Node into the cluster without any issues.

    Thanks for all the replies. I appreciate it.

    Regards,
    Sreenivas

  8. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    huntman25,

    Thanks for the reply to my initial question. I observed that even though I seen the task as Failed, but I can still see PortalCluster is created with the primary Portal's JVM and its working fine. I didn't have the logs which you are asking me.

    Also, I could able to add Portal Secondary Node into the cluster without any issues.

    Thanks for all the replies. I appreciate it.

    Regards,
    Sreenivas

  9. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    Hi Huntman, yes all appears to be running fine. I didn't even have to run the 'wp-change-portal-admin-user' as ldap creds are being utilised to log on to portal and for restarts. I think i will raise a pmr just for clarification, as this is the build for a production environment.

    One thing, whenever i restart the deployment mgr i notice that this secondary node is synchronised fine but my primary node is not, how do you determine that auto-sync is enabled and could this be the reason?

    thanks for you assistance.

  10. Re: ConfigEngine.bat cluster-node-config-cluster-setup failed inPortal 6.1.0.1

    It appears the issue i was seeing was due to copying across the wkplc.properties file from the primary node and using it on a 2ndory node. The federation still worked but ended with an error. If you use the original file and just modify the parameters as per the info centre then an error is not thrown.

+ Reply to Thread