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

[Tobias Balle-Petersen]

I am now running the debug version with extended logging.

Actually, I think the 1st time the cronjob (bbackupctl) runs after a 
restart of bbackupd, the run completes.
Following cronjobs do not. Starting bbackupctl manually does complete.

I will let my cronjob run for two days and repport back  with resulat 
and logs.

Thanks,
Tobias



Per Thomsen wrote:
> On 8/22/06 1:18 PM, tbp wrote:
>   
>> Hello....
>>
>> 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?
>>     
> Only files that are sent to the store. Here's an example of what I'm
> seeing with 'ExtendedLogging = yes':
>
> Aug 20 04:35:07 mostro bbackupd[2125]: Send
> StoreFile(0x2f16,0x41b70ed5684c0,0x57a46e0d1741a059,0xce6c,"index.html")
> Aug 20 04:35:07 mostro bbackupd[2125]: Sending stream, size uncertain
> Aug 20 04:35:07 mostro bbackupd[2125]: Receive Success(0xced0)
> Aug 20 04:35:07 mostro bbackupd[2125]: Send
> StoreFile(0x2f16,0x41b70ed5684c0,0x974c3454965ac769,0x0,"usage.png")
> Aug 20 04:35:07 mostro bbackupd[2125]: Sending stream, size uncertain
> Aug 20 04:35:07 mostro bbackupd[2125]: Receive Success(0xced1)  
>
> You are not seeing anything like that on the client machine? These logs
> are from a 0.09 installation, but I think this should log the same on
> 0.10.                 
>   
>>> 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
>>     
> OK. I guess there is no harm in using the 10 second number. I believe
> the SSL timeout is 180 seconds, so I set my KeepAliveTime to 90. Don't
> know that it would have any impact.
>
> Thanks,
> Per
>
>