[Box Backup] bbackupctl always fails when run from crontab. Manual always OK?

[tbp]

Hello....

Per Thomsen wrote:
> On 8/22/06 11:37 AM, tbp wrote:
>   
>> Hello...
>>
>> The cronjob seems to fail within the 1st hour. A successful run is
>> about 6 hours.
>>     
> Why does the backup take 6 hours? A lot of data, or a slow connection?
>   
There is a lot of data.

>> I don't think I have done a manual run at the exact same time as the
>> cronjob.
>>     
> As I said, I'm just trying to cover all the bases. I don't know if the
> problem is related to the timing of the runs.
>   
I am now running cron at 10 in the morning. It fails, but when I do 
manual runs during the day they
always complete.
>> The user is the same ion the manual and crontab runs (root)
>>     
> OK.
>   
>> Should the debug build tell me what file is being backed up? I have
>> never noticed.
>> I will run again with the debug build and report back.
>>     
> Actually, AFAICT, turning on ExtendedLogging gives you the filenames in
> the logs on the client.
>   
I don't remember ever having seen the filenames of files being backed up 
even with extended logging on.
Would all files be listed as the are evaluated, or just the new files 
that are to be added to the store?
> No need to run debug builds, near as I can tell.
>
> If the same file (or type/size/location) is the culprit every time,
> you'll have to figure out what's different about this file.
>
> Finally, I just want to make sure you're using the 'KeepAliveTime"
> parameter in the bbackupd.conf file. You're receiving a timeout error,
> so I just want to eliminate the lack of that parameter as the reason.
>   

KeepAliveTime is 10
> Thanks,
> Per
>   
>> Tobias
>>
>> Per Thomsen wrote:
>>     
>>> On 8/22/06 8:38 AM, tbp wrote:
>>>  
>>>       
>>>> I have been running the cronjob at different times a day. I used to
>>>> run the cronjob at night. I then had successfull manual runs during
>>>> the day. I decided to move the cronjob to the same time as the
>>>> sucessfull manual runs.
>>>>     
>>>>         
>>> This is a bit odd...
>>>
>>> Just trying to cover all the bases.. Couple of questions:
>>>
>>>     * Does this happen when backing up a specific file? Or a specific
>>>       time during the run (e.g.: always 20 minutes into the run)?
>>>     * What happens when you run manually at the time that the cron job
>>>       was failing?
>>>     * Is the user the same on the cron job, as on the manual run?
>>>     * Is the cron problem related to a particular file? (Debug build
>>>       should tell you the file being backed up)
>>>
>>> Thanks,
>>> Per
>>>
>>>   
>>>       
>> _______________________________________________
>> boxbackup mailing list
>> boxbackup@fluffy.co.uk
>> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
>>     
>
>
>