Maybe I should be actually posting this to the dev list on account of
the version being fresh out of the oven...
Anyway, I have a weird problem going on. Both the storage daemon and
the sole client are set up with a heartbeat interval (30 seconds),
but the backup always dies five minutes and five seconds into the
connection, give or take a second. It doesn't seem to matter whether
TLS is enabled or not. The SD claims a broken pipe error, and the
client claims a connection reset by peer.
I know data is being poured into the storage daemon from checking
with tcpdump, but the 5:05 timeout seems to be the same as the
symptom for inactivity. An idle netcat connection between the two
machines times out in almost exactly the same period.
There is some IP/Firewall weirdness going on for each machine (co-
located at different providers), but I was able to connect from the
client machine to the SD port on the server and keep the connection
active indefinitely in tests with netcat. (Sending a bit of data
every minute.)
Is it possible that the heartbeat interval isn't working for some
reason? (No detected config errors...)
Thanks in advance,
--
--Darien A. Hager
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
