 |
Looking at some configs from the zillion other problems you opened it seems you have some problems understanding the meaning of the heartbeat mechanism. Either setup the heartbeat right (e.g. if you really need it, its only needed when you have connections through firewalls that otherwise time out) or set it to a proper value e.g. every 300 seconds or so. What probably happens now is that you set a value that is to low 0 (which makes absolutely no sense, did you mean to disable it ? then don't set it at all as that is default.) the TCP_KEEPIDLE setting is something that was in Bacula for ages so its been working for ages already so as long as you set correct values things tend to work fine. B.T.W. most problems you opened in the bug tracker are not really bugs but more misinterpretations from the docs so maybe it helps to first post one mail to the users mailinglist with the issues you ran into. |
|
|
1. From the docs: "The default value is zero, which means no change is made to the socket." Setting it explicitly to zero should not - and does not - generate this error. So that works as expected. 2. I had it set to 1 (one) when I was getting this error, as I was trying to determine if my firewall was part of the problem. As far as I can tell, this error still should not have been generated; I've followed the code path and I can't see any reason I can't set TCP_KEEPIDLE to 1. Unless it's another Capabilities / permissions problem? Yes, that's a silly setting for production, but I was trying to debug. As soon as the current backup finishes, I'll test to see if there is in fact a lower bound, or whether it's global (which might indicate a permission problem or something like that). |
|
|
Cannot reproduce in nightly build. I'm not going back to crashing build (15.2.1) right now just to test this, so keep it closed - sorry for the noise. |
- Anonymous
