So, I've been trying to work out why my cron is getting stuck since last night.

Using cron control module I've turned off cron jobs for all module and then on again one at a time.

The problem module is Backup Migrate (Files).

I can do manual db backups BUT manual files backups fail and I'm assuming this is the problem.
I recently upgraded to Backup Migrate 6.x-2.2. (after getting caught by the 2.1 mix up)

Backup Migrate Files used to work just fine on my system can anyone give me any ideas what's wrong?

I'm not sure if the problem is with Backup Migrate Files or with Backup Migrate itself, since it is the latter that has recently changed, so I'm going to cross post this in the Backup Migrate issue cue also.

Thanks!

Comments

austintnacious’s picture

austintnacious CreditAttribution: austintnacious commented
Title: Since upgrading Backup Migrate to 6.x-2.2 Backup Migrate Files has stopped working and jams up my cron job » Since upgrading Backup Migrate to 6.x-2.x-dev Backup Migrate Files has stopped working and jams up my cron job

Sorry, I actually had 6.x-2.x-dev installed.

I changed to Backup Migrate 6.x-2.2 and cron seems to be working again OK!

My files backup is still NOT working!

ahabman’s picture

ahabman CreditAttribution: ahabman commented

Same here. 2.2 and 2.x both spin forever, even though I've maxed out: memory_limit and execution_time. I even removed all directories from from the backup by adding them to the exclude list - still spins forever.

sillygwailo’s picture

sillygwailo
Location Toronto, ON
CreditAttribution: sillygwailo commented

Cross-reference to the issue on the Backup and Migrate project: http://drupal.org/node/665532

roderik’s picture

roderik
Primary language Dutch
Location Amsterdam,NL / Budapest,HU
CreditAttribution: roderik commented

@ahabman: maybe your 'spins forever' error is related to this? #866566: Eternal loop if directory doesn't exist

ronan’s picture

ronan CreditAttribution: ronan commented
Status: Active » Postponed (maintainer needs more info)

Can you confirm if this was related to the issue mentioned above?

dashaver’s picture

dashaver CreditAttribution: dashaver commented

You may have to use Backup and Restore in Maintenance Mode
When I changed from the event to date modules I used the same events since I had thousands. This worked great I added the field for the new date format to event type. The problem this caused is Google began constantly querying the site for event files which now had a different name. The log entry looked like this page not found03/10/2011 - 7:32amevent/2015/08/03/week/all/all/1 and there were about 20 per minute. This made the scheduled back up of the Backup and Migrate module fail which in turn caused the cron to fail. I was baffled by all of this and finally got poormanscron to run by using Semiclean module. The cache was not being cleared because I had minimum lifetime cache set and did not know this would keep the cache from being cleared. After getting cron to run again I began trying to see why Backup and Migrate would not run. Backup and Migrate is an absolute necessity in my case since my data base is too large for PHPMyadmin unless I divide it in to segments. I found Backup and Migrate before I figured out how to do it that way. It was just a wild hunch that the constant querying by Google was keeping the Backup and Migrate from working that made me try to run a manual Backup in maintenance mode and it worked fine.

I think the important points here are:
Backup and Restore may not run if your log is too busy
Your cache will not be cleared if minimum lifetime cache is set
http://drupal.org/node/227228