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 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 and again only the first job run fine.
>>>>>     
>>>>>           
>>>> Have your concurrency settings been reset? Remember it needs to be 
>>>> checked
>>>> in multiple places.
>>>>
>>>>   
>>>>         
>>> Hi and thank you for your answer, actually you where right , I had ma 
>>> concurrent jobs se to 1 into director configuration file, though I had 
>>> it also in 3.0.1 and it worked like a charm .... thats why I 
>>> overlooked the problem, has something changed since 3.0.1 ? and anyway 
>>> even if I had a concurrency limit of 1 ( which I could like ) why are 
>>> jobs then not firing up once the first one has completed ?
>>>
>>> Anyway I may consider my problem for such I thank you very much
>>>
>>> Sincerely
>>>
>>>       
>> Well evidently I was wrong my problem is not solved, it just change 
>> behavior, now subsequent jobs does not sit anymore in queue saying
>>
>> "job is waiting execution" but  instead they claim to be running which in 
>> fact is not true, since backup devise is dismounted and nothing happens , 
>> pratically the system is on hang till I reboot the bacula service .... then 
>> only  the firts job in line again does run others hangs the system and so on 
>> ...
>>
>> Any clue ?? 
>>
>>
>>     
> Since yesterday, I've upgraded our working 2.4.4 version to a 3.0.3 build.
>
> I'm facing the same trouble. first job run smoothly, other are marked as 
> running
> but a status client / storage show that nothing is running on other daemons.
>
> How did you fix your case ?
>
>   
Hi,

    well in my case I purged all my store deleted and recreated em  , 
disinstalled bacula ( saving all the config files ) then re-compiled it 
and reinstalled directly the 3.0.3 , wich of course can't be actually 
define a "solution" AND I could do this since I m still in testing phase 
I dunno if you can purge all your backup stores ...






------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users