ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

adm-connector errors with "No known job with id"

book

Article ID: 169355

calendar_today

Updated On:

Products

Security Analytics

Issue/Introduction

The /var/log/messages file reports:

Feb 17 08:20:44 sensor1 /usr/sbin/adm-connector[8405]: Couldn't fetch results URL localhost:8080/engine/v1/alerts_longpoll/20170123182409-00002?probability=80&timeout=60 (http ret=404) response:{ "message" : "No known job with id '20170123182409-00002'", "errorCode" : 20101} 

OR

Feb  2 10:40:32 sensor1 /usr/sbin/adm-connector[8424]: Couldn't fetch results URL localhost:8080/engine/v1/alerts_longpoll/20170123182409-00002?probability=80&timeout=60 (http ret=400) response:{  "message" : "Cannot alert on job '20170123182409-00002' because the job is not running",  "errorCode" : 60103} .

Cause

This was seen after repeated reboots.  The process may be losing track of old jobs, which have been removed but remain in the queue.

Resolution

The jobs need to be removed and the service restarted.

For the message above, delete the job using these commands:

service adm-connector restart
curl -X DELETE 'http://localhost:8080/engine/v1/jobs/20170123182409-00002'  (use the job number from your own log file)
service adm-connector restart

Powered by Wolken Software