After upgrading to Background Process dev my backups (backup and migrate module) have failed. The error message:

The site backup has failed with the following messages:
Could not run backup because the file could not be saved to the destination

If i revert to latest stable version (1.6) the error is gone.

Comments

gielfeldt’s picture

gielfeldt CreditAttribution: gielfeldt commented

I'm gonna need just a weee bit more info than that. What versions of the modules. Is there any custom code involved? Are you using Background Batch?

fox_01’s picture

fox_01 CreditAttribution: fox_01 commented

Versions:

  • backup and migrate module 7.x-3.0
  • Background Process 7.x-1.16+3-dev
  • ultimate cron 7.x-2.0-beta6

I have just configured the standard GUI controlled scheduled backup with a local folder as the destination.

I have also tried manual backups that work. Its just a problem with the scheduled ones.

I'm not using Background Batch

gielfeldt’s picture

gielfeldt CreditAttribution: gielfeldt commented

I have a hunch which commit could be causing this problem. Could you try to apply this patch?

diff --git a/background_process.module b/background_process.module
index b496daf..f35865d 100755
--- a/background_process.module
+++ b/background_process.module
@@ -989,7 +989,7 @@ function background_process_build_request($url, $service_hostname = NULL, $optio
 
   $url = url($url, $options);
   $parsed = parse_url($url);
-  $host = !empty($service_host['http_host']) ? $service_host['http_host'] : (isset($parsed['host']) ? (isset($parsed['port'])? ($parsed['host'].':'.$parsed['port']) : $parsed['host']) : NULL);
+  $host = !empty($service_host['http_host']) ? $service_host['http_host'] : (isset($parsed['host']) ? $parsed['host'] : NULL);
   $headers = _background_process_request_headers();
   $headers = _background_process_filter_headers($headers);
   $headers['User-Agent'] = variable_get('background_process_user_agent', 'Drupal (+http://drupal.org/)');
gielfeldt’s picture

gielfeldt CreditAttribution: gielfeldt commented
Status: Active » Postponed (maintainer needs more info)
fox_01’s picture

fox_01 CreditAttribution: fox_01 commented

Error is a bit different but still there with or without the patch
Could not run backup because a there was no valid destination to save to.

gielfeldt’s picture

gielfeldt CreditAttribution: gielfeldt commented

Hi

I've tried setting up the backup and migrate module, and I cannot recreate the error :-(. I also can't understand/imagine how background process would be able to cause this error.

Do you get any messages in watchdog besides the error you already mentioned?