On Jan 8, 2008, at 4:24 PM, Dan Langille wrote:
> Ken Monville wrote:
>> On Jan 8, 2008, at 2:36 PM, Dan Langille wrote:
>>>
>>> On Jan 8, 2008, at 2:30 PM, Ken Monville wrote:
On Jan 8, 2008, at 2:12 PM, Dan Langille wrote:
> Ken Monville wrote:
>> Hi all,
>> I had a longti
Ken Monville wrote:
>
> On Jan 8, 2008, at 2:36 PM, Dan Langille wrote:
>
>>
>> On Jan 8, 2008, at 2:30 PM, Ken Monville wrote:
>>> On Jan 8, 2008, at 2:12 PM, Dan Langille wrote:
>>>
Ken Monville wrote:
> Hi all,
> I had a longtime running bacula 1.38.11 environment running on
>
On Jan 8, 2008, at 2:36 PM, Dan Langille wrote:
>
> On Jan 8, 2008, at 2:30 PM, Ken Monville wrote:
>> On Jan 8, 2008, at 2:12 PM, Dan Langille wrote:
>>
>>> Ken Monville wrote:
Hi all,
I had a longtime running bacula 1.38.11 environment running on
FreeBSD hosts that worked flawle
On Jan 8, 2008, at 2:30 PM, Ken Monville wrote:
> On Jan 8, 2008, at 2:12 PM, Dan Langille wrote:
>
>> Ken Monville wrote:
>>> Hi all,
>>> I had a longtime running bacula 1.38.11 environment running on
>>> FreeBSD hosts that worked flawlessly. Recently I had a drive
>>> failure on one of the cl
Hi Dan,
Double checking my configuration, there is no "Spool Attributes"
parameter set anywhere, so I assume its off. The database server has
virtually no load and I don't notice anything when the job is hung.
Also, it stays in this state indefinitely until I restart the fd as I
mentione
Ken Monville wrote:
> Hi all,
>
> I had a longtime running bacula 1.38.11 environment running on FreeBSD
> hosts that worked flawlessly. Recently I had a drive failure on one
> of the clients, rebuilt it from scratch and have been unable to get a
> successful backup since.
>
> Ironically,
Hi all,
I had a longtime running bacula 1.38.11 environment running on FreeBSD
hosts that worked flawlessly. Recently I had a drive failure on one
of the clients, rebuilt it from scratch and have been unable to get a
successful backup since.
Ironically, I started having issues with the ser
