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/





-------------------------------------------------------------------------
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 prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users