On 03.10.19 at 16:15 wrote Brock Palen: > I am running into issues where roaming clients using client initiated > connections are un-reliable. They worked very well for a number of months but > now I find that clients that we know are online, and the director reports as > connected something as simple as > > status client=<client> > > Will just drop the connection,
So, will (1) the status command get executed, you receive an answer and the connection is lost after this, or will (2) the connection close immediately? > eventually the client comes back, but it causes a lot of backup failures > and unreliable reporting. > > All clients are windows 10. > > Has anyone started seeing this? Should we try tuning some timeouts? Right > now they are defaults. On 1: Well, it works a designed. A connection is only used for one task/job. On Client Initiated Connection the FD opens up a connection to the Director. When the Director uses this connection, either by running a job or running a status command, the FD opens up another connection, so the Director has a spare one available. The connection used by the Director will be closed after the task/job. On 2: Yes, you should set Heartbeat Interval like described in the documentation: https://docs.bareos.org/TasksAndConcepts/NetworkSetup.html#client-initiated-connection Regards, Jörg -- Jörg Steffens [email protected] Bareos GmbH & Co. KG Phone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/qn77vf%24871e%241%40blaine.gmane.org.
