 |
Hello, please understand that this is a bugtracker. This means that it is intended to track bugs. If bareos does not behave as you expect, this does not mean that you have found a bug. Please write such problems to the bareos-users mailinglist instead of filing a bug. Regarding your problem: "Elapsed time: 2 hours 4 secs" sounds like your firewall has a maximum session time of two hours and kills the connection. Either configure your firewall to have a long enough session time or use the "Heartbeat Interval" directives create network traffic that keeps the connection open. I hope this solves your problem. Best regards, Philipp |
|
|
Hallo Philipp >If bareos does not behave as you expect, this does not mean that you have found a bug. Absolutely I interpreted the log like this: 22-May-2015 17:21: Job Started 22-May-2015 17:48: Client successfully finished backup: 2.694 GB in 5,973 files sent to storage daemon. Status (on client side): OK. The Director misses the state change, potentially because the client side closes the socket connection to the director prematurely. 22-May-15 19:21: The Director times out after 2 hours, and as the connection is already closed, it records a network error. With small amount of data to be stored (a couple of 10 MBs), the behaviour did not show, and the jobs completed successfully. I do not know the protocol between client and director, and its underlying state machine. It is however obvious, that it needed to be changed for the implementation of the passive mode -- meaning that there are rather recent additions in this part of the code. I am still not convinced that it is not a bug. I have read that you thoroughly test the software before releasing a new feature. Hence I am thinking of a glitch in the protocol machine for the passive mode that only shows given special preconditions (like an amount of data bigger than a certain threshold combined with client and director being in different nets) I will read about the "Heartbeat Interval" directive, and give this a go. Thanks Tilman |
|
|
Dear Philipp setting the heartbeat interval fixes the issue. So it is apparently not a bug, but a user issue on my part. Thanks for your support Tilman |
- Anonymous
