Repairing a corrupted discovery

If the discovery stops in an unusual way, for example, if the ncp_disco process is stopped forcibly from the command line, or exits unexpectedly, you might need to repair the discovery before running another discovery.

About this task

If the discovery is shut down normally, all the dependent processes such as discovery agents are also shut down, and the discovery database is ready for another discovery. However, if the ncp_disco process is stopped forcibly or unexpectedly, then dependent processes can be left running, and the discovery cache files are left in a state such that they can interfere with the next discovery. In this case the discovery can be said to be corrupted.

To repair a corrupted discovery, complete the following steps:

Procedure

  1. Remove the entry for the ncp_disco process from the services.inTray database in ncp_ctrl, if it is present. Removing the entry prevents the ncp_ctrl process from restarting ncp_disco.
  2. Stop the ncp_disco process, if it is still running, using an appropriate command for your operating system.
    For example, on Unix, run the kill -9 command on the process ID for ncp_disco.
  3. Remove the cache files for the dNCIM database. Navigate to the $PRECISION_HOME/embeddedDb/sqlite directory and delete the ncp_disco.domain directory.
  4. Optional: Archive or remove existing log files to start the next discovery with fresh log files. The log files for the following processes are relevant:
    • ncp_disco
    • ncp_df_*
    • ncp_agent*
    • ncp_disco_perl_agent*
  5. Search for any discovery finders or agents that are still running in the corrupted domain. The discover finders have process names that start with ncp_df. The discovery agents start with ncp_agent, and any Perl discovery agents start with ncp_disco_perl_agent. Stop any agents or finders that are still running in the corrupted domain.
  6. If you want to run the ncp_disco process as a process managed by the ncp_ctrl process, which is the default, then start ncp_disco as a managed process. See the topic on starting managed processes for more information.
    Starting ncp_disco as a managed process starts a new discovery.
  7. Start or monitor your discovery using the Discovery Configuration GUI.