On Sep 23, 2008, at 11:24 AM, Win Htin wrote:

> Hi folks,
>
> I reconfigured one of my Bacula clients running version 2.2.6 to  
> connect to a new 2.4.2 server for testing and got the following error:
>
> [bacula@client01 ]  /etc/bacula/bin/bconsole
> Connecting to Director baculaserver:9101
> 23-Sep 10:58 bconsole JobId 0: Fatal error: bsock.c:129
> Unable to connect to Director daemon on baculaserver:9101.
> ERR=No route to host

This is a networking issue as I see it.

client01 cannot connect to baculaserver.

I've seen the other posts in the thread.  The above still applies.

>
>
> I've triple checked to see the "Password" entries are correct in  
> both bconsole.conf and bacula-fd.conf files. Client is running RHEL  
> 4 and server is CentOS 5.2.

Password entries are not relevant until comms can be established.

>
>
> Any help is much appreciated.
>
> Win
> -------------------------------------------------------------------------
> 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

-- 
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