Hi,

Yes, thanks, I traced the problem to the stop script not stopping the fd 
DAemon, so it never re-read the .conf so never picked up the 
changes...none of the scripts work (stop the sd or director), so I 
suspect I have mis-configured or mis-installed bacula, so I need to 
figure out waht went wrong....

regards

Steven


John Drescher wrote:
> On Tue, Jul 8, 2008 at 5:03 AM, thing <thing AT thing.dyndns DOT org> wrote:
>   
>> Hi,
>>
>> I have an issue with the director refusing to connect on 127.0.0.1 to
>> the fd....
>>
>> Any ideas where I start looking? the /etc/bacula/bacula-fd.conf and
>> bacula-director.conf both point to the local hsot but when I do a stuts
>> I get,
>>
>> ============
>> Using default Catalog name=MyCatalog DB=bacula
>> Status available for:
>>     1: Director
>>     2: Storage
>>     3: Client
>>     4: All
>> Select daemon type for status (1-4): 3
>> Automatically selected Client: hermes-fd
>> Connecting to Client hermes-fd at hermes:9102
>> Failed to connect to Client hermes
>> *
>> 08-Jul 20:58 hermes-dir: *Console*.2008-07-08_20.58.15 Fatal error:
>> bnet.c:859 Unable to connect to File daemon on hermes:9102.
>> ERR=Connection refused
>> *
>> ===========
>>
>> Why woudnt the director try to attach to the localhost?
>>
>>     
> Do you have FDAddress set in your bacula-fd.conf?
>
> John
>   


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users