Hi there,
I found some debug message on the client sugar. Please help me to check.
Please don't mind that I masked the IP address of backup server.
Successful Backup Run for sugar (Another directories) debug file
===================================================
sendbackup: debug 1 pid 18955 ruid 5023 euid 5023 start time Wed Jul 4 03:43:13
2001
/usr/local/amanda/libexec/sendbackup: version 2.4.2p2
sendbackup: got input request: GNUTAR /usr/local/mysql 1 2001:6:27:19:16:16 OPTI
ONS |;bsd-auth;compress-best;index;
parsed request as: program `GNUTAR'
disk `/usr/local/mysql'
lev 1
since 2001:6:27:19:16:16
opt `|;bsd-auth;compress-best;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: stream_server: waiting for connection: 0.0.0.0.34388
sendbackup: stream_server: waiting for connection: 0.0.0.0.34389
sendbackup: stream_server: waiting for connection: 0.0.0.0.34390
waiting for connect on 34388, then 34389, then 34390
sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62714
sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62715
sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62716
got all connections
sendbackup: spawning /bin/gzip in pipeline
sendbackup: argument list: /bin/gzip --best
sendbackup-gnutar: pid 18956: /bin/gzip --best
sendbackup-gnutar: doing level 1 dump as listed-incremental from /usr/local/aman
da/var/gnutar-lists/sugar_usr_local_mysql_0 to /usr/local/amanda/var/gnutar-list
s/sugar_usr_local_mysql_1.new
sendbackup-gnutar: doing level 1 dump from date: 2001-06-27 19:16:16 GMT
sendbackup: spawning /usr/local/amanda/libexec/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory /usr/local/mysql -
-one-file-system --listed-incremental /usr/local/amanda/var/gnutar-lists/sugar_u
sr_local_mysql_1.new --sparse --ignore-failed-read --totals .
sendbackup-gnutar: /usr/local/amanda/libexec/runtar: pid 18958
sendbackup: started index creator: "/bin/gtar -tf - 2>/dev/null | sed -e 's/^\./
/'"
sendbackup: index created successfully
sendbackup: pid 18955 finish time Wed Jul 4 03:43:21 2001
Failed Sugar Dump File
===================
sendbackup: debug 1 pid 18993 ruid 5023 euid 5023 start time Wed Jul 4 03:43:28
2001
/usr/local/amanda/libexec/sendbackup: version 2.4.2p2
sendbackup: got input request: GNUTAR /export/home 0 1970:1:1:0:0:0 OPTIONS |;bs
d-auth;compress-fast;index;
parsed request as: program `GNUTAR'
disk `/export/home'
lev 0
since 1970:1:1:0:0:0
opt `|;bsd-auth;compress-fast;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: stream_server: waiting for connection: 0.0.0.0.34398
sendbackup: stream_server: waiting for connection: 0.0.0.0.34399
sendbackup: stream_server: waiting for connection: 0.0.0.0.34400
waiting for connect on 34398, then 34399, then 34400
sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62717
sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62718
sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62719
got all connections
sendbackup: spawning /bin/gzip in pipeline
sendbackup: argument list: /bin/gzip --fast
sendbackup-gnutar: pid 18994: /bin/gzip --fast
sendbackup-gnutar: doing level 0 dump as listed-incremental to /usr/local/amanda
/var/gnutar-lists/sugar_export_home_0.new
sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT
sendbackup: spawning /usr/local/amanda/libexec/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory /export/home --one
-file-system --listed-incremental /usr/local/amanda/var/gnutar-lists/sugar_expor
t_home_0.new --sparse --ignore-failed-read --totals .
sendbackup-gnutar: /usr/local/amanda/libexec/runtar: pid 18996
sendbackup: started index creator: "/bin/gtar -tf - 2>/dev/null | sed -e 's/^\./
/'"
index tee cannot write [Broken pipe]
sendbackup: pid 18995 finish time Wed Jul 4 05:43:45 2001
Failed backup occured because the index tee cannot write.
Is it related to local client or server-side ?
In my firewall, connection timeout is 60 minutes. I think that it's pretty long.
Regards,
Edward.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of John R. Jackson
Sent: Wednesday, July 04, 2001 2:42 AM
To: Edward Tsang
Cc: [EMAIL PROTECTED]
Subject: Re: Connection reset by peer problem again
>... Firewall is present between the client and amanda server. But we already ope
>ned a full hole for amanda traffic.
>...
> sugar /export/home lev 0 FAILED [mesg read: Connection reset by peer]
This says the client (or the firewall) closed this connection and dumper
on the server was not happy about that.
There are either two or three connections between the client and dumper.
The mesg one passes log message from the client back to dumper. It is
(usually) very low activity. The data path sends the actual dump image
and should be very active. The index path is optional and sends the
catalogue. It can either be high activity at the beginning (if you're
using dump) or sporadic (GNU tar).
>From above report, we can observe that amanda can perform backup on other dire
>ctories on the host 'sugar'. But it can't perform backup on the /export/home d
>irectory.
About my only guess is that the firewall timed out the connection.
There would be very little traffic on the mesg path. So you may need
to tweak the firewall configuration some more.
You might take a look at the /tmp/amanda/sendbackup*debug file
on the client that goes along with this file system (if you used
--with-pid-debug-files on ./configure or are running 2.4.2p2) and see
what kinds of timestamps it shows. Take a look at the last modification
time on the file as well (ls -l).
>Edward.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
