Hello,
we have a problem with our configuration. When a client is offline, the
director detects it and sends a retry order (because of ERR=Connection refused):
2018-11-05 12:18:42 bareos-dir JobId 463: Warning: lib/bsock_tcp.cc:133
Could not connect to Client: LinuxTest on 192.168.142.229:9102. ERR=Connection
refused
Retrying ...
But it stucks on this step with the job status Running, and never ends. If I
have other jobs waiting this one, they never start, keeping all the time
enqueued.
To try to solve this situation (it has to be done on the director or the
storage daemon, as the file daemon is offline), I've configured this parameters
in the director configuration (bareos-dir.d/director/bareos-dir.conf):
Heartbeat Interval = 30
FD Connect Timeout = 180
SD Connect Timeout = 180
In the director definition of the client, I have cnofigured the HeartBeat
parameter too (bareos-dir.d/client/LinuxTest.conf):
Client {
Name = LinuxTest
Address = a.b.c.d
Password = *****
Heartbeat interval = 30
}
But I get no success.
Thanks in advanced,
Albert
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
