Did anyone ever work out how to solve this?
I've a fresh install of bacula on a fresh virtual machine (had it working
fine in a previous version too - so I know what I'm doing).
3.0.3 has jobs as waiting execution after the first job has ran. I've spent
2 days trying to solve this, does anyone h
Bruno Friedmann wrote:
> On 11/17/2009 03:31 PM, Giuseppe De Nicolo' wrote:
>
>> Giuseppe De Nicolo' wrote:
>>
>>> Alan Brown wrote:
>>>
On Tue, 17 Nov 2009, Giuseppe De Nicolo' wrote:
> Hi All,
>
> Since the upgrade to 3.0.3 our test se
On 11/17/2009 03:31 PM, Giuseppe De Nicolo' wrote:
> Giuseppe De Nicolo' wrote:
>> Alan Brown wrote:
>>> On Tue, 17 Nov 2009, Giuseppe De Nicolo' wrote:
>>>
>>>
Hi All,
Since the upgrade to 3.0.3 our test server have this strange
behavior , the first job after bacula start
Giuseppe De Nicolo' wrote:
> Giuseppe De Nicolo' wrote:
>
>> Alan Brown wrote:
>>
>>> On Tue, 17 Nov 2009, Giuseppe De Nicolo' wrote:
>>>
>>>
>>>
Hi All,
Since the upgrade to 3.0.3 our test server have this strange
behavior , the first job after bacula start
Giuseppe De Nicolo' wrote:
> Alan Brown wrote:
>> On Tue, 17 Nov 2009, Giuseppe De Nicolo' wrote:
>>
>>
>>> Hi All,
>>>
>>> Since the upgrade to 3.0.3 our test server have this strange
>>> behavior , the first job after bacula start up runs fine all others get
>>> in line as "job is waiting e
On Tue, 17 Nov 2009, Giuseppe De Nicolo' wrote:
> Hi All,
>
> Since the upgrade to 3.0.3 our test server have this strange
> behavior , the first job after bacula start up runs fine all others get
> in line as "job is waiting execution" and nothing happens, restarting
> bacula reset job lists
