Troubleshooting startup problems

Troubleshoot startup problems by examining log files for the processes that are not starting up. Use process dependencies to help identify the origin of the startup problem.

The default name of the log file is the process name followed by the domain name and then the .log or .trace file extension. Complete these steps to locate a log file for a process.

  1. Run the itnm_status command to determine which process or processes are failing to start.
    The itnm_status output might show, for example, that the ncp_disco process is failing to start.
  2. Determine the process dependencies for the failing processes.
    Process dependencies are listed in the link below.
    For example, if the ncp_disco process is failing then the following dependencies apply:
    • The ncp_disco process depends on the Helper Server, ncp_d_helpserv, and the Topology Manager, ncp_model.
    • The ncp_d_helpserv process has no dependencies.
    • The ncp_model process depends on the Active Object Class manager, ncp_class.
  3. Navigate to the default location for process log and trace files, NCHOME/log/precision.
  4. Locate the log and trace files that correspond to the process name.
    For example, an instance of the ncp_disco process running on the NCOMS domain generates the following files.
    • ncp_disco.NCOMS.log
    • ncp_disco.NCOMS.trace
  5. View the content of the log files for the failing process and for the process dependencies. Examine these files in reverse order of startup.
    For example, if the ncp_disco process is failing, then examine the log files in the following order
    • ncp_disco.DOMAIN.log
    • ncp_d_helpserv.DOMAIN.log
    • ncp_class.DOMAIN.log

For more information about troubleshooting the Dashboard Application Services Hub, see the Jazz for Service Management documentation.