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
+-------+--------------------+---------------------+------+-------+----------+----------------+-----------+
| JobId | Name | StartTime | Type | Level | JobFiles | JobBytes | JobStatus |
+-------+--------------------+---------------------+------+-------+----------+----------------+-----------+
| 1 | Tiger USB Critical | 2008-09-20 10:43:04 | B | F | 0 |
0 | f |
| 2 | BackupCatalog | 2008-09-20 23:10:02 | B | F | 0 | 0 | A |
| 3 | Tiger USB Critical | 2008-09-21 09:41:54 | B | F | 0 | 0 | f |
| 4 | Tiger USB Critical | 2008-09-22 06:30:03 | B | F | 85 | 17,016,560,760 | T |
| 5 | Tiger USB Critical | 2008-09-23 11:44:11 | B | F | 85 | 17,016,560,760 | T |
| 6 | Tiger USB Critical | 2008-09-25 10:36:37 | B | I | 3 | 570,292,154 | T |
| 7 | Tiger USB Critical | 2008-09-25 10:46:46 | B | I | 3 | 570,292,154 | T |
| 8 | Tiger USB Critical | 2008-09-26 06:30:02 | B | I | 0 | 0 | R |
| 9 | Tiger USB Critical | 2008-09-27 06:30:02 | B | I | 0 | 0 | R |
| 10 | Tiger USB Critical | 2008-09-28 06:30:03 | B | I | 0 | 0 | T |
| 11 | Tiger USB Critical | 2008-09-29 06:30:02 | B | I | 0 | 0 | R |
| 12 | Tiger USB Critical | 2008-09-30 06:30:02 | B | I | 0 | 0 | R |
| 13 | Tiger USB Critical | 2008-10-01 06:30:03 | B | I | 0 | 0 | R |
| 14 | Tiger USB Critical | 2008-10-02 06:30:02
| B | I | 0 | 0 | R |
+-------+--------------------+---------------------+------+-------+----------+----------------+-----------+
*
02-Oct 06:30 tiger-dir JobId 14: Start Backup JobId 14, Job=Tiger_USB_Critical.2008-10-02_06.30.04
*messages
You have no messages.
*cancel
No Jobs running.
*
----- Original Message ----
From: Dan Langille <dan AT langille DOT org>
To: Bill Damage <bill.damage AT yahoo DOT com>
Cc: bacula-users AT lists.sourceforge DOT net
Sent: Tuesday, September 30, 2008 12:46:50
PM
Subject: Re: [Bacula-users] Director dies every morning!
On Sep 30, 2008, at 4:15 AM, Bill Damage wrote:
> 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:
Does that job fail?
>
>
> [root@tiger ~]# bconsole
> Connecting to Director tiger:9101
> 30-Sep 09:11 bconsole JobId 0: Fatal error: bsock.c:129 Unable to
> connect to Director daemon on tiger:9101. ERR=Connection refused
>
> If I restart bacule it lets me in. How can I find out why its dying
> please?
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 Langille
http://langille.org/