Cron without URL throws warning

This happens because Drupal's cron process expects to be run with a full HTTP request string. When one is not available, as in the direct cron code you are using, domain lookups fail.

See https://drupal.org/cron

One solution, if you have drush on the server, is to call cron via drush instead:

drush cc -l http://example.com

This warning is harmless in your case -- it means that all cron requests will run under your default domain. There is no simple way to disable it.

Better title.

Hi Folks-
We recently enabled elysia_cron on a project, and our watchdog is slammed with the same error message including Location: http:///. I think the two are correlated (in our case) and wanted to share this tidbit fwiw.
-Bronius

The instructions for setting up Drupal cron clearly state that you should pass a url value for this very reason.

https://drupal.org/node/23714

You can also disable this message in settings.php if you can't fix your cron script.

Add this to settings.php (at the bottom):

      // Show a warning to admin users, if enabled.
      // You may disable this warning by adding:
      // to the bottom of settings.php.
      $conf['domain_hide_errors'] = TRUE;
      

@agentrickard- Would it be possible/appropriate in the testing for and falling back to default domain bit of domain init to also check against empty domain? You still want to throw error for bad bootstrap and for "legitimately unrecognized domains", but if the issue occurs widely enough that cron is called "from" http:/// for my or others' use cases, then handling it would squash all errors: It could still be helpful to provide documentation that says, "Oh by the way, call each specific domain's cron, if that's important to your application" but even that is probably an edge case.

Are there other reasons the failure at phase bootstrap might falsely report that settings.php was not configured, and is there a better or more specific test to run? Perhaps just the presence and absence of some constant defined only in DA's settings.inc would be a more direct "hey you didn't follow INSTALL.txt, you goof" checker.

-Bronius

Given that cron in Drupal requires a URL, I don't see the point. This is a configuration error.

And it certainly isn't getting any attention in 6.x

For what it's worth, my empty requester is Location: https:/// (secure https, not http as reported earlier), but the site is not a secure site. Maybe I've got something else calling and coinciding?..

Also @agentrickard would it make sense instead of using empty($hide) to check on the value of $hide in the event someone wants to keep the definition in settings.php but just toggle it while troubleshooting:

      $hide = variable_get('domain_hide_errors', FALSE);
      if (user_access('administer domains') && !$hide) {
        drupal_set_message($error, 'error');
      }
      if (!$hide) {
        watchdog('domain', $error, NULL, WATCHDOG_ERROR);
      }

Well dang it-- checking apache logs, looks like nagios is our (us- our, not you folks and me- our) culprit:

some.source.ip - - [16/Aug/2012:16:50:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:16:53:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:16:56:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:16:59:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:17:02:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:17:05:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:17:08:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:17:11:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
some.source.ip - - [16/Aug/2012:17:14:48 -0400] "GET / HTTP/1.0" 403 5152 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"

My two earlier questions are still valid: Can Domain Access only check for valid domains and, for confirming proper settings.php, include a constant in its settings.inc to look for?

No. These reports are designed to help you troubleshoot. You have ways to turn them off, as noted above.

They are largely for novice users, not advanced users, and their inclusion has made support much, much easier.