I did as suggested and from Kira to Emma it was "instantaneous". I did this multiple times.
Remember, I've stopped IPTABLES on both machines off, to eliminate possible issues (even though I opened the correct ports). Thanks Wayne -----Original Message----- From: Martin Simmons [mailto:mar...@lispworks.com] Sent: Friday, January 07, 2011 2:19 PM To: Bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] REPOST Can't connect to Remote. OK, the output shows that bacula is interrupting the connect itself, as a way to prevent it from hanging indefinitely. It looks like the error could be reported better, but the upshot is that connect is hanging unexpectedly. Does the "Interrupted system call" happen after a delay of 3 minutes (or the configured FD Connect Timeout)? I suggest trying telnet 192.68.0.30 9102 on kira to see if that can connect to emma reliably. __Martin p.s. I've replied to the list again. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
