-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jean-Louis Martineau wrote:
> Look in the client sendsize.*.debug or sendbackup.*.debug file to find
> the error reported by tar.

grep finds 'error' several times in sendbackup*; none in sendsize*.
Here's one that looks to be on topic -- from Sunday/Monday night:

> sendbackup: debug 1 pid 15171 ruid 34 euid 34: start at Mon Apr  9 01:09:57 
> 2007
> sendbackup: version 2.5.1p1
> Could not open conf file "/etc/amanda/amanda-client.conf": No such file or 
> directory
> Could not open conf file "/etc/amanda/sls/amanda-client.conf": No such file 
> or directory
> sendbackup: debug 1 pid 15171 ruid 34 euid 34: rename at Mon Apr  9 01:09:57 
> 2007
>   sendbackup req: <GNUTAR /var  2 2007:4:1:7:33:33 OPTIONS 
> |;auth=BSD;index;exclude-list=/var/backups/exclude.sls.gtar;>
>   parsed request as: program `GNUTAR'
>                      disk `/var'
>                      device `/var'
>                      level 2
>                      since 2007:4:1:7:33:33
>                      options 
> `|;auth=BSD;index;exclude-list=/var/backups/exclude.sls.gtar;'
> sendbackup: start: server.slsware.dmz:/var lev 2
> sendbackup-gnutar: time 0.001: doing level 2 dump as listed-incremental from 
> '/var/lib/amanda/gnutar-lists/server.slsware.dmz_var_1' to 
> '/var/lib/amanda/gnutar-lists/server.slsware.dmz_var_2.new'
> sendbackup-gnutar: time 0.023: doing level 2 dump from date: 2007-04-01  
> 7:33:33 GMT
> sendbackup: time 0.024: started index creator: "/bin/tar -tf - 2>/dev/null | 
> sed -e 's/^\.//'"
> sendbackup: time 0.024: spawning /usr/lib/amanda/runtar in pipeline
> sendbackup: argument list: runtar sls gtar --create --file - --directory /var 
> --one-file-system --listed-incremental 
> /var/lib/amanda/gnutar-lists/server.slsware.dmz_var_2.new --sparse 
> --ignore-failed-read --totals --exclude-from 
> /tmp/amanda/sendbackup._var.20070409010957.exclude .
> sendbackup-gnutar: time 0.027: /usr/lib/amanda/runtar: pid 15175
> sendbackup: time 0.027: started backup
> sendbackup: time 20.677: 118: strange(?): gtar: ./lib/ntop/dnsCache.db: file 
> changed as we read it
> sendbackup: time 29.301:  53:  normal(|): gtar: 
> ./run/postgresql/.s.PGSQL.5432: socket ignored
> sendbackup: time 29.879:  47:    size(|): Total bytes written: 151971840 
> (145MiB, 4.9MiB/s)
> sendbackup: time 29.882: index created successfully
> sendbackup: time 29.883: error [/bin/tar returned 1]
> sendbackup: time 29.883: pid 15171 finish time Mon Apr  9 01:10:27 2007

Why would tar hurl on this? The file change? Is this why the p3 release
of Amanda is necessary? Or is tar bent again?

If it doesn't like the file changing, this looks like something that may
have just happened coincidently the past couple backups. Is that right?

I notice it looking for client config filed. I didn't know there was
such a thing. Would it be possible to fix this problem in a client config?

> Which tar release? (tar --version)
> If it's tar 1.16, you need amanda-2.5.1p3

It's 1.16. I've been taking the Debian update binaries. Maybe I need to
file a bug with Debian's Amanda maintainer??

Thanks very much.

- --
Glenn English
ghe AT slsware DOT com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGG7Cl04yQfZbbTLYRAmcMAJ421L1Ixm+EoCpLr+yc5GHpkqKUpgCfSM9k
RjulzF7IQONtQhFlVto9IEg=
=gBkR
-----END PGP SIGNATURE-----