Richard van den Berg

503 Error with message 'No record found for selection of trigger' in 11.4.1.0

Discussion created by Richard van den Berg on Apr 15, 2020
Latest reply on Apr 16, 2020 by Richard van den Berg

I just had an interesting upgrade experience. On our test environment I did an upgrade from NetWitness 11.4.0.1 to 11.4.1.0 and got stuck with the UI not coming up. After some investigation the culprit showed in /var/lib/netwitness/uax/logs/sa.log :

2020-04-15 12:47:18,355 [main] WARN  org.springframework.web.context.support.XmlWebApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0'; nested exception is org.springframework.scheduling.SchedulingException: Could not start Quartz Scheduler; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn't retrieve trigger: No record found for selection of Trigger with key: 'DEFAULT.8c0550a9-a782-40f4-a66d-32c69e7080b5' and statement: SELECT * FROM QRTZ_SIMPLE_TRIGGERS WHERE SCHED_NAME = 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' AND TRIGGER_NAME = ? AND TRIGGER_GROUP = ? [See nested exception: java.lang.IllegalStateException: No record found for selection of Trigger with key: 'DEFAULT.8c0550a9-a782-40f4-a66d-32c69e7080b5' and statement: SELECT * FROM QRTZ_SIMPLE_TRIGGERS WHERE SCHED_NAME = 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' AND TRIGGER_NAME = ? AND TRIGGER_GROUP = ?]]

Searching on the RSA Community site let to 000017462 - 503 Error with message 'No record found for selection of trigger' in RSA Security Analytics  which looked promising but is very outdated. It seems a newer version of H2 is being used that now stores data in platform.mv.db (instead of the old platform.h2.db).

 

I was able this fix this by replacing the first steps of DOC-47175 with:

  1. systemctl stop jetty
  2. cd /var/lib/netwitness/uax/db
  3. cp platform.mv.db platform.mv.db.backup
  4. wget https://repo1.maven.org/maven2/com/h2database/h2/1.4.199/h2-1.4.199.jar
  5. java -cp h2-1.4.199.jar org.h2.tools.Shell -url jdbc:h2:file:./platform

 

The SQL part of DOC-47175 is still the same:

  1. sql> DELETE FROM QRTZ_TRIGGERS WHERE JOB_NAME = '<triggerName>';
  2. sql> DELETE FROM QRTZ_JOB_DETAILS WHERE JOB_NAME = '<triggerName>';
  3. sql > quit

 

After a "systemctl start jetty" all is fine again.

Outcomes