Security Connect 2021 is coming Jun 3. Register for free today!

Cb Response: Job-runner no longer running after upgrade to 6.2.2

Cb Response: Job-runner no longer running after upgrade to 6.2.2


  • Cb Response 6.2.2+


  • /var/log/cb/job-runner/startup.out lists the following message

    /usr/bin/python: No module named cb.maintenance

  • /var/log/cb/job-runner/job-runner.log is empty

  • /etc/cb/cron/ contains a cb.cron.template.rpmnew file
  • No new watchlist or feeds alerts have been generated
  • Postgres table sizes are growing


The upgrade to Python packages in the 6.2.2 server version resulted in a path change for many of our cron jobs. If the new values listed in cb.cron.template.rpmnew are not copied to cb.cron.template, crond will continue to use the wrong path when executing the jobs.

The old path was /usr/bin/python, the new path is /usr/share/cb/virtualenv/bin/python.


The files used by cron will need to be updated in order for job-runner to execute successfully.

    1. Resolve differences between cb.cron.template and cb.cron.template.rpmnew in /etc/cb/cron. If you have not customized this template before, you can make a backup of the current template and rename cb.cron.template.rpmnew to cb.cron.template

    2. Restart services Cb Response: How to restart services

    3. Restart crond

      The crond restart method will depend on your operating system, please find the right method for your flavor of Linux

You can verify jobs are running by tailing job-runner.log or /var/log/cron

    1. job-runner.log
      tail -f /var/log/cb/job-runner/job-runner.log
    2. cron
      tail -f /var/log/cron

Additional Notes

If job-runner is still empty, there may be permission issues with the cron files. Below are the necessary permissions.


-rw-r--r--. 1 root cb cb.cron.template


-rw-r--r--. 1 root root /etc/cron.d/cb

Labels (1)
Tags (1)
Was this article helpful? Yes No
No ratings
Article Information
Creation Date: