Hello Together,
I get the folloing message when I ask for the Status of Storage File
Fatal error: bsock.c:135 Unable to connect to Storage daemon on
backupsrv.ke-si.intern:9103. ERR=Connection refused
DNS is correct Sever Name is checkt many times FQN is in hosts too. Password
is proofed.
I get the folloing message when I ask for the Status of Storage File
Fatal error: bsock.c:135 Unable to connect to Storage daemon on
backupsrv.ke-si.intern:9103. ERR=Connection refused
DNS is correct Sever Name is checkt many times FQN is in hosts too. Password
is proofed.
When I use
On Mon, Dec 7, 2009 at 9:56 AM, John Drescher dresche...@gmail.com wrote:
I get the folloing message when I ask for the Status of Storage File
Fatal error: bsock.c:135 Unable to connect to Storage daemon on
backupsrv.ke-si.intern:9103. ERR=Connection refused
DNS is correct Sever Name is
On Mon, Dec 07, 2009 at 06:33:59AM -0800, Oliver Knittel wrote:
Hello Together,
I get the folloing message when I ask for the Status of Storage File
Fatal error: bsock.c:135 Unable to connect to Storage daemon on
backupsrv.ke-si.intern:9103. ERR=Connection refused
DNS is correct Sever
basis. So telnet may fail and bacula succeeds, or vice versa.
-Original Message-
From: Oliver Knittel [mailto:o...@systemhaus-kec.de]
Sent: Monday, December 07, 2009 6:34 AM
To: bacula-users@lists.sourceforge.net
Subject: [Bacula-users] Bacula Problem Storage File
Hello Together
Oliver Knittel wrote:
Hello Together,
I get the folloing message when I ask for the Status of Storage File
Fatal error: bsock.c:135 Unable to connect to Storage daemon on
backupsrv.ke-si.intern:9103. ERR=Connection refused
DNS is correct Sever Name is checkt many times FQN is in hosts
Everything didnt work. now I install the Serve new and keep my config files.
I will tell the result soon to you. Via telnet it was posible to get on the
comp. now I changed the name from backuupsrv to backup.
Oliver Knittel wrote:
Hello Together,
I get the folloing message when I ask
