Author: Bill Damage <bill.damage AT yahoo DOT com>
Date: Thu, 2 Oct 2008 11:45:46 -0700 (PDT)
I have more info. Why can't I cancel these jobs - they appear as running! It seems a new job is made each day which just does nothing except lock up the console: *list jobs +--+--+--+--+--+--+--+--+
What does '*status dir' say? Mike -- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand p
Author: Bill Damage <bill.damage AT yahoo DOT com>
Date: Thu, 2 Oct 2008 03:32:38 -0700 (PDT)
I have more info. Why can't I cancel these jobs - they appear as running! It seems a new job is made each day which just does nothing except lock up the console: *list jobs +--+--+--+--+--+--+--+--+
Author: Bill Damage <bill.damage AT yahoo DOT com>
Date: Thu, 2 Oct 2008 12:00:27 -0700 (PDT)
login as: root root@tiger's password: Last login: Thu Oct 2 12:54:58 2008 from 192.168.62.3 [root@tiger ~]# bconsole Connecting to Director tiger:9101 1000 OK: tiger-dir Version: 2.4.2 (26 July 2008)
Author: Bill Damage <bill.damage AT yahoo DOT com>
Date: Fri, 3 Oct 2008 00:37:48 -0700 (PDT)
-- Original Message -- From: Mike Eggleston <mikeegg1 AT mac DOT com> To: Bill Damage <bill.damage AT yahoo DOT com> Cc: bacula-users AT lists.sourceforge DOT net Sent: Thursday, October 2, 2008 7:50
Author: "Frederico Argolo" <fredargolo AT gmail DOT com>
Date: Mon, 6 Oct 2008 10:04:44 -0300
I think that's a bacula problem....because there are no jobs running but when you list the jobs you see JobStatus = R (running) So...when I got this, I delete the job! * delete jobid=<jobid number> F
Author: Bill Damage <bill.damage AT yahoo DOT com>
Date: Tue, 7 Oct 2008 00:52:02 -0700 (PDT)
And now the Director lives every morning! Thanks. I did 2 things different, one/both might have fixed it. First I did as you suggested and left it with no jobs in this wierd R state. Next I thought b
Author: Bill Damage <bill.damage AT yahoo DOT com>
Date: Tue, 30 Sep 2008 01:15:47 -0700 (PDT)
I'm relatively new to Bacula. I set up an incremental to fire up at 6.30am but for the past 2 days when I try to inspect it I get this: [root@tiger ~]# bconsole Connecting to Director tiger:9101 30-S
Does that job fail? Do you restart? Or start? What are you 'restarting'? bacula-dir? or something else? When you get connected via bconsole, do you see any errors via the 'mes' command? -- Dan Langil