On Mon, Jul 11, 2011 at 2:41 PM, rlh1533 <bacula-forum AT backupcentral DOT 
com> wrote:
> I've searched everywhere and can't seem to find the solution. My current 
> setup is such that I have bacula-dir, bacula-fd, and bacula-sd installed on 
> one CentOS 5.5 machine, and just the client (bacula-fd) installed on another 
> CentOS 5.5 machine. iptables is totally off and is not running on either 
> machine. I can ping between the two devices, and I can also telnet from the 
> client to the backup server with ports 9101, 9102, and 9103. Passwords in the 
> bacula-fd.conf, bacula-sd.conf, bacula-dir.conf, and bacula.conf as well as 
> bacula-fd.conf on the client machine are all the same. Output of 
> /var/bacula/working/log is empty, unless I cancel the job, in which case it 
> reports that it's been cancelled with the usual information. I'm not seeing 
> any error messages anywhere, it's just that the client hangs when I try to do 
> the backup, and "messages" from bconsole reads:
>
> "<client & date> is waiting for Client <client> to connect to Storage File"
>
> And that's as far as it gets. Does anyone have any ideas? Please help..
>

Have you removed localhost and 127.0.0.1 from your bacula config files
and replaced this with the external ip address? Some distros ship
default configurations that prevent bacula from being a network backup
application..

John

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users