CallsMonitoring job failing

1

On my test systems if CallsMonitoring won’t run I can usually get it working again by running it over and over or by running it via a curl command.
But on my current test system it’s stuck and won’t complete. :frowning:

Error :

Dec 19 15:55:01 vlab-ytui-mgt-syd-testenv YETI-admin[7827]: [15:55:01.453180 ] [ WARN]: Couldn't find BaseJob with [WHERE "sys"."jobs"."running" = $1 AND ("sys"."jobs"."id" = 0 OR "sys"."jobs"."type" = 'CallsMonitoring')]
Dec 19 15:55:01 vlab-ytui-mgt-syd-testenv YETI-admin[7827]: [15:55:01.453412 ] [ WARN]: /opt/yeti-web/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.4.3/lib/active_record/relation/finder_methods.rb:343:in `raise_record_not_found_exception!'
2

It is not clear how to reproduce this issue, also there is no possibility to run CallsMonitoring using curl in modern versions, so it looks like you are running some 5 years old version(ruby 2.6, activerecord-5.2.).

According to your log you have no job with type “CallsMonitoring” in your database, or it has flag running=true

1 Like
3

Yes, this is an old version in my migration testing Lab - we’re running Yeti 10 and getting ready to upgrade to Yeti 13.

I have noted the Cron jobs in Yeti 13 are different from 10 and more reliable.

Just noted in the Yeti 10 Lab server that it’s working now. I remembered I’ve seen that before, that it sorts itself out after a time.

TLDR: Don’t worry about it, especially as we’re moving to Yeti 13 soon.