On 3/12/2012 9:58 AM, Silver Salonen wrote:
On Tuesday 06 March 2012 14:44:33 Silver Salonen wrote:
So I've confirmed that what is to blame here is pfSense's port
reflection. From forums I've found that supposedly it means that the
port redirection is done with netcat instead of PF (which is
On Tuesday 28 February 2012 16:07:50 Christopher Hylarides wrote:
I'm not sure why (I haven't had the need to dig this deep), but with
large backups (well all of them, really) bacula-dir connects to the FD,
then the FD starts doing stuff while the DIR still maintains the
connection. So it
On Thursday 23 February 2012 11:11:54 Silver Salonen wrote:
On Wednesday 22 February 2012 15:20:10 Silver Salonen wrote:
On Wed, 22 Feb 2012 12:33:49 +0100, Hugo Letemplier wrote:
I think you can try to configure the Heartbeat Interval directive on
your various daemons.
Hi.
My
On 02/28/2012 05:00 AM, Silver Salonen wrote:
I look at these lines:
28-Feb 00:04 backupsrv-dir JobId 58414: Sending Accurate information.
28-Feb 00:07 backupsrv-sd2 JobId 58414: Recycled volume
fbsd1-userdata-incr-6106 on device device-fbsd1
(/mnt/backup/bacula/fbsd1), all previous data
On Tuesday 28 February 2012 08:26:50 Phil Stracchino wrote:
On 02/28/2012 05:00 AM, Silver Salonen wrote:
I look at these lines:
28-Feb 00:04 backupsrv-dir JobId 58414: Sending Accurate information.
28-Feb 00:07 backupsrv-sd2 JobId 58414: Recycled volume
fbsd1-userdata-incr-6106 on
I'm not sure why (I haven't had the need to dig this deep), but with
large backups (well all of them, really) bacula-dir connects to the FD,
then the FD starts doing stuff while the DIR still maintains the
connection. So it could be timing out after half an hour and then later
when the DIR
I had a similar issue that was solved by tweaking my TCP-keepalives at
the kernel level that my director was on (in my case Solaris).
My case was on a LAN, but with over 300GB. It would fail at exactly the
same time.
Christopher Hylarides
Systems Administrator
OANDA Corporation
On Monday 27 February 2012 09:29:13 Christopher Hylarides wrote:
I had a similar issue that was solved by tweaking my TCP-keepalives at
the kernel level that my director was on (in my case Solaris).
My case was on a LAN, but with over 300GB. It would fail at exactly the
same time.
Hi.
On Thu, 23 Feb 2012 10:49:55 -0500, Josh Fisher wrote:
On 2/23/2012 4:11 AM, Silver Salonen wrote:
On Wednesday 22 February 2012 15:20:10 Silver Salonen wrote:
What's also interesting about these failures are these lines
(similar in all these failing jobs):
FD Files Written: 381
On Wednesday 22 February 2012 15:20:10 Silver Salonen wrote:
On Wed, 22 Feb 2012 12:33:49 +0100, Hugo Letemplier wrote:
I think you can try to configure the Heartbeat Interval directive on
your various daemons.
Hi.
My SD already had Heartbeat Interval set to 60. I now tried it on one
I think you can try to configure the Heartbeat Interval directive on
your various daemons.
2012/2/22 Silver Salonen sil...@serverock.ee:
Hi.
Recently we changed the network connection for our backup server which is
Bacula 5.2.3 on FreeBSD 9.0.
After that many jobs running across WAN
On Wed, 22 Feb 2012 12:33:49 +0100, Hugo Letemplier wrote:
I think you can try to configure the Heartbeat Interval directive on
your various daemons.
Hi.
My SD already had Heartbeat Interval set to 60. I now tried it on one
FD too, but the job still failed with the same error.
Other FD's on
Hi.
Recently we changed the network connection for our backup server which is
Bacula 5.2.3 on FreeBSD 9.0.
After that many jobs running across WAN started failing with various broken
pipe errors. Some examples:
21-Feb 22:42 fbsd1-fd JobId 57779: Error: bsock.c:398 Wrote 32151 bytes to
13 matches
Mail list logo
