On Sun, Apr 18, 2010 at 11:46:33AM -0500, Jon Schewe wrote:
http://wiki.bacula.org/doku.php?id=faq#my_backup_starts_but_dies_after_a_while_with_connection_reset_by_peer_error
[1] It actually tries that at one point in src/lib/bsock.c if
TCP_KEEPIDLE support is detected, but it fails to
On 04/16/2010 08:30 AM, Matija Nalis wrote:
On Mon, Apr 12, 2010 at 03:59:49PM -0500, Jon Schewe wrote:
On 4/12/10 9:40 AM, Matija Nalis wrote:
It is especially problem with bigger databases and MySQL instead of
PostgreSQL, see http://bugs.bacula.org/view.php?id=1472, where it can
On Mon, Apr 12, 2010 at 03:59:49PM -0500, Jon Schewe wrote:
On 4/12/10 9:40 AM, Matija Nalis wrote:
It is especially problem with bigger databases and MySQL instead of
PostgreSQL, see http://bugs.bacula.org/view.php?id=1472, where it can
take even several hours! (note that while it talks
On Sun, Apr 11, 2010 at 09:32:43AM -0500, Jon Schewe wrote:
I got it to work again last night. Changing the firewall time outs
didn't help. What fixed it was turning off Accurate backups.
Ah, so possibly bacula spent long enough stuck doing an accurate query in the
catalog that the firewall
On Fri, Apr 09, 2010 at 07:30:19PM -0500, Jon Schewe wrote:
I have heartbeat intervals set at the following:
bacula-dir.conf:
client {
Heartbeat interval = 15 Seconds
}
storage {
Heartbeat interval = 1 minutes
}
bacula-sd.conf
storage {
Heartbeat interval = 1 minute
}
On 04/12/2010 04:17 AM, Matija Nalis wrote:
On Fri, Apr 09, 2010 at 07:30:19PM -0500, Jon Schewe wrote:
I have heartbeat intervals set at the following:
bacula-dir.conf:
client {
Heartbeat interval = 15 Seconds
}
storage {
Heartbeat interval = 1 minutes
}
bacula-sd.conf
storage
On Mon, Apr 12, 2010 at 05:41:51AM -0500, Jon Schewe wrote:
Strange. Are you running GNU/Linux system on all the machines
(FD, SD, DIR) ? IIRC, it might not be supported on other systems,
and/or it may need additional tuning on them.
I'm running opensuse Linux for the director and
On 4/12/10 7:21 AM, Matija Nalis wrote:
On Mon, Apr 12, 2010 at 05:41:51AM -0500, Jon Schewe wrote:
Strange. Are you running GNU/Linux system on all the machines
(FD, SD, DIR) ? IIRC, it might not be supported on other systems,
and/or it may need additional tuning on them.
On Mon, Apr 12, 2010 at 07:59:53AM -0500, Jon Schewe wrote:
/proc/sys/net/ipv4/tcp_keepalive_time:7200
netstat -to
Client:
tcp0 0 client:9102 server:54043 ESTABLISHED
keepalive (7196.36/0/0)
That's strange. It should've been the timeouts you specified in
config
On 4/12/10 8:39 AM, Matija Nalis wrote:
On Mon, Apr 12, 2010 at 07:59:53AM -0500, Jon Schewe wrote:
/proc/sys/net/ipv4/tcp_keepalive_time:7200
netstat -to
Client:
tcp0 0 client:9102 server:54043 ESTABLISHED
keepalive (7196.36/0/0)
That's
On 4/12/10 9:00 AM, Matija Nalis wrote:
On Mon, Apr 12, 2010 at 08:45:36AM -0500, Jon Schewe wrote:
On 4/12/10 8:39 AM, Matija Nalis wrote:
echo 60 /proc/sys/net/ipv4/tcp_keepalive_time
(or edit /etc/sysctl.d/* or /etc/sysctl.conf to retain value across
reboots). Can you try what
On Mon, Apr 12, 2010 at 09:23:51AM -0500, Jon Schewe wrote:
On 4/12/10 9:00 AM, Matija Nalis wrote:
(SO_KEEPALIVE will work even with only one side of connection having
it enabled).
So I should only need the heartbeat on that client's setup as well,
right? Getting rid of extra heart
On 4/12/10 9:40 AM, Matija Nalis wrote:
On Mon, Apr 12, 2010 at 09:23:51AM -0500, Jon Schewe wrote:
On 4/12/10 9:00 AM, Matija Nalis wrote:
Good, let us know how it fares.
It seems to be running, but I've run into a problem with bconsole. Once
I started the job, if I run
I got it to work again last night. Changing the firewall time outs
didn't help. What fixed it was turning off Accurate backups.
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed
On 04/09/2010 02:33 AM, jerry lowry wrote:
On 4/10/2010 3:30 AM, Jon Schewe wrote:
On 04/08/2010 07:04 AM, Matija Nalis wrote:
On Wed, Apr 07, 2010 at 02:15:14PM +0100, Prashant Ramhit wrote:
b06-Apr 12:54 client-fd JobId 299: Fatal error: backup.c:892 Network
I increased the connection timeout and started another job and got this:
10-Apr 08:11 jon-dir JobId 5334: Start Backup JobId 5334,
Job=mtu.2010-04-10_08.11.11_32
10-Apr 08:11 jon-dir JobId 5334: Using Device FileStorage
10-Apr 08:11 mtu-fd JobId 5334: shell command: run ClientRunBeforeJob
On 4/10/2010 3:30 AM, Jon Schewe wrote:
On 04/08/2010 07:04 AM, Matija Nalis wrote:
On Wed, Apr 07, 2010 at 02:15:14PM +0100, Prashant Ramhit wrote:
b06-Apr 12:54 client-fd JobId 299: Fatal error: backup.c:892 Network send
error to SD. ERR=Connection reset by peer/b/small/pre
On Wed, Apr 07, 2010 at 02:15:14PM +0100, Prashant Ramhit wrote:
b06-Apr 12:54 client-fd JobId 299: Fatal error: backup.c:892 Network send
error to SD. ERR=Connection reset by peer/b/small/pre
Is it possible to tell me how to enable more debug on client and
storage so that i can find more
Hi All,
My Backup is failing on a client.
The client has only one Fileset and the size is 400GB.
The error is as follows
Messages:
06-Apr 12:16 server-sd JobId 299: Spooling data again ...
06-Apr 12:38 server-sd JobId 299: User specified spool size reached.
06-Apr 12:38 server-sd JobId 299:
19 matches
Mail list logo
