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 ?? ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
