13.6 Issue: Status of Data Collection is Suspended

You may see that the data collection status is Suspended on the Identity Vaults screen.

In this case, you should look at the following list of possible causes:

  • The Managed System Gateway driver is not running.

  • The Managed System Gateway driver has incorrect connection information.

  • Errors have occurred in collection services for the Data Collection Service driver.

Here are some troubleshooting tips:

  • Look at the database to see if it provides any clues about what might be causing the suspension:

    • The data collection status and failure reasons are stored in the idm_rpt_data.idmrp_ms_collect_state table.

    • The Managed System Gateway driver registration is stored in the idm_rpt_data.idmrpt_ms_collector table.

    • The Data Collection Service driver registration is stored in the idm_rpt_data.idmrpt_rpt_driver table:

      select ms_collect_id, ms_query_api, ms_collect_time, ms_collect_error from idm_rpt_data.idmrpt_ms_collect_state where
idm_rpt_data.idmrpt_ms_collect_state.ms_collect_state = FALSE;

  • If you see a failure to connect error:

    • Verify that the Managed System Gateway driver is running. In iManager, check that the driver is present and the current status is running. If not, start the driver and activate data collection on the Identity Vaults screen.

    • Verify that the Managed System Gateway driver is accessible from the machine that the Reporting Module is running on. If the Reporting Module and Identity Manager are not running on the same box, verify that the Managed System Gateway driver configuration references the real IP address, rather than 127.0.0.1 (the default setting).

      Also, check the Managed System Gateway parameter section.

      Check that the proper configuration information is reflected in the idm_rpt_data.idmrpt_ms_collector table. 

      select * from idm_rpt_data.idmrpt_ms_collector;

    • If you see an HTTP status other than 200, verify that you can execute a query from a different tool such as Poster or RESTClient.

  • If you see other kinds of errors, enable logging and reactive data collection.

    • Enable Managed System Gateway driver trace logging at level 5. Delete the old trace file (if one exists) and restart the Data Collection Service driver.

    • Enabled pulled Data Collection Service driver trace logging.

      Add the following trace to the idmrptcore_logging.xml file and tail the console log (by using tail -f server.log). You should see trace messages with recognizable DNs, names, and so forth. 

      <logger name="com.novell.idm.rpt.core.server.service.DataCollectMgrService" level="TRACE" additivity="true"/>
<logger name="com.novell.idm.rpt.core.server.dc" level="TRACE" additivity="true"/>