Op 20121016 om 10:35 schreef Константин Поветкин:
> Hi, all!
Hello again,
> After a while backup job reports: Socket error. Err = Connection reset by
> peer.
>
> I`ve read
> http://wiki.bacula.org/doku.php?id=faq#my_backup_starts_but_dies_after_a_while_with_connection_reset_by_peer_error
> a
Hi, all!
After a while backup job reports: Socket error. Err = Connection reset by peer.
I`ve read
http://wiki.bacula.org/doku.php?id=faq#my_backup_starts_but_dies_after_a_while_with_connection_reset_by_peer_error
and comments on this mail list.
Both FD and DIR are in one broadcast domain and
Just to get this into google for anybody else who may have this issue, I
fixed it my tuning my kernel's TCP keepalive setting to 15 seconds.
On solaris it can be done with this:
/usr/sbin/ndd -set /dev/tcp tcp_keepalive_interval 15000
Christopher Hylarides
Systems Administrator
OANDA Corporati
On 12-01-27 9:03 AM, René Moser wrote:
> Hi Chris
>
> On Thu, 2012-01-26 at 13:29 -0500, Christopher Hylarides wrote:
>>
>> Scheduled time: 25-Jan-2012 22:00:00
>> Start time: 25-Jan-2012 22:00:01
>> End time: 26-Jan-2012 00:27:32
>> Elapsed time:
Hi Chris
On Thu, 2012-01-26 at 13:29 -0500, Christopher Hylarides wrote:
>
>Scheduled time: 25-Jan-2012 22:00:00
>Start time: 25-Jan-2012 22:00:01
>End time: 26-Jan-2012 00:27:32
>Elapsed time: 2 hours 27 mins 31 secs
It is just a gues
Hey all,
This always happens repeatedly with only this windows client at 2 hours
and 27 minutes no matter what. The Bacula DIR and SD are on a solaris
10 host and on the same subnet, so there is no firewall timing out.
This problem has been happening repeatedly, even before with bacula
5.0.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
scar @ 07/26/2011 06:44 PM:
> i am getting this error on one of my remote clients, work1-fd. what is
> confusing to me is that i have another system, work2-fd, on the same
> network, behind the same router, running the same OS and bacula version
> (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mike Ruskai @ 07/26/2011 08:09 PM:
> So, in short, if you have network problems, suspect network problems.
>
i'll look into it. i find it kind of absurd though, that it only
happens AFTER the backup is finished, and quite some time after. i've
ne
On 7/26/2011 9:44 PM, scar wrote:
> i am getting this error on one of my remote clients, work1-fd. what is
> confusing to me is that i have another system, work2-fd, on the same
> network, behind the same router, running the same OS and bacula version
> (ubuntu 10.04, 5.0.1) which doesn't have any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
i am getting this error on one of my remote clients, work1-fd. what is
confusing to me is that i have another system, work2-fd, on the same
network, behind the same router, running the same OS and bacula version
(ubuntu 10.04, 5.0.1) which doesn't h
hi
since i've upgraded bacula from 2.2.x to 2.4.4 (both backport.org
versions) the full backup (about 3TB) gets a "Connection reset by peer".
dir, sd and fd are on the same network, connected to the same switch - so
no NAT inbetween. with 2.2.x also 4TB backups were no problem.
after searchin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Greenland escribió:
> Start time: 06-Jan-2008 02:02:52
> End time: 06-Jan-2008 04:02:52
> Elapsed time: 2 hours
...
> FD Bytes Written: 0 (0 B)
...
> Other (smaller) jobs from the same client
Looks like the usual Firewall/Router dropping the connection after two
hours, yes?
06-Jan 02:02 moregruel-dir: Start Backup JobId 4501,
Job=Web-fury.2008-01-06_01.05.03
06-Jan 02:02 moregruel-dir: Recycled volume "Vol0033"
06-Jan 02:02 moregruel-sd: Recycled volume "Vol0033" on device "FileStorag
Hi, I'm having some trouble with one particular client on my Bacula
server. I've been running Bacula for over a year now and for this
particular client I'm seeing an odd sequence of events:
29-Oct 03:36 client: DIR and FD clocks differ by 402 seconds, FD
automatically adjusting.
...
29-Oct
Hello,
On 21.10.2005 16:24, Timo Neuvonen wrote:
I just added into my system another file daemon to be baked up.
This new client is dilbert-fd, which is located in the dmz network segment
of a SonicWall firewall, while the director and the storage daemon are on
the lan network segment.
By def
Timo Neuvonen wrote:
> I just added into my system another file daemon to be baked up.
>
> This new client is dilbert-fd, which is located in the dmz network segment
> of a SonicWall firewall, while the director and the storage daemon are on
> the lan network segment.
>
> By default, all traffic
I just added into my system another file daemon to be baked up.
This new client is dilbert-fd, which is located in the dmz network segment
of a SonicWall firewall, while the director and the storage daemon are on
the lan network segment.
By default, all traffic from lan to dmz is allowed. I also
17 matches
Mail list logo