i have set FD Connect Timeout = 2min in the director config
if the fd ist stopped and the client-system is running, i get :
22-Aug 12:13 backup-dir: thomasws2.2007-08-22_12.11.28 Fatal error:
bsock.c:129 Unabl
e to connect to File daemon on thomasws2:9102. ERR=Connection refused
22-Aug
Hi Ryan,
On Wednesday 22 August 2007 01:47:45 am Ryan Novosielski wrote:
John Drescher wrote:
Of course it is not running, that's what the whole story is about. I
have a bunch of desktop/laptop clients configured that can be shut
down/disconnected/not around at random and are well beyond
On Tue, 21 Aug 2007, Ivan Adzhubey wrote:
Of course it is not running, that's what the whole story is about. I have a
bunch of desktop/laptop clients configured that can be shut
down/disconnected/not around at random and are well beyond my control.
Add a RunBeforeJob to ping the hosts and
On 22 Aug 2007 at 2:01, Ivan Adzhubey wrote:
Hi Ryan,
On Wednesday 22 August 2007 01:47:45 am Ryan Novosielski wrote:
John Drescher wrote:
Of course it is not running, that's what the whole story is about. I
have a bunch of desktop/laptop clients configured that can be shut
Hi Alan,
On Wednesday 22 August 2007 06:03:51 am Alan Brown wrote:
On Tue, 21 Aug 2007, Ivan Adzhubey wrote:
Of course it is not running, that's what the whole story is about. I have
a bunch of desktop/laptop clients configured that can be shut
down/disconnected/not around at random and
I am well aware of this solution but as I wrote before I consider it a hack.
Let me summarize why. First of all, I am positively certain that any network
connectivity issues have to be a core part of any network enabled software. I
can't imagine why Bacula developers deny this obvious fact.
I
Hi,
Just upgraded from 1.36.1 to 1.38.11 (last binaries a could found for our old
RedHat 8.0 box), now I am fighting with this dreadful infinite client timeout
bug (err..., feature). One thing I can't understand: when client is
unavailable, that's what I see in director's log after initial
On 8/21/07, Ivan Adzhubey [EMAIL PROTECTED] wrote:
Hi,
Just upgraded from 1.36.1 to 1.38.11 (last binaries a could found for our old
RedHat 8.0 box), now I am fighting with this dreadful infinite client timeout
bug (err..., feature). One thing I can't understand: when client is
unavailable,
Hi John,
On Tuesday 21 August 2007 02:52:22 pm John Drescher wrote:
On 8/21/07, Ivan Adzhubey [EMAIL PROTECTED] wrote:
Hi,
Just upgraded from 1.36.1 to 1.38.11 (last binaries a could found for our
old RedHat 8.0 box), now I am fighting with this dreadful infinite client
timeout bug
Of course it is not running, that's what the whole story is about. I have a
bunch of desktop/laptop clients configured that can be shut
down/disconnected/not around at random and are well beyond my control.
Sorry. I totally missed your point but I see now.
I want
bacula to cease any further
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Drescher wrote:
Of course it is not running, that's what the whole story is about. I have a
bunch of desktop/laptop clients configured that can be shut
down/disconnected/not around at random and are well beyond my control.
Sorry. I totally
11 matches
Mail list logo
