Ever since the upgrade to background process a couple of days ago Ultimate Cron has not been running on most items:

Could not call service uc-queue_views_bulk_operations for callback UltimateCronBackgroundProcessLegacyLauncher::job_callback: stdClass Object
(
    [url] => https://telsoc.org/bgp-start/uc-queue_views_bulk_operations/48597018050a02f5e8e1aaa52f2fb1f2
    [options] => Array
        (
            [method] => POST
            [headers] => Array
                (
                    [User-Agent] => Drupal (+http://drupal.org/)
                    [Accept] => */*
                    [Host] => telsoc.org
                    [Connection] => close
                )

            [data] => 
            [max_redirects] => 3
            [timeout] => 2
            [context] => Resource id #553
            [blocking] => 
            [postpone] => 
        )

    [code] => 0
    [uri] => Array
        (
            [scheme] => https
            [host] => telsoc.org
            [path] => /bgp-start/uc-queue_views_bulk_operations/48597018050a02f5e8e1aaa52f2fb1f2
        )

    [socket] => ssl://telsoc.org:443
    [postponed] => 
    [start] => 1491899169.58
    [data_ready] => 1
    [response] => 
    [error] => Error opening socket ssl://telsoc.org:443
    [end] => 1491899169.59
)

Could not execute background process dispatch for handle uc-queue_views_bulk_operations

In the Configuration settings clicking on the "Determine default service host" button produced the following error message:

Could not determine default service host. Please configure background process in your settings.php

Comments

GrahamShepherd created an issue.

GrahamShepherd’s picture

As an expedient to get around this problem, I have set the Ultimate Cron launcher to Serial, the lockout period to 60 seconds and the number of threads to 5.

However, it would be good to get a fix.

mmeytin’s picture

Have you been able to figure out a fix or workaround for this issue? I'm running into the same problem after a recent round of updates to several modules in my Drupal install.

GrahamShepherd’s picture

No, I'm sorry. I abandoned Background Process for all my projects. I still use Ultimate Cron but with the launcher set to Serial.

zread’s picture

This appears to be related to https://www.drupal.org/node/2868954

/u/noah's solution to turn off "SSL verification" (in Configuration > Background process) solves the "Could not determine default service host" error for me. An alternative would be to downgrade to 1.16 which didn't have this problem.