(Looks like my last message was misaddressed. Resending.)
On Jan 30, 2007, at 1:09 PM, Kern Sibbald wrote:
> Another thing to check for is HP printers on the network [...]
I don't think that's the problem in my case. While we have an HP
server on our internal office network, the two servers I w
On Tuesday 30 January 2007 20:24, Darien Hager wrote:
> On Jan 30, 2007, at 1:02 AM, Arno Lehmann wrote:
> > As far as I know, the heartbeat is not sent during despooling and / or
> > attribute despooling. So, if you have that enabled, try turning it off
> > to see what happens.
>
> I haven't enabl
On Jan 30, 2007, at 1:02 AM, Arno Lehmann wrote:
> As far as I know, the heartbeat is not sent during despooling and / or
> attribute despooling. So, if you have that enabled, try turning it off
> to see what happens.
I haven't enabled spooling--I'm backing up to a plain old file on the
server,
Darien
Do you have access to the firewalls?
The problem could be in
/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established that
is usually 5 days it could have been changed on one of the firewalls
Have you set SD or FD Connect timeout to 5 seconds ? If you have grep
for 300 in /pro
Hello,
On 1/30/2007 7:08 AM, Darien Hager wrote:
>
> Maybe I should be actually posting this to the dev list on account of
> the version being fresh out of the oven...
Oh, it's released and as such problems should be discussed here, IMO.
> Anyway, I have a weird problem going on. Both the stor
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
