IBM Support

CP4S: The idrmrisk Job is Suspended and Threat Event Data is Not Importing

Troubleshooting


Problem

IBM Cloud Pak for Security (CP4S) Risk Manager application complains about not being able to import data with error message:
"The idrmrisk job is suspended. Threat event data is not imported. Asset data is not imported. Contact your system administrator."

Symptom

After trying to import threat event data, produces error and does not complete the import:

image-20220608160544-1
Risk Manager application does not import asset data in CP4S.

Diagnosing The Problem

The projects cronjob displays warnings for "too many missed start time":

oc get events --sort-by='.metadata.creationTimestamp'

LAST SEEN   TYPE      REASON                   OBJECT                                                                MESSAGE
51s         Warning   FailedNeedsStart         cronjob/car-post-process-cronjob                                      Cannot determine if job needs to be started: too many missed start time (> 100). Set or decrease .spec.startingDeadlineSeconds or check clock skew
50s         Warning   FailedNeedsStart         cronjob/idrmrisk                                                      Cannot determine if job needs to be started: too many missed start time (> 100). Set or decrease .spec.startingDeadlineSeconds or check

Resolving The Problem

  1. List cronjobs: 
    oc get cronjobs

NAME                             SCHEDULE       SUSPEND   ACTIVE   LAST SCHEDULE   AGE
app-manager                      0 */12 * * *   False     0        <none>          4h35m
car-post-process-cronjob         */2 * * * *    False     0        17s             5h43m
entitlements-licensing-cronjob   0 * * * *      False     0        16m             85d
idrmrisk                         */10 * * * *   False     0        6m17s           5h42m
isc-cases-event-adapter          * */12 * * *   False     1        9h              85d
serviceability-loader            0 0 * * SUN    False     0        <none>          85d
udi-changelog-cronjob            0 1 * * *      False     0        21h             85d
udi-encrypt-cronjob              0 2 * * *      False     0        20h             85d
     
  2. Focus on cronjob car-post-process-cronjob 
    oc edit cronjob car-post-process-cronjob
  3. Replace the following value at the end of the file from 0 to 1000.  
      schedule: '*/2 * * * *'
  successfulJobsHistoryLimit:  0                                    
  suspend: false
status:
  lastScheduleTime: "2022-06-08T22:22:00Z"
    NOTE: The lastSceduleTime is set to a value by the system and we are not changing it. If your value for lastSceduleTime is different, leave your unique value in place.
  4. Ensure to write and save the file, after making the change: 
      schedule: '*/2 * * * *'
  successfulJobsHistoryLimit:  1000                                    
  suspend: false
status:
  lastScheduleTime: "2022-06-08T22:22:00Z"
  5. Once the file saves, the cronjob reloads automatically and the error will be cleared from the screen and assets data is imported again. 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTDPP","label":"IBM Cloud Pak for Security"},"ARM Category":[{"code":"a8m3p0000000rboAAA","label":"Risk Manager"}],"ARM Case Number":"TS009580803","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
09 June 2022

UID

ibm16593729

Page Feedback