IBM Support

MustGather: Synchronization problems in WebSphere Application Server

Troubleshooting


Problem

Collecting data for synchronization problems with the IBM WebSphere Application Server. Gathering this MustGather information before contacting IBM support helps familiarize you with the troubleshooting process and save you time.

Resolving The Problem

Tab navigation


If you already contacted IBM Support, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.


Synchronization-specific MustGather information
This document explains the information needed to better understand why specific files are not properly transferred and synchronized or why the administrative console or wsadmin display a node as being not Synchronized.
 
Perform the following steps to test and collect information for understanding synchronization problems:
  1. Stop all WebSphere processes (Deployment Manager [dmgr], Node Agent and Servers) and clear the logs from under the following locations for the dmgr and node profiles.
    If you would like to retain the logs, you can back them up before deleting them.
    profile_root/logs

     
  2. Set the following trace on both the dmgr and node agent.
    com.ibm.ws.management.sync.*=all


    For more information on how to set the trace by using the administrative console see the following link: 
    Setting up a trace in WebSphere Application Server
    https://www.ibm.com/support/pages/setting-trace-websphere-application-server
     
  3. Start the dmgr and make sure it is up and running by checking for the following line in the SystemOut.log file.
    WSVR0001I: Server dmgr open for e-business

     
  4. Execute the syncNode script with the -trace parameter from the node profile_root/bin location:
    profile_root/bin/syncNode.bat(sh) <dmgr host> <dmgr port> -trace

    Note:  If security is enabled include -username and -password parameters in the syncNode command.

    Reference:
    syncNode command - IBM Documentation
    https://www.ibm.com/docs/en/was-nd/9.0.5?topic=tools-syncnode-command
     
    Note:  If the syncNode script works but Startup Synchronization or Automatic Synchronization fails, the data will provide details about the problem. 
                However, once this initial set of data is analyzed, we may need to request additional tracing in order to further isolate the problem.

     
  5. Run the collector tool on both Deployment Manager and  Node profiles.
    Reference:
    IBM Support TV - YouTube Video - How to run the collector tool

     
  6. Follow instructions to send diagnostic information to IBM support.
What to do Next?
Once you collect the preceding information, you can begin Analyzing the data, or simply submit the diagnostic information to IBM support.

For a listing of all documents, downloads, and educational materials specific to synchronization, search the WebSphere Application Server support site.

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000CdW9AAK","label":"WebSphere Application Server traditional-All Platforms-\u003ESystem Management-\u003ETraditional WAS-\u003ESynchronization"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;9.0.5"},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
25 October 2022

UID

swg21140941