------------------------------

Message: 7
Date: Tue, 23 Sep 2008 21:54:34 +0200
From: Nils Blanck-Wehde <nils.blanck-wehde AT backofficeservice DOT biz>
Subject: Re: [Bacula-users] bconsole error from Bacula client
Cc: bacula-users AT lists.sourceforge DOT net
Message-ID: <48D9497A.3020300 AT backofficeservice DOT biz>
Content-Type: text/plain; charset="iso-8859-1"

I can confirm that in a CentOS standard install this port will be blocked.
Opening the required ports (system-config-securitylevel) is very easy.
Nevertheless I ran in some problems running bacula with selinux enabled.
I think that with some tweaking to the default policies bacula should
run fine with selinux enabled I was just too lazy to figure it out...

Nils

Win Htin schrieb:
> I'm starting to suspect CentOS is blocking that particular port; I
> need to look into the selinux configurations. Following are the
> results of various tests I did:
>
> # Telnet to Bacula server port test:
> [win@client01 ~]$ telnet baculaserver 9101
> Trying 192.168.12.44...
> telnet: connect to address 192.168.12.44 <http://192.168.12.44>: No
> route to host
> telnet: Unable to connect to remote host: No route to host
>
> # Telnet to a different host test:
> [win@client01 ~]$ telnet sqlserver 9101
> Trying 192.168.12.234...
> Connected to sqlserver.qwerty.com <http://sqlserver.qwerty.com>
> (192.168.12.234 <http://192.168.12.234>).
> Escape character is '^]'.
> ^]
> telnet> quit
> Connection closed.
>
> # Ping bacula server test:
> [win@client01 ~]$ ping baculaserver
> PING baculaserver (192.168.12.44 <http://192.168.12.44>) 56(84) bytes
> of data.
> 64 bytes from baculaserver (192.168.12.44 <http://192.168.12.44>):
> icmp_seq=0 ttl=61 time=8.55 ms
> 64 bytes from baculaserver (192.168.12.44 <http://192.168.12.44>):
> icmp_seq=1 ttl=61 time=8.80 ms
> 64 bytes from baculaserver (192.168.12.44 <http://192.168.12.44>):
> icmp_seq=2 ttl=61 time=8.82 ms
> 64 bytes from baculaserver (192.168.12.44 <http://192.168.12.44>):
> icmp_seq=3 ttl=61 time=8.83 ms
>
> --- baculaserver ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3005ms
> rtt min/avg/max/mdev = 8.556/8.754/8.835/0.162 ms, pipe 2
>
> # ssh test to Bacula server:
> [win@client01 ~]$ ssh baculaserver
> The authenticity of host 'baculaserver (192.168.12.44
> <http://192.168.12.44>)' can't be established.
> RSA key fingerprint is d6:0c:04:97:12:2b:7e:e3:dd:56:7e:85:8c:c3:1e:ea.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'baculaserver,192.168.12.44
> <http://192.168.12.44>' (RSA) to the list of known hosts.
> win@baculaserver's password:
> Last login: Mon Sep 22 16:31:10 2008 from fb0737.qwerty.com
> <http://fb0737.qwerty.com>
> [win@baculaserver ~]$ <== (Logged in successfully to baculaserver)
>
> On Tue, Sep 23, 2008 at 2:38 PM, Dan Langille <dan AT langille DOT org
> <mailto:dan AT langille DOT org>> wrote:
>
>
>     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