Re: amanda backup hanging consistently

[Orion Poplawski]

On 6/17/22 04:25, Jose M Calhariz wrote:

Hi,


If you run tar by hand on the DLE does it finish?  After how much time?


Thanks for the suggestion.  That made me notice that it was bogging down 
dealing with a *very* deep directory that had been created by a buggy 
process going into infinite recursion.  Removing that appears to have 
fixed the dump.


Still seems like there is an issue with amanda not cleaning up properly 
from the timeout condition though.




On Wed, Jun 15, 2022 at 09:50:11AM -0600, Orion Poplawski wrote:

On 6/15/22 09:38, Orion Poplawski wrote:

Recently the backup of a particular DLE has started hanging consistently.  I
don't see any recent changes on the server except possibly a change from
kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
problem didn't start until June 6th.

The tar command is stuck trying to write out the name of the directory to 
amgtar:

root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .

# strace -f -s 500 -p 11321
strace: Process 11321 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

# strace -f -s 500 -p 11432
strace: Process 11432 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

amgtar is stuck writing output to amandad:

# strace -s 200 -p 11427
strace: Process 11427 attached
write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
2022-05-23 17:31
./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096


amgtar debug has:

Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
/bin/tar
Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
/var/lib/amanda/gnutar-lists
Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM no
Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
bytes written: [0-9][0-9]*
Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
Directory is new$
Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
Directory has been renamed
Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
open conf file
Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
time:
Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL ^Throughput
Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
directory is on a different filesystem; not dumped
Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
ignored$
Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
shrunk by [0-9][0-9]* bytes, padding with zeros
Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
add file .*: No such file or directory$
Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
exit delayed from previous errors
Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: error
Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
"/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
/bin/tar '--version'
Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar   : Spawning
"/usr/bin/tar 

Re: amanda backup hanging consistently

[Jose M Calhariz]

Hi,


If you run tar by hand on the DLE does it finish?  After how much time?

Kind regards
Jose M Calhariz


On Wed, Jun 15, 2022 at 09:50:11AM -0600, Orion Poplawski wrote:
> On 6/15/22 09:38, Orion Poplawski wrote:
> > Recently the backup of a particular DLE has started hanging consistently.  I
> > don't see any recent changes on the server except possibly a change from
> > kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
> > problem didn't start until June 6th.
> > 
> > The tar command is stuck trying to write out the name of the directory to 
> > amgtar:
> > 
> > root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
> > --verbose --verbose --block-number --file - --directory 
> > /export/backup/rufous
> > --no-check-device --listed-incremental
> > /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> > --ignore-failed-read --totals --exclude-from
> > /var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
> > root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
> > --verbose --verbose --block-number --file - --directory 
> > /export/backup/rufous
> > --no-check-device --listed-incremental
> > /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> > --ignore-failed-read --totals --exclude-from
> > /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .
> > 
> > # strace -f -s 500 -p 11321
> > strace: Process 11321 attached
> > write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> > 
> > # strace -f -s 500 -p 11432
> > strace: Process 11432 attached
> > write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> > 
> > amgtar is stuck writing output to amandad:
> > 
> > # strace -s 200 -p 11427
> > strace: Process 11427 attached
> > write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
> > 2022-05-23 17:31
> > ./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
> > orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096
> > 
> > 
> > amgtar debug has:
> > 
> > Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid > > 0
> > euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
> > Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
> > Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 
> > 156
> > Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid > > 0
> > euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
> > Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
> > /bin/tar
> > Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
> > /var/lib/amanda/gnutar-lists
> > Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : 
> > ONE-FILE-SYSTEM no
> > Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
> > Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
> > Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE 
> > no
> > Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
> > Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
> > Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
> > Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
> > Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
> > bytes written: [0-9][0-9]*
> > Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
> > Directory is new$
> > Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
> > Directory has been renamed
> > Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could 
> > not
> > open conf file
> > Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL 
> > ^Elapsed time:
> > Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL 
> > ^Throughput
> > Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
> > directory is on a different filesystem; not dumped
> > Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
> > ignored$
> > Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File 
> > .*
> > shrunk by [0-9][0-9]* bytes, padding with zeros
> > Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
> > add file .*: No such file or directory$
> > Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
> > exit delayed from previous errors
> > Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: 
> > error
> > Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
> > "/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
> > Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
> > /bin/tar '--version'
> > Tue Jun 14 23:47:14.126144343 2022: pid 11427: 

Re: amanda backup hanging consistently

[Orion Poplawski]

On 6/15/22 09:38, Orion Poplawski wrote:
> Recently the backup of a particular DLE has started hanging consistently.  I
> don't see any recent changes on the server except possibly a change from
> kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
> problem didn't start until June 6th.
> 
> The tar command is stuck trying to write out the name of the directory to 
> amgtar:
> 
> root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
> --verbose --verbose --block-number --file - --directory /export/backup/rufous
> --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
> root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
> --verbose --verbose --block-number --file - --directory /export/backup/rufous
> --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .
> 
> # strace -f -s 500 -p 11321
> strace: Process 11321 attached
> write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> 
> # strace -f -s 500 -p 11432
> strace: Process 11432 attached
> write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> 
> amgtar is stuck writing output to amandad:
> 
> # strace -s 200 -p 11427
> strace: Process 11427 attached
> write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
> 2022-05-23 17:31
> ./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
> orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096
> 
> 
> amgtar debug has:
> 
> Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
> euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
> Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
> Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
> Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
> euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
> Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
> /bin/tar
> Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
> /var/lib/amanda/gnutar-lists
> Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM 
> no
> Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
> Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
> Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
> Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
> Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
> Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
> Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
> Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
> bytes written: [0-9][0-9]*
> Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
> Directory is new$
> Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
> Directory has been renamed
> Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
> open conf file
> Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
> time:
> Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL 
> ^Throughput
> Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
> directory is on a different filesystem; not dumped
> Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
> ignored$
> Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
> shrunk by [0-9][0-9]* bytes, padding with zeros
> Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
> add file .*: No such file or directory$
> Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
> exit delayed from previous errors
> Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: 
> error
> Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
> "/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
> Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
> /bin/tar '--version'
> Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar   : Spawning
> "/usr/bin/tar /usr/bin/tar --create --verbose --verbose --block-number --file
> - --directory /export/backup/rufous --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude ." in 
> pipeline
> 
> amandad debug has:

amanda backup hanging consistently

[Orion Poplawski]

Recently the backup of a particular DLE has started hanging consistently.  I
don't see any recent changes on the server except possibly a change from
kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
problem didn't start until June 6th.

The tar command is stuck trying to write out the name of the directory to 
amgtar:

root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .

# strace -f -s 500 -p 11321
strace: Process 11321 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

# strace -f -s 500 -p 11432
strace: Process 11432 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

amgtar is stuck writing output to amandad:

# strace -s 200 -p 11427
strace: Process 11427 attached
write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
2022-05-23 17:31
./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096


amgtar debug has:

Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
/bin/tar
Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
/var/lib/amanda/gnutar-lists
Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM no
Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
bytes written: [0-9][0-9]*
Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
Directory is new$
Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
Directory has been renamed
Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
open conf file
Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
time:
Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL ^Throughput
Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
directory is on a different filesystem; not dumped
Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
ignored$
Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
shrunk by [0-9][0-9]* bytes, padding with zeros
Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
add file .*: No such file or directory$
Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
exit delayed from previous errors
Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: error
Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
"/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
/bin/tar '--version'
Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar   : Spawning
"/usr/bin/tar /usr/bin/tar --create --verbose --verbose --block-number --file
- --directory /export/backup/rufous --no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude ." in 
pipeline

amandad debug has:

Tue Jun 14 23:47:14.049156625 2022: pid 11417: ??-amandad   : sending REP pkt:
<
CONNECT DATA 49 MESG 48 INDEX 47 STATE 46
OPTIONS features=9efefbfff3fffbf79f00;
>
Tue Jun 14 

Re: amanda-backup, can't remove "backup" from names used

[Chris Hassell]

TOP NOTES:

Make a build and the .deb files.


  1.  Maybe remove the 'amanda' or 'amandabackup' user and its home directories 
(any).  Remove it from the /etc/passwd as well.  The /var/lib/amanda is the 
*normal* home directory but has no config in there.. so it should go too.
  2.  Don't add it back ... or if you must add it (if you know its UID was set 
to 63998 as is the necessary default) use:

$ sudo useradd -c "Amanda" -g  -u 63998 -d /var/lib/amanda -s 
/bin/bash amanda

  3.  Try installing the packages *then*.

If that doesn't work, remove the packages again and then run this separately 
(if something failed and you're not sure why):

% bash -xv ./packaging/deb/preinst

Not sure.  But that's what *should* succeed and make the user on its own.  You 
may need to check everything *everywhere* in /etc/amanda and /var/log/amanda 
and /var/lib/amanda etc.. etc... is changed over to the new user (because the 
uid# is the *real* presence of a user... not the stringy name).

Use "dpkg -V amanda-backup-server" and I think it'll check the 
ownership/validity of the install.  Remember .. the server has both server and 
client binaries .. so its what you want.

On 5/11/19 9:32 AM, Gene Heskett wrote:

Despite changing the name in the rules file, its hard coded to be
amanda-backup in the .dsc files. GRRR

The .dsc file is (I believe) from the Debian build process.  Whatever user you 
have, it will find one name to describe the file owners.  If you have 
amandabackup and amanda both in your /etc/passwd ... it can pick either one as 
a valid choice.\

I don't run Debian-based at home so I can't tell right now what it looks like.  
I know that if it's changed within every file in packaging/deb/... then it's 
changed for all new builds.  Make sure to run a "git clean -d -f" before a 
build to start clean.

Nothing works if you have the last-used-user spread all hither and yon and 
change it upstream in one place.

Without fixing this, how the hell do we get rid of the older version
trash when updateing it?  Seems like a heck of a good question to me. Do
we expect the users to wear out find in cleaning house file by file?  I
think not.

The only files (in the repo) that mention amandabackup ... are entirely within 
packaging/...

This was amanda for 2 decades before some marketing type decreed a name
change. What was this person thinking?

Confusion.  I've no idea but many names all identical are kind confusing.  Some 
folks *may* even have a young or old lady using a machine named 'amanda'?  
Changes are the norm.  Static stuff is rare... except bugs live there too

Anyway, I blew that whole /home/amanda/amanda directory away an started
with becoming amanda, then a fresh git clone from github.
Then did exactly as said. It builds 5 packages. so I attempt to install
the amanda-backup-server since this machine is the server.

I still don't get that *anything* is good about having the amanda user or 
building-with-amanda.  I'm worried its your problem there?  Take it or leave it 
.. but things haven't worked smoothly yet.

And its stuck, just like the previous attempt.  No cpu used, no progress.
pstree does show but one process, but htop shows 5, with the highest pid
being from gnupg getting a no-permissions from /var/lib/amanda. An ls -l
of that dir is:

What process was it?  (May need to use pstree -phul to see everything).

amanda@coyote:..$<mailto:amanda@coyote:..$> ls -l /var/lib/amanda
total 16
-rw-r--r-- 1 root root 34 May 11 09:59 amanda-release
-rw-r--r-- 1 backup   backup0 May  6 10:51 amandates
drwxr-xr-x 3 amandabackup disk   4096 May 11 11:01 example
drwxrwx--- 2 amandabackup disk   4096 May 11 09:59 gnutar-lists
drwxr-xr-x 2 amandabackup disk   4096 May 11 11:01 template.d

That's amanda's home directory, by default.  One should try running the build 
with no packages installed and no amanda user in place.

And that directory is owned by backup.  And I'm lost, and I need to go
convince a winders 10 home edition that I am indeed boss. I can't even
get it online. Need a manpage for netfs.

Thanks Chris, but its Your turn.

That's all I have for right now.  Some of these pre-post install scripts could 
be more clear and block an install (with a reason why) to help everyone get 
success sometime without guesswork.



Cheers, Gene Heskett

Re: amanda-backup, can't remove "backup" from names used

[Gene Heskett]

a rebase (which can be messy) you can still track
> things by stacking (but tracking) remote changes on your local changes
> and intermingle them like a huge huge dagwood sandwich.  Linear
> history be damned.. cuz coding rarely goes linearly.
>
> I have no apology for the bizarre set of names and terms and invisible
> states it maintains.  It is not easy to learn and an easier GUI
> version like "gitg" or something is far better, if you can because
> it's very hard to visualize in the first two years of use.  Even so,
> things like local changes are good to make and easy to stow away.
>
> Restarting from a "reset --hard " or a nicer "checkout -b
> mineno2 ..." is always possible... but beware as some changes you make
> can be lost.
>
> On 5/11/19 9:32 AM, Gene Heskett wrote:
>
> Despite changing the name in the rules file, its hard coded to be
> amanda-backup in the .dsc files. GRRR
>
> Without fixing this, how the hell do we get rid of the older version
> trash when updateing it?  Seems like a heck of a good question to me.
> Do we expect the users to wear out find in cleaning house file by
> file?  I think not.
>
> This was amanda for 2 decades before some marketing type decreed a
> name change. What was this person thinking?
>
> Anyway, I blew that whole /home/amanda/amanda directory away an
> started with becoming amanda, then a fresh git clone from github.
> Then did exactly as said. It builds 5 packages. so I attempt to
> install the amanda-backup-server since this machine is the server.
>
> And its stuck, just like the previous attempt.  No cpu used, no
> progress. pstree does show but one process, but htop shows 5, with the
> highest pid being from gnupg getting a no-permissions from
> /var/lib/amanda. An ls -l of that dir is:
>
> amanda@coyote:..$<mailto:amanda@coyote:..$> ls -l /var/lib/amanda
> total 16
> -rw-r--r-- 1 root root 34 May 11 09:59 amanda-release
> -rw-r--r-- 1 backup   backup0 May  6 10:51 amandates
> drwxr-xr-x 3 amandabackup disk   4096 May 11 11:01 example
> drwxrwx--- 2 amandabackup disk   4096 May 11 09:59 gnutar-lists
> drwxr-xr-x 2 amandabackup disk   4096 May 11 11:01 template.d
>
No comment of this?

> And that directory is owned by backup.  And I'm lost, and I need to go
> convince a winders 10 home edition that I am indeed boss. I can't even
> get it online. Need a manpage for netfs.
>
> Thanks Chris, but its Your turn.
>
> Cheers, Gene Heskett



Copyright 2019 by Maurice E. Heskett
Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: amanda-backup, can't remove "backup" from names used

[Chris Hassell]

cal changes are good to make 
and easy to stow away.

Restarting from a "reset --hard " or a nicer "checkout -b mineno2 
..." is always possible... but beware as some changes you make can be lost.

On 5/11/19 9:32 AM, Gene Heskett wrote:

Despite changing the name in the rules file, its hard coded to be
amanda-backup in the .dsc files. GRRR

Without fixing this, how the hell do we get rid of the older version
trash when updateing it?  Seems like a heck of a good question to me. Do
we expect the users to wear out find in cleaning house file by file?  I
think not.

This was amanda for 2 decades before some marketing type decreed a name
change. What was this person thinking?

Anyway, I blew that whole /home/amanda/amanda directory away an started
with becoming amanda, then a fresh git clone from github.
Then did exactly as said. It builds 5 packages. so I attempt to install
the amanda-backup-server since this machine is the server.

And its stuck, just like the previous attempt.  No cpu used, no progress.
pstree does show but one process, but htop shows 5, with the highest pid
being from gnupg getting a no-permissions from /var/lib/amanda. An ls -l
of that dir is:

amanda@coyote:..$<mailto:amanda@coyote:..$> ls -l /var/lib/amanda
total 16
-rw-r--r-- 1 root root 34 May 11 09:59 amanda-release
-rw-r--r-- 1 backup   backup0 May  6 10:51 amandates
drwxr-xr-x 3 amandabackup disk   4096 May 11 11:01 example
drwxrwx--- 2 amandabackup disk   4096 May 11 09:59 gnutar-lists
drwxr-xr-x 2 amandabackup disk   4096 May 11 11:01 template.d

And that directory is owned by backup.  And I'm lost, and I need to go
convince a winders 10 home edition that I am indeed boss. I can't even
get it online. Need a manpage for netfs.

Thanks Chris, but its Your turn.

Cheers, Gene Heskett

amanda-backup, can't remove "backup" from names used

[Gene Heskett]

Despite changing the name in the rules file, its hard coded to be 
amanda-backup in the .dsc files. GRRR

Without fixing this, how the hell do we get rid of the older version 
trash when updateing it?  Seems like a heck of a good question to me. Do 
we expect the users to wear out find in cleaning house file by file?  I 
think not.

This was amanda for 2 decades before some marketing type decreed a name 
change. What was this person thinking?

Anyway, I blew that whole /home/amanda/amanda directory away an started 
with becoming amanda, then a fresh git clone from github.
Then did exactly as said. It builds 5 packages. so I attempt to install 
the amanda-backup-server since this machine is the server.

And its stuck, just like the previous attempt.  No cpu used, no progress. 
pstree does show but one process, but htop shows 5, with the highest pid 
being from gnupg getting a no-permissions from /var/lib/amanda. An ls -l 
of that dir is:

amanda@coyote:..$ ls -l /var/lib/amanda
total 16
-rw-r--r-- 1 root root 34 May 11 09:59 amanda-release
-rw-r--r-- 1 backup   backup0 May  6 10:51 amandates
drwxr-xr-x 3 amandabackup disk   4096 May 11 11:01 example
drwxrwx--- 2 amandabackup disk   4096 May 11 09:59 gnutar-lists
drwxr-xr-x 2 amandabackup disk   4096 May 11 11:01 template.d

And that directory is owned by backup.  And I'm lost, and I need to go 
convince a winders 10 home edition that I am indeed boss. I can't even 
get it online. Need a manpage for netfs.

Thanks Chris, but its Your turn.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: Fw: amanda backup fails, because of wrong suid settings

[Jean-Louis Martineau]

Read the ReleaseNotes and we will find that suid have changed in 3.5


Le lun. 10 déc. 2018, à 16 h 35, Charles Stroom 
a écrit :

> Sorry, but below replace "sticky bit" by "suid bit".
>
> Charles
>
> Begin forwarded message:
>
> Date: Mon, 10 Dec 2018 21:10:36 +0100
> From: Charles Stroom 
> To: amanda-users@amanda.org
> Subject: amanda backup fails, because of wrong suid settings
>
>
> Hi all,
>
> This is on Linux Opensuse 42.3 with amanda 3.5.1 compiled from tar
> file. Today I discovered that amcheck failed to run, while during the
> last backup on 2018-12-06 there were no problems with amcheck and
> the subsequent amdump.  But today I got:
> 
> From: "(Cron Daemon)" 
> To: root@fiume7.localnet
> Subject: Cron  amcheck -a daily_lto2
> Date: Mon, 10 Dec 2018 17:52:01 +0100 (CET)
>
>
> ** (process:16780): CRITICAL **: amcheck must not be setuid (0, 37)
> 
>
> Odd, but I cleared the sticky bit, and then amcheck produced a normal
> output and reported 0 errors.
>
> However, the subsequent amdump failed:
> 
> From: amanda@fiume7.localnet (Amanda Backup)
> To: root@fiume7.localnet
> Subject: daily_backup FAIL: AMANDA MAIL REPORT FOR ? 2, 0
> Date: Mon, 10 Dec 2018 18:29:02 +0100
> User-Agent: Heirloom mailx 12.5 7/5/10
>
> *** THE DUMPS DID NOT FINISH PROPERLY!
>
> Org : daily_backup
> Config  : daily_lto2
> Date: ? 2, 0
>
>
>
> FAILURE DUMP SUMMARY:
>   driver: FATAL Did not get DATE line from planner
>
>
> STATISTICS:
>   Total   Full  Incr.   Level:#
>         
> Estimate Time (hrs:min) 0:00
> Run Time (hrs:min)  0:00
> Dump Time (hrs:min) 0:00   0:00   0:00
> Output Size (meg)0.00.00.0
> Original Size (meg)  0.00.00.0
> Avg Compressed Size (%)  -- -- --
> DLEs Dumped0  0  0
> Avg Dump Rate (k/s)  -- -- --
>
> Tape Time (hrs:min) 0:00   0:00   0:00
> Tape Size (meg)  0.00.00.0
> Tape Used (%)0.00.00.0
> DLEs Taped 0  0  0
> Parts Taped0  0  0
> Avg Tp Write Rate (k/s)  -- -- --
>
>
> DUMP SUMMARY:
>DUMPER STATS   TAPER
> STATS
> HOSTNAME DISKL ORIG-KB  OUT-KB  COMP%  MMM:SS   KB/s
> MMM:SS   KB/s -- --
> ---
>
> (brought to you by Amanda version 3.5.1)
> 
>
> and when I looked at the amdump.1 file it seemed like a similar uid
> problem: 
> amdump: start at Mon Dec 10 18:31:40 CET 2018
> amdump: datestamp 20181210
> amdump: starttime 20181210183140
> amdump: starttime-locale-independent 2018-12-10 18:31:40 CET
>
> ** (process:18834): CRITICAL **: planner must not be setuid root
> driver: pid 18835 executable /usr/lib/amanda/driver version 3.5.1
> driver: Did not get DATE line from planner
> amdump: end at Mon Dec 10 18:31:40 CET 2018
> /var/log/amanda/daily_lto2/amdump.1 (END)
> 
>
> Now I got suspicious, because there were no problems a few days ago and
> suddenly all this sticky bit business.  Has my system been tampered
> with? I then compared the file modes of my current amanda installation
> with my installation in my previous version of opensuse (42.1, same
> 3.5.1 version) and found that indeed in 42.1 amcheck did not have a
> sticky bit set (??), but planner (and a couple)
> of other amanda programs in /usr/lib/amanda do have sticky bits set.
>
> Of course I can take the sticky bit of planner away, but I would like
> to have an opinion of the more knowledgeable forum.  Could there be
> another reason why all of a sudden there are these problems?
>
> Many thanks,
>
> Charles
>
>
>
>
>
>
> --
> Charles Stroom
> email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.")
>
>
> --
> Charles Stroom
> email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.")
>

amanda backup fails

[Gene Heskett]

On Monday 10 December 2018 18:04:47 Elias Pereira wrote:

> Hello Helge,
>
> Thanks for the answer!!!
>
> In my cups webgui does not have that tiny triangle!!! Can you show me
> with a printscreen?
>
> On Mon, Dec 10, 2018 at 3:13 PM Helge Blischke  
wrote:
> > > Am 10.12.2018 um 17:35 schrieb Elias Pereira :
> > >
> > > Hello,
> > >
> > > How do I config cups webgui to display the jobs in ascending order
> >
> > (Newest
> >
> > > to Oldest)?
> > >
> > > --
> > > Elias Pereira
> >
> > Klick on one of the tiny triangles besides the "ID“ in the title
> > line.
> >
> > Helge
> >
Normally you build amanda in the /home/amanda directory, sudo -i,
then su amanda. Then when its built, ctrl-D out of amanda and make 
install as root, then your perms are all as they should be. I have a 
configure driver file to configure and build, and It won't do a thing if 
I'm root.  Thats a bad dog, no biscuit if not the user amanda.

The script:

#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo "!! Warning !!!"
echo "Amanda needs to be configured and built by the"
echo "user amanda, but must be installed by user root."
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-gnu-ld \
--prefix=/usr/local/ \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=coyote \
--with-bsdtcp-security --with-amandahosts \
--with-configdir=/usr/local/etc/amanda \
--enable-manpage-build  \
--with-readline \
--with-gnutar=/bin/tar \
--with-security-file=/etc/amanda-security.conf \
--with-amandates-file=/etc/amandates
echo "sleeping for reading configures warnings"
echo "a make as amanda will continue after 75 seconds..."
sleep 75
make




> > ___
> > cups mailing list
> > c...@cups.org
> > https://lists.cups.org/mailman/listinfo/cups



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Fw: amanda backup fails, because of wrong suid settings

[Charles Stroom]

Sorry, but below replace "sticky bit" by "suid bit".

Charles

Begin forwarded message:

Date: Mon, 10 Dec 2018 21:10:36 +0100
From: Charles Stroom 
To: amanda-users@amanda.org
Subject: amanda backup fails, because of wrong suid settings


Hi all,

This is on Linux Opensuse 42.3 with amanda 3.5.1 compiled from tar
file. Today I discovered that amcheck failed to run, while during the
last backup on 2018-12-06 there were no problems with amcheck and
the subsequent amdump.  But today I got:

From: "(Cron Daemon)" 
To: root@fiume7.localnet
Subject: Cron  amcheck -a daily_lto2
Date: Mon, 10 Dec 2018 17:52:01 +0100 (CET)


** (process:16780): CRITICAL **: amcheck must not be setuid (0, 37)


Odd, but I cleared the sticky bit, and then amcheck produced a normal
output and reported 0 errors.

However, the subsequent amdump failed:

From: amanda@fiume7.localnet (Amanda Backup)
To: root@fiume7.localnet
Subject: daily_backup FAIL: AMANDA MAIL REPORT FOR ? 2, 0
Date: Mon, 10 Dec 2018 18:29:02 +0100
User-Agent: Heirloom mailx 12.5 7/5/10

*** THE DUMPS DID NOT FINISH PROPERLY!

Org : daily_backup
Config  : daily_lto2
Date: ? 2, 0



FAILURE DUMP SUMMARY:
  driver: FATAL Did not get DATE line from planner


STATISTICS:
  Total   Full  Incr.   Level:#
        
Estimate Time (hrs:min) 0:00
Run Time (hrs:min)  0:00
Dump Time (hrs:min) 0:00   0:00   0:00
Output Size (meg)0.00.00.0
Original Size (meg)  0.00.00.0
Avg Compressed Size (%)  -- -- --
DLEs Dumped0  0  0
Avg Dump Rate (k/s)  -- -- --

Tape Time (hrs:min) 0:00   0:00   0:00
Tape Size (meg)  0.00.00.0
Tape Used (%)0.00.00.0
DLEs Taped 0  0  0
Parts Taped0  0  0
Avg Tp Write Rate (k/s)  -- -- --


DUMP SUMMARY:
   DUMPER STATS   TAPER
STATS
HOSTNAME DISKL ORIG-KB  OUT-KB  COMP%  MMM:SS   KB/s
MMM:SS   KB/s -- --
---

(brought to you by Amanda version 3.5.1)


and when I looked at the amdump.1 file it seemed like a similar uid
problem: 
amdump: start at Mon Dec 10 18:31:40 CET 2018
amdump: datestamp 20181210
amdump: starttime 20181210183140
amdump: starttime-locale-independent 2018-12-10 18:31:40 CET

** (process:18834): CRITICAL **: planner must not be setuid root
driver: pid 18835 executable /usr/lib/amanda/driver version 3.5.1
driver: Did not get DATE line from planner
amdump: end at Mon Dec 10 18:31:40 CET 2018
/var/log/amanda/daily_lto2/amdump.1 (END)


Now I got suspicious, because there were no problems a few days ago and
suddenly all this sticky bit business.  Has my system been tampered
with? I then compared the file modes of my current amanda installation
with my installation in my previous version of opensuse (42.1, same
3.5.1 version) and found that indeed in 42.1 amcheck did not have a
sticky bit set (??), but planner (and a couple)
of other amanda programs in /usr/lib/amanda do have sticky bits set.

Of course I can take the sticky bit of planner away, but I would like
to have an opinion of the more knowledgeable forum.  Could there be
another reason why all of a sudden there are these problems?

Many thanks,

Charles






-- 
Charles Stroom
email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.")


-- 
Charles Stroom
email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.")

amanda backup fails, because of wrong suid settings

[Charles Stroom]

Hi all,

This is on Linux Opensuse 42.3 with amanda 3.5.1 compiled from tar file.  
Today I discovered that amcheck failed to run, while during the last
backup on 2018-12-06 there were no problems with amcheck and
the subsequent amdump.  But today I got:

From: "(Cron Daemon)" 
To: root@fiume7.localnet
Subject: Cron  amcheck -a daily_lto2
Date: Mon, 10 Dec 2018 17:52:01 +0100 (CET)


** (process:16780): CRITICAL **: amcheck must not be setuid (0, 37)


Odd, but I cleared the sticky bit, and then amcheck produced a normal
output and reported 0 errors.

However, the subsequent amdump failed:

From: amanda@fiume7.localnet (Amanda Backup)
To: root@fiume7.localnet
Subject: daily_backup FAIL: AMANDA MAIL REPORT FOR ? 2, 0
Date: Mon, 10 Dec 2018 18:29:02 +0100
User-Agent: Heirloom mailx 12.5 7/5/10

*** THE DUMPS DID NOT FINISH PROPERLY!

Org : daily_backup
Config  : daily_lto2
Date: ? 2, 0



FAILURE DUMP SUMMARY:
  driver: FATAL Did not get DATE line from planner


STATISTICS:
  Total   Full  Incr.   Level:#
        
Estimate Time (hrs:min) 0:00
Run Time (hrs:min)  0:00
Dump Time (hrs:min) 0:00   0:00   0:00
Output Size (meg)0.00.00.0
Original Size (meg)  0.00.00.0
Avg Compressed Size (%)  -- -- --
DLEs Dumped0  0  0
Avg Dump Rate (k/s)  -- -- --

Tape Time (hrs:min) 0:00   0:00   0:00
Tape Size (meg)  0.00.00.0
Tape Used (%)0.00.00.0
DLEs Taped 0  0  0
Parts Taped0  0  0
Avg Tp Write Rate (k/s)  -- -- --


DUMP SUMMARY:
   DUMPER STATS   TAPER
STATS
HOSTNAME DISKL ORIG-KB  OUT-KB  COMP%  MMM:SS   KB/s MMM:SS   KB/s
-- -- ---

(brought to you by Amanda version 3.5.1)


and when I looked at the amdump.1 file it seemed like a similar uid problem:

amdump: start at Mon Dec 10 18:31:40 CET 2018
amdump: datestamp 20181210
amdump: starttime 20181210183140
amdump: starttime-locale-independent 2018-12-10 18:31:40 CET

** (process:18834): CRITICAL **: planner must not be setuid root
driver: pid 18835 executable /usr/lib/amanda/driver version 3.5.1
driver: Did not get DATE line from planner
amdump: end at Mon Dec 10 18:31:40 CET 2018
/var/log/amanda/daily_lto2/amdump.1 (END)


Now I got suspicious, because there were no problems a few days ago and
suddenly all this sticky bit business.  Has my system been tampered with?
I then compared the file modes of my current amanda installation
with my installation in my previous version of opensuse (42.1, same
3.5.1 version) and found that indeed in 42.1 amcheck did not have a
sticky bit set (??), but planner (and a couple)
of other amanda programs in /usr/lib/amanda do have sticky bits set.

Of course I can take the sticky bit of planner away, but I would like
to have an opinion of the more knowledgeable forum.  Could there be
another reason why all of a sudden there are these problems?

Many thanks,

Charles






-- 
Charles Stroom
email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.")

Re: Patches used by Debian on amanda -- "backup" user under Debian

[Charles Curley]

On Mon, 9 Jan 2017 14:21:00 -0500
Nathan Stratton Treadway  wrote:

> On Sun, Jan 08, 2017 at 12:51:45 -0700, Charles Curley wrote:
> > May I request you end two irritants about the Debian version. It
> > creates a user, "backup". That's fine, although "amanda", say,
> > would avoid stepping on some other user named "backup".


> 
> For what it's worth, the "backup" user (uid 34) -- including its home
> directory and login shell settings -- is actually defined on all
> Debian systems as part of the base-passwd package (and thus exist
> completely separately from the Amanda packages).
> 
> See, for example:
>   
> https://anonscm.debian.org/cgit/users/cjwatson/base-passwd.git/tree/passwd.master
>   https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2.2
>  (_Debian Policy Manual_ "9.2.2 UID and GID classes")

I stand corrected, thank you.

> 
> 
> I've always figured that whoever did the original Debian packaging for
> the Amanda software (years ago) decided it would be easier to make use
> of that pre-existing user rather than having to have the package
> installation scripts manage creation (and deletion) of a separate
> "amanda" user

My conjecture also.

The culprits also did not anticipate amanda over ssh, or possibly
other tools like amcheck, and so the need to use the amanda account
interactively.

> 
> Interestingly, /usr/share/doc/base-passwd/users-and-groups.txt.gz
> doesn't seem to know what the "backup" user is for, either:
>   backup
> 
> Presumably so backup/restore responsibilities can be locally
> delegated to someone without full root permissions?
> 
> HELP: Is that right? Amanda reportedly uses this, details?
> 
>  so I suspect that this user was "allocated" in the early mists of
> time for the Debian project, and since then has mostly or completely
> fallen out of use -- except for the use by the Amanda packages

Yep. Except that something, probably the update-passwd tool, appears to
still use it.

-- 

The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Re: Patches used by Debian on amanda -- "backup" user under Debian

[Jean-Louis Martineau]

Steve,

The amanda-client can be run with any user.
The user is compiled in, but it doesn't need to be the same on the 
amanda server and amanda-client.

What was the problem?

Jean-Louis

On 09/01/17 02:41 PM, Steve Wray wrote:
For what its worth, this creates problems with inter-operability 
between CentOS and Debian; we rebuilt the CentOS rpm for amanda client 
so it used the backup user instead of amanda, as our amanda server was 
on Debian. We tried hard but never found a way to configure this.


It would be nice to be able to configure this and not have to have it 
compiled in.



On Mon, Jan 9, 2017 at 11:21 AM, Nathan Stratton Treadway 
> wrote:


On Sun, Jan 08, 2017 at 12:51:45 -0700, Charles Curley wrote:
> May I request you end two irritants about the Debian version. It
creates
> a user, "backup". That's fine, although "amanda", say, would avoid
> stepping on some other user named "backup".
>
> The irritant is that debian makes the user's home
> directory /var/backups. Something else uses that directory, and
I don't
> like co-mingling the two different functions. It also sets the user
> shell to "/usr/sbin/nologin" rather than to bash, which is an
irritant
> on the way to using amanda over ssh.
>

For what it's worth, the "backup" user (uid 34) -- including its home
directory and login shell settings -- is actually defined on all
Debian
systems as part of the base-passwd package (and thus exist completely
separately from the Amanda packages).

See, for example:

https://anonscm.debian.org/cgit/users/cjwatson/base-passwd.git/tree/passwd.master


https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2.2

 (_Debian Policy Manual_ "9.2.2 UID and GID classes")


I've always figured that whoever did the original Debian packaging for
the Amanda software (years ago) decided it would be easier to make use
of that pre-existing user rather than having to have the package
installation scripts manage creation (and deletion) of a separate
"amanda" user

Interestingly, /usr/share/doc/base-passwd/users-and-groups.txt.gz
doesn't
seem to know what the "backup" user is for, either:
  backup

Presumably so backup/restore responsibilities can be locally
delegated to
someone without full root permissions?

HELP: Is that right? Amanda reportedly uses this, details?

 so I suspect that this user was "allocated" in the early mists of
time for the Debian project, and since then has mostly or completely
fallen out of use -- except for the use by the Amanda packages


Nathan


Nathan Stratton Treadway  - natha...@ontko.com
 -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -
http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt
  ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239




Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast Ltd, an innovator in Software as a Service 
(SaaS) for business. Providing a safer and more useful place for your human 
generated data. Specializing in; Security, archiving and compliance. To find 
out more visit the Mimecast website.

Re: Patches used by Debian on amanda -- "backup" user under Debian

[Steve Wray]

For what its worth, this creates problems with inter-operability between
CentOS and Debian; we rebuilt the CentOS rpm for amanda client so it used
the backup user instead of amanda, as our amanda server was on Debian. We
tried hard but never found a way to configure this.

It would be nice to be able to configure this and not have to have it
compiled in.


On Mon, Jan 9, 2017 at 11:21 AM, Nathan Stratton Treadway <
natha...@ontko.com> wrote:

> On Sun, Jan 08, 2017 at 12:51:45 -0700, Charles Curley wrote:
> > May I request you end two irritants about the Debian version. It creates
> > a user, "backup". That's fine, although "amanda", say, would avoid
> > stepping on some other user named "backup".
> >
> > The irritant is that debian makes the user's home
> > directory /var/backups. Something else uses that directory, and I don't
> > like co-mingling the two different functions. It also sets the user
> > shell to "/usr/sbin/nologin" rather than to bash, which is an irritant
> > on the way to using amanda over ssh.
> >
>
> For what it's worth, the "backup" user (uid 34) -- including its home
> directory and login shell settings -- is actually defined on all Debian
> systems as part of the base-passwd package (and thus exist completely
> separately from the Amanda packages).
>
> See, for example:
>   https://anonscm.debian.org/cgit/users/cjwatson/base-
> passwd.git/tree/passwd.master
>   https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2.2
>  (_Debian Policy Manual_ "9.2.2 UID and GID classes")
>
>
> I've always figured that whoever did the original Debian packaging for
> the Amanda software (years ago) decided it would be easier to make use
> of that pre-existing user rather than having to have the package
> installation scripts manage creation (and deletion) of a separate
> "amanda" user
>
> Interestingly, /usr/share/doc/base-passwd/users-and-groups.txt.gz doesn't
> seem to know what the "backup" user is for, either:
>   backup
>
> Presumably so backup/restore responsibilities can be locally delegated
> to
> someone without full root permissions?
>
> HELP: Is that right? Amanda reportedly uses this, details?
>
>  so I suspect that this user was "allocated" in the early mists of
> time for the Debian project, and since then has mostly or completely
> fallen out of use -- except for the use by the Amanda packages
>
>
> Nathan
>
> 
> 
> Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
> Ray Ontko & Co.  -  Software consulting services  -
> http://www.ontko.com/
>  GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
>  Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239
>

Re: Patches used by Debian on amanda -- "backup" user under Debian

[Nathan Stratton Treadway]

On Sun, Jan 08, 2017 at 12:51:45 -0700, Charles Curley wrote:
> May I request you end two irritants about the Debian version. It creates
> a user, "backup". That's fine, although "amanda", say, would avoid
> stepping on some other user named "backup".
> 
> The irritant is that debian makes the user's home
> directory /var/backups. Something else uses that directory, and I don't
> like co-mingling the two different functions. It also sets the user
> shell to "/usr/sbin/nologin" rather than to bash, which is an irritant
> on the way to using amanda over ssh.
> 

For what it's worth, the "backup" user (uid 34) -- including its home
directory and login shell settings -- is actually defined on all Debian
systems as part of the base-passwd package (and thus exist completely
separately from the Amanda packages).

See, for example:
  
https://anonscm.debian.org/cgit/users/cjwatson/base-passwd.git/tree/passwd.master
  https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2.2
 (_Debian Policy Manual_ "9.2.2 UID and GID classes")


I've always figured that whoever did the original Debian packaging for
the Amanda software (years ago) decided it would be easier to make use
of that pre-existing user rather than having to have the package
installation scripts manage creation (and deletion) of a separate
"amanda" user

Interestingly, /usr/share/doc/base-passwd/users-and-groups.txt.gz doesn't
seem to know what the "backup" user is for, either:
  backup

Presumably so backup/restore responsibilities can be locally delegated to
someone without full root permissions?

HELP: Is that right? Amanda reportedly uses this, details?

 so I suspect that this user was "allocated" in the early mists of
time for the Debian project, and since then has mostly or completely
fallen out of use -- except for the use by the Amanda packages


Nathan


Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

Greeting Jean-Louis;

Trying to figure out why amanda can't backup this machine, one of the 
things I noticed in /etc, is that on the shop box, which works, there is 
not an /etc/xinetd.d but it has an old-xinetd.d with a single stanza 
amanda file in it.

An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently 
accessed a few minutes ago by my amcheck from the server.

However, on the new install on the machine that is failing to allow the 
connection, there is an /etc/xinet.d, with an amanda file in it with an 
old last access date/time, was not 'touched' when I ran the amcheck.  Its  
last access date/time is I believe, the date/time of the installation 
itself.

That amanda-common is 2.6.1p1 IIRC.

amcheck says:
WARNING: lathe: selfcheck request failed: Connection refused

There has been enough configuration done that amrecover on this machine 
works.

There is a /var/backups/.amandahosts file, its a link to /etc/amandahosts
BUT, in /etc/.amandahosts.  I'll mv it to /etc/amandahosts. Ran amcheck, 
no change and that file was not accessed.

What do I check next?  

Thank you.
 
Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[John Hein]

Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
  Trying to figure out why amanda can't backup this machine, one of the
  things I noticed in /etc, is that on the shop box, which works, there is
  not an /etc/xinetd.d but it has an old-xinetd.d with a single stanza
  amanda file in it.
 
  An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
  accessed a few minutes ago by my amcheck from the server.
 
  However, on the new install on the machine that is failing to allow the
  connection, there is an /etc/xinet.d, with an amanda file in it with an
  old last access date/time, was not 'touched' when I ran the amcheck.  Its
  last access date/time is I believe, the date/time of the installation
  itself.
 
  That amanda-common is 2.6.1p1 IIRC.
 
  amcheck says:
  WARNING: lathe: selfcheck request failed: Connection refused

Try running xinetd -d (then amcheck) to see if (or why not) xinetd is
running amandad.

Re: amrecover works, normal amanda backup, logging connection refused

[Olivier Nicole]

Gene,

On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote:
 Greeting Jean-Louis;

 Trying to figure out why amanda can't backup this machine, one of the
 things I noticed in /etc, is that on the shop box, which works, there is
 not an /etc/xinetd.d but it has an old-xinetd.d with a single stanza
 amanda file in it.

 An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
 accessed a few minutes ago by my amcheck from the server.

 However, on the new install on the machine that is failing to allow the
 connection, there is an /etc/xinet.d, with an amanda file in it with an
 old last access date/time, was not 'touched' when I ran the amcheck.  Its
 last access date/time is I believe, the date/time of the installation
 itself.

 That amanda-common is 2.6.1p1 IIRC.

 amcheck says:
 WARNING: lathe: selfcheck request failed: Connection refused

 There has been enough configuration done that amrecover on this machine
 works.

 There is a /var/backups/.amandahosts file, its a link to /etc/amandahosts
 BUT, in /etc/.amandahosts.  I'll mv it to /etc/amandahosts. Ran amcheck,
 no change and that file was not accessed.

 What do I check next?

netstat -na |grep 10080

You should see an UDP open on that port, else it means xinetd is not
running/not listening for amanda.

Olivier



 Thank you.

 Cheers, Gene Heskett
 --
 There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order.
 -Ed Howdershelt (Author)
 Genes Web page http://geneslinuxbox.net:6309/gene
 US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 10:50:47 John Hein did opine
And Gene did reply:
 Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
   Trying to figure out why amanda can't backup this machine, one of
   the things I noticed in /etc, is that on the shop box, which works,
   there is not an /etc/xinetd.d but it has an old-xinetd.d with a
   single stanza amanda file in it.
   
   An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
   accessed a few minutes ago by my amcheck from the server.
   
   However, on the new install on the machine that is failing to allow
   the connection, there is an /etc/xinet.d, with an amanda file in it
   with an old last access date/time, was not 'touched' when I ran the
   amcheck.  Its last access date/time is I believe, the date/time of
   the installation itself.
   
   That amanda-common is 2.6.1p1 IIRC.
   
   amcheck says:
   WARNING: lathe: selfcheck request failed: Connection refused
 
 Try running xinetd -d (then amcheck) to see if (or why not) xinetd is
 running amandad.

Puzzle, first I had to install it!  Then got a report ending here:
Service defaults
Bind = All addresses.
Only from: All sites
No access: No blocked sites
No logging

Service configuration: amanda
id = amanda
flags = IPv4
socket_type = dgram
Protocol (name,number) = (udp,17)
port = 10080
wait = yes
user = 34
group = 34
Groups = yes
PER_SOURCE = -1
Bind = All addresses.
Server = /usr/lib/amanda/amandad
Server argv = amandad -auth=bsd amdump amindexd amidxtaped
Only from: All sites
No access: No blocked sites
No logging

14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started service: amanda
14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} mask_max = 6, 
services_started = 1
14/7/18@11:27:40: NOTICE: 3748 {main} xinetd Version 2.3.14 started with 
libwrap loadavg options compiled in.
14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available service
14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services = 1

But running an amcheck on the server didn't get any further output than 
what you see above.  And got the same results, connection refused.
But I see an auth=bsd, where it should be bsdtcp. Fixed that, restarted 
xinetd, no change in amcheck report, lathe still refused connection. the 
amanda file in xinetd.d wasn't touched.  So we are a bit closer, but no 
biscuit.  Next?

Thank you John.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 11:34:16 Olivier Nicole did opine
And Gene did reply:
 Gene,
 
 On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote:
  Greeting Jean-Louis;
  
  Trying to figure out why amanda can't backup this machine, one of the
  things I noticed in /etc, is that on the shop box, which works, there
  is not an /etc/xinetd.d but it has an old-xinetd.d with a single
  stanza amanda file in it.
  
  An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
  accessed a few minutes ago by my amcheck from the server.
  
  However, on the new install on the machine that is failing to allow
  the connection, there is an /etc/xinet.d, with an amanda file in it
  with an old last access date/time, was not 'touched' when I ran the
  amcheck.  Its last access date/time is I believe, the date/time of
  the installation itself.
  
  That amanda-common is 2.6.1p1 IIRC.
  
  amcheck says:
  WARNING: lathe: selfcheck request failed: Connection refused
  
  There has been enough configuration done that amrecover on this
  machine works.
  
  There is a /var/backups/.amandahosts file, its a link to
  /etc/amandahosts BUT, in /etc/.amandahosts.  I'll mv it to
  /etc/amandahosts. Ran amcheck, no change and that file was not
  accessed.
  
  What do I check next?
 
 netstat -na |grep 10080
 
 You should see an UDP open on that port, else it means xinetd is not
 running/not listening for amanda.
 
 Olivier

gene@lathe:/etc/xinetd.d$ netstat -na |grep 10080
udp0  0 0.0.0.0:10080   0.0.0.0:*  
udp0  0 0.0.0.0:10080   0.0.0.0:*

IIRC thats good.

Next?

Thanks Olivier.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Jean-Louis Martineau]

On 07/18/2014 11:39 AM, Gene Heskett wrote:

On Friday 18 July 2014 10:50:47 John Hein did opine
And Gene did reply:

Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
   Trying to figure out why amanda can't backup this machine, one of
   the things I noticed in /etc, is that on the shop box, which works,
   there is not an /etc/xinetd.d but it has an old-xinetd.d with a
   single stanza amanda file in it.
  
   An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
   accessed a few minutes ago by my amcheck from the server.
  
   However, on the new install on the machine that is failing to allow
   the connection, there is an /etc/xinet.d, with an amanda file in it
   with an old last access date/time, was not 'touched' when I ran the
   amcheck.  Its last access date/time is I believe, the date/time of
   the installation itself.
  
   That amanda-common is 2.6.1p1 IIRC.
  
   amcheck says:
   WARNING: lathe: selfcheck request failed: Connection refused

Try running xinetd -d (then amcheck) to see if (or why not) xinetd is
running amandad.

Puzzle, first I had to install it!  Then got a report ending here:
Service defaults
Bind = All addresses.
Only from: All sites
No access: No blocked sites
No logging

Service configuration: amanda
id = amanda
flags = IPv4
socket_type = dgram
Protocol (name,number) = (udp,17)
port = 10080
wait = yes
user = 34
group = 34
Groups = yes
PER_SOURCE = -1
Bind = All addresses.
Server = /usr/lib/amanda/amandad
Server argv = amandad -auth=bsd amdump amindexd amidxtaped
Only from: All sites
No access: No blocked sites
No logging

14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started service: amanda
14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} mask_max = 6,
services_started = 1
14/7/18@11:27:40: NOTICE: 3748 {main} xinetd Version 2.3.14 started with
libwrap loadavg options compiled in.
14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available service
14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services = 1

But running an amcheck on the server didn't get any further output than
what you see above.  And got the same results, connection refused.
But I see an auth=bsd, where it should be bsdtcp. Fixed that, restarted
xinetd, no change in amcheck report, lathe still refused connection. the
amanda file in xinetd.d wasn't touched.  So we are a bit closer, but no
biscuit.  Next?


If you are using bsdtcp, then you must fix the xinetd file for it.
   socket_type = stream
   protocol= tcp
   wait= no

Re: amrecover works, normal amanda backup, logging connection refused

[Jean-Louis Martineau]

On 07/18/2014 11:43 AM, Gene Heskett wrote:

On Friday 18 July 2014 11:34:16 Olivier Nicole did opine
And Gene did reply:

Gene,

On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote:

Greeting Jean-Louis;

Trying to figure out why amanda can't backup this machine, one of the
things I noticed in /etc, is that on the shop box, which works, there
is not an /etc/xinetd.d but it has an old-xinetd.d with a single
stanza amanda file in it.

An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
accessed a few minutes ago by my amcheck from the server.

However, on the new install on the machine that is failing to allow
the connection, there is an /etc/xinet.d, with an amanda file in it
with an old last access date/time, was not 'touched' when I ran the
amcheck.  Its last access date/time is I believe, the date/time of
the installation itself.

That amanda-common is 2.6.1p1 IIRC.

amcheck says:
WARNING: lathe: selfcheck request failed: Connection refused

There has been enough configuration done that amrecover on this
machine works.

There is a /var/backups/.amandahosts file, its a link to
/etc/amandahosts BUT, in /etc/.amandahosts.  I'll mv it to
/etc/amandahosts. Ran amcheck, no change and that file was not
accessed.

What do I check next?

netstat -na |grep 10080

You should see an UDP open on that port, else it means xinetd is not
running/not listening for amanda.

Olivier

gene@lathe:/etc/xinetd.d$ netstat -na |grep 10080
udp0  0 0.0.0.0:10080   0.0.0.0:*
udp0  0 0.0.0.0:10080   0.0.0.0:*

IIRC thats good.


It's not good, this is for bsd auth, you want to use bsdtcp.


Next?

Thanks Olivier.

Cheers, Gene Heskett

RE: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Joi L. Ellis]

I've been installing Amanda on our network for the past few months and on a 
number of the machines, I noticed that the machine had an /etc/xinetd.d/Amanda 
file, but the xinetd service wasn't installed, openbsd-inetd was, and that one 
reads /etc/inetd.conf.  Amanda-client package installs the config lines for 
both inetd packages, but naturally only one of them will be read by your 
machine.  Depending upon the version of the package you installed, I've seen 
Amanda-client install both, only xinetd, or only openbsd-inetd configs, so your 
machine may be looking at a different inetd config than you expected.

Also check to see if your machine is running iptables or ufw, and if so, do 
'lsmod | grep amanda' and verify that the ip_conntrack_amanda or 
nf_conntrack_amanda module is loaded.  If either firewall is active it is 
probably blocking your ports.

If you have the rules enabled, but the *_conntrack_amanda module isn't loaded 
in the kernel, the amcheck will work but amdump will fail.  (I've just worked 
with another admin here to get Amanda running on a new machine of his and this 
was the problem.)


--
Joi Owen
System Administrator
Pavlov Media, Inc

-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On 
Behalf Of Gene Heskett
Sent: Friday, July 18, 2014 10:39 AM
To: amanda-users@amanda.org
Subject: [BULK] Re: amrecover works, normal amanda backup, logging connection 
refused

On Friday 18 July 2014 10:50:47 John Hein did opine And Gene did reply:
 Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
   Trying to figure out why amanda can't backup this machine, one of  
  the things I noticed in /etc, is that on the shop box, which works,  
  there is not an /etc/xinetd.d but it has an old-xinetd.d with a   
 single stanza amanda file in it.
  
   An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently  
  accessed a few minutes ago by my amcheck from the server.
  
   However, on the new install on the machine that is failing to allow  
  the connection, there is an /etc/xinet.d, with an amanda file in it  
  with an old last access date/time, was not 'touched' when I ran the  
  amcheck.  Its last access date/time is I believe, the date/time of  
  the installation itself.
  
   That amanda-common is 2.6.1p1 IIRC.
  
   amcheck says:
   WARNING: lathe: selfcheck request failed: Connection refused
 
 Try running xinetd -d (then amcheck) to see if (or why not) xinetd is 
 running amandad.

Puzzle, first I had to install it!  Then got a report ending here:
Service defaults
Bind = All addresses.
Only from: All sites
No access: No blocked sites
No logging

Service configuration: amanda
id = amanda
flags = IPv4
socket_type = dgram
Protocol (name,number) = (udp,17)
port = 10080
wait = yes
user = 34
group = 34
Groups = yes
PER_SOURCE = -1
Bind = All addresses.
Server = /usr/lib/amanda/amandad
Server argv = amandad -auth=bsd amdump amindexd amidxtaped
Only from: All sites
No access: No blocked sites
No logging

14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started service: amanda
14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} mask_max = 6, 
services_started = 1
14/7/18@11:27:40: NOTICE: 3748 {main} xinetd Version 2.3.14 started with 
libwrap loadavg options compiled in.
14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available service
14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services = 1

But running an amcheck on the server didn't get any further output than what 
you see above.  And got the same results, connection refused.
But I see an auth=bsd, where it should be bsdtcp. Fixed that, restarted xinetd, 
no change in amcheck report, lathe still refused connection. the amanda file in 
xinetd.d wasn't touched.  So we are a bit closer, but no biscuit.  Next?

Thank you John.

Cheers, Gene Heskett
--
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Charles Curley]

On Fri, 18 Jul 2014 22:34:16 +0700
Olivier Nicole olivier.nic...@cs.ait.ac.th wrote:

  What do I check next?

Firewall?

That's bitten me more than once.

-- 

The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

 
 There is a /var/backups/.amandahosts file, its a link to /etc/amandahosts
 BUT, in /etc/.amandahosts.  I'll mv it to /etc/amandahosts. Ran amcheck, 
 no change and that file was not accessed.
 

The actual file SHOULD have a dot at the beginning of the name.
.amandahosts
I guess if the one amanda USES   (perhaps  /var/backups/.amandahosts   but
I’d bet on the other one)starts with a dot,  then it doesn’t much matter
what that link points to.
 But on the whole,  the file IS supposed to start with a dot.

Deb Baddorf
Fermilab

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 11:53:57 Jean-Louis Martineau did opine
And Gene did reply:
 On 07/18/2014 11:39 AM, Gene Heskett wrote:
  On Friday 18 July 2014 10:50:47 John Hein did opine
  
  And Gene did reply:
  Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
 Trying to figure out why amanda can't backup this machine, one
 of the things I noticed in /etc, is that on the shop box, which
 works, there is not an /etc/xinetd.d but it has an old-xinetd.d
 with a single stanza amanda file in it.
 
 An ls -lau shows that file, /etc/old-xinetd.d/amanda was
 apparently accessed a few minutes ago by my amcheck from the
 server.
 
 However, on the new install on the machine that is failing to
 allow the connection, there is an /etc/xinet.d, with an amanda
 file in it with an old last access date/time, was not 'touched'
 when I ran the amcheck.  Its last access date/time is I
 believe, the date/time of the installation itself.
 
 That amanda-common is 2.6.1p1 IIRC.
 
 amcheck says:
 WARNING: lathe: selfcheck request failed: Connection refused
  
  Try running xinetd -d (then amcheck) to see if (or why not) xinetd
  is running amandad.
  
  Puzzle, first I had to install it!  Then got a report ending here:
  Service defaults
  
  Bind = All addresses.
  Only from: All sites
  No access: No blocked sites
  No logging
  
  Service configuration: amanda
  
  id = amanda
  flags = IPv4
  socket_type = dgram
  Protocol (name,number) = (udp,17)
  port = 10080
  wait = yes
  user = 34
  group = 34
  Groups = yes
  PER_SOURCE = -1
  Bind = All addresses.
  Server = /usr/lib/amanda/amandad
  Server argv = amandad -auth=bsd amdump amindexd amidxtaped
  Only from: All sites
  No access: No blocked sites
  No logging
  
  14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started service:
  amanda 14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} mask_max =
  6, services_started = 1
  14/7/18@11:27:40: NOTICE: 3748 {main} xinetd Version 2.3.14 started
  with libwrap loadavg options compiled in.
  14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available
  service 14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services =
  1
  
  But running an amcheck on the server didn't get any further output
  than what you see above.  And got the same results, connection
  refused. But I see an auth=bsd, where it should be bsdtcp. Fixed
  that, restarted xinetd, no change in amcheck report, lathe still
  refused connection. the amanda file in xinetd.d wasn't touched.  So
  we are a bit closer, but no biscuit.  Next?
 
 If you are using bsdtcp, then you must fix the xinetd file for it.
 socket_type = stream
 protocol= tcp
 wait= no

Did that, and change amanda-server at the top line to the FQDN of this 
machine, which now looks like this:

# default: on
# description: The amanda service
service amanda
{
#   only_from   = coyote.coyote.den
socket_type = stream
protocol= tcp
wait= no
user= backup
group   = backup
groups  = yes
server  = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
disable = no
}

and restarted xinetd
then an xinetd -d returns this:

14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included 
configuration file: /etc/xinetd.d/amanda [file=/etc/xinetd.conf] [line=14]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included 
configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] 
[line=16]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included 
configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] 
[line=28]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included 
configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] 
[line=26]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included 
configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included 
configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=26]
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing chargen
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing chargen
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing daytime
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing daytime
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing discard
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing discard
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing echo
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing echo
14/7/18@12:09:37: DEBUG: 3859 

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 11:54:51 Jean-Louis Martineau did opine
And Gene did reply:
 On 07/18/2014 11:43 AM, Gene Heskett wrote:
  On Friday 18 July 2014 11:34:16 Olivier Nicole did opine
  
  And Gene did reply:
  Gene,
  
  On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com 
wrote:
  Greeting Jean-Louis;
  
  Trying to figure out why amanda can't backup this machine, one of
  the things I noticed in /etc, is that on the shop box, which
  works, there is not an /etc/xinetd.d but it has an old-xinetd.d
  with a single stanza amanda file in it.
  
  An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
  accessed a few minutes ago by my amcheck from the server.
  
  However, on the new install on the machine that is failing to allow
  the connection, there is an /etc/xinet.d, with an amanda file in it
  with an old last access date/time, was not 'touched' when I ran the
  amcheck.  Its last access date/time is I believe, the date/time of
  the installation itself.
  
  That amanda-common is 2.6.1p1 IIRC.
  
  amcheck says:
  WARNING: lathe: selfcheck request failed: Connection refused
  
  There has been enough configuration done that amrecover on this
  machine works.
  
  There is a /var/backups/.amandahosts file, its a link to
  /etc/amandahosts BUT, in /etc/.amandahosts.  I'll mv it to
  /etc/amandahosts. Ran amcheck, no change and that file was not
  accessed.
  
  What do I check next?
  
  netstat -na |grep 10080
  
  You should see an UDP open on that port, else it means xinetd is not
  running/not listening for amanda.
  
  Olivier
  
  gene@lathe:/etc/xinetd.d$ netstat -na |grep 10080
  udp0  0 0.0.0.0:10080   0.0.0.0:*
  udp0  0 0.0.0.0:10080   0.0.0.0:*
  
  IIRC thats good.
 
 It's not good, this is for bsd auth, you want to use bsdtcp.

I changed it according to Olivier, and now amcheck says connection reset 
by peer, and errors back out quickly rather than waiting 10 seconds. Oh, 
didn't notice the udp was a duplicate.  What effects that?

After the amanda file change, now the netstat -na |grep 10080:
gene@lathe:/etc/xinetd.d$ netstat -na |grep 10080
tcp0  0 0.0.0.0:10080   0.0.0.0:*   LISTEN 
udp0  0 0.0.0.0:10080   0.0.0.0:*

Which should look better. But it doesn't make amcheck happy:

Amanda Backup Client Hosts Check

WARNING: lathe: selfcheck request failed: recv error: Connection reset by 
peer
Client check: 3 hosts checked in 2.498 seconds.  1 problem found.

Thanks Jean-Louis.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Olivier Nicole]

On Fri, Jul 18, 2014 at 11:25 PM, Gene Heskett ghesk...@wdtv.com wrote:
 On Friday 18 July 2014 11:53:57 Jean-Louis Martineau did opine
 And Gene did reply:
 On 07/18/2014 11:39 AM, Gene Heskett wrote:
  On Friday 18 July 2014 10:50:47 John Hein did opine
 
  And Gene did reply:
  Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
 Trying to figure out why amanda can't backup this machine, one
 of the things I noticed in /etc, is that on the shop box, which
 works, there is not an /etc/xinetd.d but it has an old-xinetd.d
 with a single stanza amanda file in it.

 An ls -lau shows that file, /etc/old-xinetd.d/amanda was
 apparently accessed a few minutes ago by my amcheck from the
 server.

 However, on the new install on the machine that is failing to
 allow the connection, there is an /etc/xinet.d, with an amanda
 file in it with an old last access date/time, was not 'touched'
 when I ran the amcheck.  Its last access date/time is I
 believe, the date/time of the installation itself.

 That amanda-common is 2.6.1p1 IIRC.

 amcheck says:
 WARNING: lathe: selfcheck request failed: Connection refused
 
  Try running xinetd -d (then amcheck) to see if (or why not) xinetd
  is running amandad.
 
  Puzzle, first I had to install it!  Then got a report ending here:
  Service defaults
 
  Bind = All addresses.
  Only from: All sites
  No access: No blocked sites
  No logging
 
  Service configuration: amanda
 
  id = amanda
  flags = IPv4
  socket_type = dgram
  Protocol (name,number) = (udp,17)
  port = 10080
  wait = yes
  user = 34
  group = 34
  Groups = yes
  PER_SOURCE = -1
  Bind = All addresses.
  Server = /usr/lib/amanda/amandad
  Server argv = amandad -auth=bsd amdump amindexd amidxtaped
  Only from: All sites
  No access: No blocked sites
  No logging
 
  14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started service:
  amanda 14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} mask_max =
  6, services_started = 1
  14/7/18@11:27:40: NOTICE: 3748 {main} xinetd Version 2.3.14 started
  with libwrap loadavg options compiled in.
  14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available
  service 14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services =
  1
 
  But running an amcheck on the server didn't get any further output
  than what you see above.  And got the same results, connection
  refused. But I see an auth=bsd, where it should be bsdtcp. Fixed
  that, restarted xinetd, no change in amcheck report, lathe still
  refused connection. the amanda file in xinetd.d wasn't touched.  So
  we are a bit closer, but no biscuit.  Next?

 If you are using bsdtcp, then you must fix the xinetd file for it.
 socket_type = stream
 protocol= tcp
 wait= no

 Did that, and change amanda-server at the top line to the FQDN of this
 machine, which now looks like this:

 # default: on
 # description: The amanda service
 service amanda
 {
 #   only_from   = coyote.coyote.den
 socket_type = stream
 protocol= tcp
 wait= no
 user= backup
 group   = backup
 groups  = yes
 server  = /usr/lib/amanda/amandad
 server_args = -auth=bsdtcp amdump amindexd amidxtaped
 disable = no
 }

 and restarted xinetd
 then an xinetd -d returns this:

 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
 configuration file: /etc/xinetd.d/amanda [file=/etc/xinetd.conf] [line=14]
 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
 configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen]
 [line=16]
 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
 configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime]
 [line=28]
 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
 configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard]
 [line=26]
 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
 configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
 configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=26]
 14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing chargen
 14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing chargen
 14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing daytime
 14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing daytime
 14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing discard
 14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing discard
 14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing echo
 14/7/18@12:09:37: 

Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

 
 What do I check next?  
 
 Thank you.
 
 Cheers, Gene Heskett

Since Olivier wrote that he only used xinetd once,  I figured I’d best chime in.
I use it all the time (not that I know very much about it).   Here are parts of 
my CHECKLIST
for a new node:


yum install openssh-server
yum install xinetd
yum install  dump(xfsdump is problematic)
yum install mtx
yum install mt-st

yum remove xfsdump

Add a file with the name .amandahosts to the backup-user home directory with
these contents:

backup-server.full.name  backup-user   amdump  amindexd

chmod 600 /home/backup-user/.*amandahosts  #it insists on this


My   xinetd start file matches yours, as quoted in a recent email.
service amanda
{
socket_type = stream
protocol= tcp
wait= no
user= backup-user
group   = root#whatever you are using
server  = /usr/local/libexec/amanda/amandad  
#wherever your file actually IS
server_args = -auth=bsdtcp amdump amindexd amidxtaped
disable = no
groups  = yes
}

/sbin/service xinetd restart # restart xinetd


If they don't already exist, add these  in /etc/services
amanda 10080/udp # Dump server control
amidxtape 10083/tcp # Amanda tape indexing
amandaidx 10082/tcp # Amanda recovery program



ON SERVER:   new node:
  add to   disklist file
  add to /etc/sysconfig/iptables  and restart with
 /sbin/service iptables restart # if you have iptables 
running
  add to  .amandahosts



Test a simple backup (without using up a tape).  On SERVER:
amdump   config   --no-taper  newclientnode  /# or any DLE that’s small

===
Any of this help?
Deb Baddorf
Fermilab

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 11:58:22 Joi L. Ellis did opine
And Gene did reply:
 I've been installing Amanda on our network for the past few months and
 on a number of the machines, I noticed that the machine had an
 /etc/xinetd.d/Amanda file, but the xinetd service wasn't installed,
 openbsd-inetd was, and that one reads /etc/inetd.conf.  Amanda-client
 package installs the config lines for both inetd packages, but
 naturally only one of them will be read by your machine.  Depending
 upon the version of the package you installed, I've seen Amanda-client
 install both, only xinetd, or only openbsd-inetd configs, so your
 machine may be looking at a different inetd config than you expected.
 
 Also check to see if your machine is running iptables or ufw, and if
 so, do 'lsmod | grep amanda' and verify that the ip_conntrack_amanda
 or nf_conntrack_amanda module is loaded.  If either firewall is active
 it is probably blocking your ports.
 
 If you have the rules enabled, but the *_conntrack_amanda module isn't
 loaded in the kernel, the amcheck will work but amdump will fail. 
 (I've just worked with another admin here to get Amanda running on a
 new machine of his and this was the problem.)
 
Here, amcheck AND of course amdump are failing.  I did look at indetd.conf 
and reset it for bsdtcp, made no change.   However I just noted that htop 
is reporting two copies of xinetd running, one as root, one as me, and the 
end of the report line says inetd_compat -inetd_ipv6.  No clue where 
that inetd_ipv6 comes from.  If its a limitation, thats it.

From the manpage:
   -inetd_compat
  This  option  causes xinetd to read /etc/inetd.conf in 
addition to the standard xinetd config files.  /etc/inetd.conf is read 
after the standard xinetd
  config files.

   -inetd_ipv6
  This option causes xinetd to bind to IPv6  (AF_INET6)  
addresses  for  inetd  compatibility  lines  (see  previous  option).   
This  only  affects  how
  /etc/inetd.conf is interpreted and thus only has any effect 
if the -inetd_compat option is also used.

Is that something I should remove?  In it in the option line in 
/etc/init.d/xinetd as
init.d/xinetd:XINETD_OPTS=$XINETD_OPTS -inetd_ipv6

Do do know that by default, this 4 year old install tries to make us use 
ipv6 only. So you have to carve up your own network/interfaces files to 
get a working network.


 --
 Joi Owen
 System Administrator
 Pavlov Media, Inc
 
 -Original Message-
 From: owner-amanda-us...@amanda.org
 [mailto:owner-amanda-us...@amanda.org] On Behalf Of Gene Heskett Sent:
 Friday, July 18, 2014 10:39 AM
 To: amanda-users@amanda.org
 Subject: [BULK] Re: amrecover works, normal amanda backup, logging
 connection refused
 
 On Friday 18 July 2014 10:50:47 John Hein did opine And Gene did reply:
  Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
Trying to figure out why amanda can't backup this machine, one of
   
   the things I noticed in /etc, is that on the shop box, which works,
   there is not an /etc/xinetd.d but it has an old-xinetd.d with a  
  
  single stanza amanda file in it.
  
An ls -lau shows that file, /etc/old-xinetd.d/amanda was
apparently
   
   accessed a few minutes ago by my amcheck from the server.
   
However, on the new install on the machine that is failing to
allow
   
   the connection, there is an /etc/xinet.d, with an amanda file in it
   with an old last access date/time, was not 'touched' when I ran the
   amcheck.  Its last access date/time is I believe, the date/time of
   the installation itself.
   
That amanda-common is 2.6.1p1 IIRC.

amcheck says:
WARNING: lathe: selfcheck request failed: Connection refused
  
  Try running xinetd -d (then amcheck) to see if (or why not) xinetd is
  running amandad.
 
 Puzzle, first I had to install it!  Then got a report ending here:
 Service defaults
   Bind = All addresses.
   Only from: All sites
   No access: No blocked sites
   No logging
 
 Service configuration: amanda
   id = amanda
   flags = IPv4
   socket_type = dgram
   Protocol (name,number) = (udp,17)
   port = 10080
   wait = yes
   user = 34
   group = 34
   Groups = yes
   PER_SOURCE = -1
   Bind = All addresses.
   Server = /usr/lib/amanda/amandad
   Server argv = amandad -auth=bsd amdump amindexd amidxtaped
   Only from: All sites
   No access: No blocked sites
   No logging
 
 14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started service:
 amanda 14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} mask_max =
 6, services_started = 1 14/7/18@11:27:40: NOTICE: 3748 {main} xinetd
 Version 2.3.14 started with libwrap loadavg options compiled in.
 14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available
 service 14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services = 1
 
 But running an amcheck on the server didn't get any further

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 12:10:10 Charles Curley did opine
And Gene did reply:
 On Fri, 18 Jul 2014 22:34:16 +0700
 
 Olivier Nicole olivier.nic...@cs.ait.ac.th wrote:
   What do I check next?
 
 Firewall?
 
 That's bitten me more than once.

No firewalls running on any machine, I have a dd-wrt router between me and 
my local network and the modem.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 12:11:24 Debra S Baddorf did opine
And Gene did reply:
  There is a /var/backups/.amandahosts file, its a link to
  /etc/amandahosts BUT, in /etc/.amandahosts.  I'll mv it to
  /etc/amandahosts. Ran amcheck, no change and that file was not
  accessed.
 
 The actual file SHOULD have a dot at the beginning of the name.
 .amandahosts
 I guess if the one amanda USES   (perhaps  /var/backups/.amandahosts  
 but I’d bet on the other one)starts with a dot,  then it doesn’t
 much matter what that link points to.
  But on the whole,  the file IS supposed to start with a dot.
 
 Deb Baddorf
 Fermilab

I'll replace that link with the real .amandahosts

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 12:11:24 Debra S Baddorf did opine
And Gene did reply:
  There is a /var/backups/.amandahosts file, its a link to
  /etc/amandahosts BUT, in /etc/.amandahosts.  I'll mv it to
  /etc/amandahosts. Ran amcheck, no change and that file was not
  accessed.
 
 The actual file SHOULD have a dot at the beginning of the name.
 .amandahosts
 I guess if the one amanda USES   (perhaps  /var/backups/.amandahosts  
 but I’d bet on the other one)starts with a dot,  then it doesn’t
 much matter what that link points to.
  But on the whole,  the file IS supposed to start with a dot.
 
 Deb Baddorf
 Fermilab

I replaced the link with the real file as .amandahosts, but no change in 
the amcheck report.

Connection reset by peer.

And I mv'd /etc/amandahosts as .amandahosts. again no change in the 
amcheck report.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 12:44:49 Olivier Nicole did opine
And Gene did reply:
 On Fri, Jul 18, 2014 at 11:25 PM, Gene Heskett ghesk...@wdtv.com 
wrote:
  On Friday 18 July 2014 11:53:57 Jean-Louis Martineau did opine
  
  And Gene did reply:
  On 07/18/2014 11:39 AM, Gene Heskett wrote:
   On Friday 18 July 2014 10:50:47 John Hein did opine
   
   And Gene did reply:
   Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
  Trying to figure out why amanda can't backup this machine,
  one of the things I noticed in /etc, is that on the shop
  box, which works, there is not an /etc/xinetd.d but it has
  an old-xinetd.d with a single stanza amanda file in it.
  
  An ls -lau shows that file, /etc/old-xinetd.d/amanda was
  apparently accessed a few minutes ago by my amcheck from the
  server.
  
  However, on the new install on the machine that is failing to
  allow the connection, there is an /etc/xinet.d, with an
  amanda file in it with an old last access date/time, was not
  'touched' when I ran the amcheck.  Its last access date/time
  is I believe, the date/time of the installation itself.
  
  That amanda-common is 2.6.1p1 IIRC.
  
  amcheck says:
  WARNING: lathe: selfcheck request failed: Connection refused
   
   Try running xinetd -d (then amcheck) to see if (or why not)
   xinetd is running amandad.
   
   Puzzle, first I had to install it!  Then got a report ending here:
   Service defaults
   
   Bind = All addresses.
   Only from: All sites
   No access: No blocked sites
   No logging
   
   Service configuration: amanda
   
   id = amanda
   flags = IPv4
   socket_type = dgram
   Protocol (name,number) = (udp,17)
   port = 10080
   wait = yes
   user = 34
   group = 34
   Groups = yes
   PER_SOURCE = -1
   Bind = All addresses.
   Server = /usr/lib/amanda/amandad
   Server argv = amandad -auth=bsd amdump amindexd amidxtaped
   Only from: All sites
   No access: No blocked sites
   No logging
   
   14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started
   service: amanda 14/7/18@11:27:40: DEBUG: 3748
   {cnf_start_services} mask_max = 6, services_started = 1
   14/7/18@11:27:40: NOTICE: 3748 {main} xinetd Version 2.3.14
   started with libwrap loadavg options compiled in.
   14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available
   service 14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services
   = 1
   
   But running an amcheck on the server didn't get any further output
   than what you see above.  And got the same results, connection
   refused. But I see an auth=bsd, where it should be bsdtcp. Fixed
   that, restarted xinetd, no change in amcheck report, lathe still
   refused connection. the amanda file in xinetd.d wasn't touched. 
   So we are a bit closer, but no biscuit.  Next?
  
  If you are using bsdtcp, then you must fix the xinetd file for it.
  
  socket_type = stream
  protocol= tcp
  wait= no
  
  Did that, and change amanda-server at the top line to the FQDN of
  this machine, which now looks like this:
  
  # default: on
  # description: The amanda service
  service amanda
  {
  #   only_from   = coyote.coyote.den
  
  socket_type = stream
  protocol= tcp
  wait= no
  user= backup
  group   = backup
  groups  = yes
  server  = /usr/lib/amanda/amandad
  server_args = -auth=bsdtcp amdump amindexd amidxtaped
  disable = no
  
  }
  
  and restarted xinetd
  then an xinetd -d returns this:
  
  14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
  configuration file: /etc/xinetd.d/amanda [file=/etc/xinetd.conf]
  [line=14] 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading
  included configuration file: /etc/xinetd.d/chargen
  [file=/etc/xinetd.d/chargen] [line=16]
  14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
  configuration file: /etc/xinetd.d/daytime
  [file=/etc/xinetd.d/daytime] [line=28]
  14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
  configuration file: /etc/xinetd.d/discard
  [file=/etc/xinetd.d/discard] [line=26]
  14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
  configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo]
  [line=25] 14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading
  included configuration file: /etc/xinetd.d/time
  [file=/etc/xinetd.d/time] [line=26] 14/7/18@12:09:37: DEBUG: 3859
  {remove_disabled_services} removing chargen 14/7/18@12:09:37: DEBUG:
  3859 {remove_disabled_services} removing chargen 14/7/18@12:09:37:
  DEBUG: 3859 {remove_disabled_services} removing daytime
  14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing
  daytime 

Re: amrecover works, normal amanda backup, logging connection refused

[John Hein]

Gene Heskett wrote at 12:25 -0400 on Jul 18, 2014:
  14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address 
  already in use (errno = 98)). service = amanda

More than one xinetd or inetd running?

Maybe some basic background is in order.  The basic operation of
*inetd is pretty simple, and if you understand the basics, you can
really solve many of the common issues yourself.

*inetd runs forever listening on the sockets you tell it to
listen on (as configured by the xinetd or inetd config files).
When requests (any activity) on that socket come in, it tries
to run the service that is specified in its configuration.

If something else owns that socket, *inetd can't do its job
(i.e., can't start the service corresponds to that socket).

If not, then *inetd will spawn off the configured service (amandad
in amanda's case).

Technically, you don't need *inetd.  You can kick off amandad to run
on the client some other way (e.g., daemontools, ssh).  But the server
expects something to be listening on the client when it comes time to
do the dump.

As others have mentioned, you have to configure things for the right
type of socket - the configuration of the amanda server (primarily
in amanda.conf / disklist) and client (typically inetd config and
amanda-client.conf) should match (see amanda-auth(7) and
amanda-client.conf(5)).

Here's some other good info so you can maybe help yourself and
understand better how things work:

http://wiki.zmanda.com/index.php/Quick_start_%28old%29

Re: amrecover works, normal amanda backup, logging connection refused

[Jon LaBadie]

On Fri, Jul 18, 2014 at 10:26:38AM -0400, Gene Heskett wrote:
 Greeting Jean-Louis;
 
 Trying to figure out why amanda can't backup this machine, one of the 
 things I noticed in /etc, is that on the shop box, which works, there is 
 not an /etc/xinetd.d but it has an old-xinetd.d with a single stanza 
 amanda file in it.
 
 An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently 
 accessed a few minutes ago by my amcheck from the server.
 
 However, on the new install on the machine that is failing to allow the 
 connection, there is an /etc/xinet.d, with an amanda file in it with an 
 old last access date/time, was not 'touched' when I ran the amcheck.  Its  
 last access date/time is I believe, the date/time of the installation 
 itself.
 

The last used time 'may' not be valid.  Some admins mount their
filesystems with the ?noatime? option.

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (609) 477-8330 (C)

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 13:24:12 Debra S Baddorf did opine
And Gene did reply:
  What do I check next?
  
  Thank you.
  
  Cheers, Gene Heskett
 
 Since Olivier wrote that he only used xinetd once,  I figured I’d best
 chime in. I use it all the time (not that I know very much about it). 
  Here are parts of my CHECKLIST for a new node:
 
 
 yum install openssh-server
Got that already
 yum install xinetd
installed about an hour ago
 yum install  dump(xfsdump is problematic)
Not using dump, tar-1.22 instead
 yum install mtx
Not using tape
 yum install mt-st
Not using tape 
 yum remove xfsdump
 
 Add a file with the name .amandahosts to the backup-user home
 directory with these contents:
 
 backup-server.full.name  backup-user   amdump  amindexd

backup user on the server is amanda, but neither client machine even has 
an amanda (or backup) user.  Presumably its backup:backup on the clients.
The /var/backups/.amandahosts files were different, so I made the failing 
machine match the working machines version, no change, made the one in 
/etc match, again no change.  Neither file had amindexd listed, added that 
to each, one at a time, no change.

 
 chmod 600 /home/backup-user/.*amandahosts  #it insists on this
 
Yup
 
 My   xinetd start file matches yours, as quoted in a recent email.
 service amanda
 {
 socket_type = stream
 protocol= tcp
 wait= no
 user= backup-user
 group   = root#whatever you are using
 server  = /usr/local/libexec/amanda/amandad
  #wherever your file actually IS server_args =
 -auth=bsdtcp amdump amindexd amidxtaped disable = no
 groups  = yes
 }
 
 /sbin/service xinetd restart # restart xinetd
 
 
 If they don't already exist, add these  in /etc/services
 amanda 10080/udp # Dump server control
 amidxtape 10083/tcp # Amanda tape indexing
 amandaidx 10082/tcp # Amanda recovery program
 
 
 
 ON SERVER:   new node:
   add to   disklist file
   add to /etc/sysconfig/iptables  and restart with
  /sbin/service iptables restart # if you have
 iptables running add to  .amandahosts
 
No iptables running.
 
 
 Test a simple backup (without using up a tape).  On SERVER:
 amdump   config   --no-taper  newclientnode  /# or any DLE
 that’s small
as root: su amanda -c amdump Daily --no-taper lathe /home

returns no error in about 1 full second.

 ===
 Any of this help?
 Deb Baddorf
 Fermilab


Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

On Jul 18, 2014, at 11:25 AM, Gene Heskett ghesk...@wdtv.com wrote:

 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address 
 already in use (errno = 98)). service = amanda
 14/7/18@12:09:37: ERROR: 3859 {cnf_start_services} Service amanda failed 
 to start and is deactivated.
 14/7/18@12:09:37: DEBUG: 3859 {cnf_start_services} mask_max = 0, 
 services_started = 0
 14/7/18@12:09:37: CRITICAL: 3859 {init_services} no services. Exiting...


I don’t like this part of your earlier email.
Does tail  /var/log/messages  say anything about an error?  
After I use root and restart xinetd  

 /sbin/service xinetd restart 
Stopping xinetd:   [  OK  ]
Starting xinetd:   [  OK  ]



  my  /var/log/messages file says

Jul 18 13:50:47 adback2 xinetd[32427]: Exiting...
Jul 18 13:50:47 adback2 xinetd[32468]: xinetd Version 2.3.14 started with 
libwrap loadavg labeled-networking options compiled in.
Jul 18 13:50:47 adback2 xinetd[32468]: Started working: 8 available services


Does yours say there are ANY services successfully running?
Deb

RE: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Joi L. Ellis]

I think you have a more basic network connectivity issue.  If it were a simple 
.amandahosts issue, you'd get an error message to that affect, not 'connection 
reset by peer', which is a network thing.

Don't forget to check the logs on the server and the client, see 
/var/log/Amanda/*, find the newest files in there and see what they say.

The first thing to do is verify that the server can backup itself as a client.  
If your server-side is not working, this will get that straightened out.  Then 
check that the server and the client can resolve each other's hostnames, and 
that they can ping each other (firewalls allowing.)  If you can, put the client 
on the same network as the server and disable all iptables/ufw firewalls, and 
verify it works that way.  Then move the client back to its own network and 
test again.  If it breaks on the other network, it has to be a firewall or 
network issue blocking you.

In my own project here to install Amanda services everywhere, I've discovered 
hosts running undocumented iptables, undocumented firewalls, and all sorts of 
DNS breakages that I've had to clean up as I went.

For what it's worth, I had to drop back to using plain old auth=bsd for Amanda, 
not bsdtcp, as some of the clients are so ancient the Amanda-client packages 
they have don't grok bsdtcp yet, so I'm using the lcd to get everyone running 
on a consistent setup.  Once the ancients are retired I can upgrade all of them 
to something modern, but until then...


--
Joi Owen
System Administrator
Pavlov Media, Inc


-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On 
Behalf Of Gene Heskett
Sent: Friday, July 18, 2014 1:36 PM
To: amanda-users@amanda.org
Subject: [BULK] Re: amrecover works, normal amanda backup, logging connection 
refused

On Friday 18 July 2014 13:24:12 Debra S Baddorf did opine And Gene did reply:
  What do I check next?
  
  Thank you.
  
  Cheers, Gene Heskett
 
 Since Olivier wrote that he only used xinetd once,  I figured I'd best 
 chime in. I use it all the time (not that I know very much about it).
  Here are parts of my CHECKLIST for a new node:
 
 
 yum install openssh-server
Got that already
 yum install xinetd
installed about an hour ago
 yum install  dump(xfsdump is problematic)
Not using dump, tar-1.22 instead
 yum install mtx
Not using tape
 yum install mt-st
Not using tape 
 yum remove xfsdump
 
 Add a file with the name .amandahosts to the backup-user home 
 directory with these contents:
 
 backup-server.full.name  backup-user   amdump  amindexd

backup user on the server is amanda, but neither client machine even has an 
amanda (or backup) user.  Presumably its backup:backup on the clients.
The /var/backups/.amandahosts files were different, so I made the failing 
machine match the working machines version, no change, made the one in /etc 
match, again no change.  Neither file had amindexd listed, added that to each, 
one at a time, no change.

 
 chmod 600 /home/backup-user/.*amandahosts  #it insists on this
 
Yup
 
 My   xinetd start file matches yours, as quoted in a recent email.
 service amanda
 {
 socket_type = stream
 protocol= tcp
 wait= no
 user= backup-user
 group   = root#whatever you are using
 server  = /usr/local/libexec/amanda/amandad
  #wherever your file actually IS server_args =
 -auth=bsdtcp amdump amindexd amidxtaped disable = no
 groups  = yes
 }
 
 /sbin/service xinetd restart # restart xinetd
 
 
 If they don't already exist, add these  in /etc/services amanda 
 10080/udp # Dump server control amidxtape 10083/tcp # Amanda tape 
 indexing amandaidx 10082/tcp # Amanda recovery program
 
 
 
 ON SERVER:   new node:
   add to   disklist file
   add to /etc/sysconfig/iptables  and restart with
  /sbin/service iptables restart # if you have
 iptables running add to  .amandahosts
 
No iptables running.
 
 
 Test a simple backup (without using up a tape).  On SERVER:
 amdump   config   --no-taper  newclientnode  /# or any DLE
 that's small
as root: su amanda -c amdump Daily --no-taper lathe /home

returns no error in about 1 full second.

 ===
 Any of this help?
 Deb Baddorf
 Fermilab


Cheers, Gene Heskett
--
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

On Jul 18, 2014, at 1:35 PM, Gene Heskett ghesk...@wdtv.com wrote:

 backup user on the server is amanda, but neither client machine even has 
 an amanda (or backup) user.  Presumably its backup:backup on the clients.
 The /var/backups/.amandahosts files were different, so I made the failing 
 machine match the working machines version, no change, made the one in 
 /etc match, again no change.  Neither file had amindexd listed, added that 
 to each, one at a time, no change.


Well, whatever you have as the username   (I use operator and group=root)
you need to have a user by that name.  It can be  no-loginbut it has
to be there.

Does the client have any  /tmp/amanda log files? Certain such log files
contain the  configured params at the top.   That would tell you what the
backup user is supposed to be. grep   for   CLIENT_LOGIN

Or did I miss you saying that you HAD created an account on the client node?
Deb

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 14:27:20 Jon LaBadie did opine
And Gene did reply:
 On Fri, Jul 18, 2014 at 10:26:38AM -0400, Gene Heskett wrote:
  Greeting Jean-Louis;
  
  Trying to figure out why amanda can't backup this machine, one of the
  things I noticed in /etc, is that on the shop box, which works, there
  is not an /etc/xinetd.d but it has an old-xinetd.d with a single
  stanza amanda file in it.
  
  An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
  accessed a few minutes ago by my amcheck from the server.
  
  However, on the new install on the machine that is failing to allow
  the connection, there is an /etc/xinet.d, with an amanda file in it
  with an old last access date/time, was not 'touched' when I ran the
  amcheck.  Its last access date/time is I believe, the date/time of
  the installation itself.
 
 The last used time 'may' not be valid.  Some admins mount their
 filesystems with the ?noatime? option.
 
 Jon

That option is not set in either machines /etc/fstab Jon.

Thanks.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 14:51:39 Debra S Baddorf did opine
And Gene did reply:
 On Jul 18, 2014, at 11:25 AM, Gene Heskett ghesk...@wdtv.com wrote:
  14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address
  already in use (errno = 98)). service = amanda
  14/7/18@12:09:37: ERROR: 3859 {cnf_start_services} Service amanda
  failed to start and is deactivated.
  14/7/18@12:09:37: DEBUG: 3859 {cnf_start_services} mask_max = 0,
  services_started = 0
  14/7/18@12:09:37: CRITICAL: 3859 {init_services} no services.
  Exiting...
 
 I don’t like this part of your earlier email.
 Does tail  /var/log/messages  say anything about an error?
 After I use root and restart xinetd
 
  /sbin/service xinetd restart
 Stopping xinetd:   [  OK  ]
 Starting xinetd:   [  OK  ]
 
 
 
   my  /var/log/messages file says
 
 Jul 18 13:50:47 adback2 xinetd[32427]: Exiting...
 Jul 18 13:50:47 adback2 xinetd[32468]: xinetd Version 2.3.14 started
 with libwrap loadavg labeled-networking options compiled in. Jul 18
 13:50:47 adback2 xinetd[32468]: Started working: 8 available services
 
 
 Does yours say there are ANY services successfully running?
 Deb

Nothing about xinetd in dmesg, or in messages.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 14:53:23 Joi L. Ellis did opine
And Gene did reply:
 I think you have a more basic network connectivity issue.  If it were a
 simple .amandahosts issue, you'd get an error message to that affect,
 not 'connection reset by peer', which is a network thing.
 
 Don't forget to check the logs on the server and the client, see
 /var/log/Amanda/*, find the newest files in there and see what they
 say.
 
 The first thing to do is verify that the server can backup itself as a
 client.

It did last night, along with the shop machine, but not the lathe machine.  
I've been using amanda for about 15 years here

 If your server-side is not working, this will get that
 straightened out.  Then check that the server and the client can
 resolve each other's hostnames, and that they can ping each other
 (firewalls allowing.)  If you can, put the client on the same network
 as the server and disable all iptables/ufw firewalls, and verify it
 works that way.

They are all on the same 192.168.xx.xx subnet. I use hosts files and  can 
ssh -Y lathe into the machine, in fact thats how I am doing all this.

 Then move the client back to its own network and test
 again.  If it breaks on the other network, it has to be a firewall or
 network issue blocking you.
 
 In my own project here to install Amanda services everywhere, I've
 discovered hosts running undocumented iptables, undocumented
 firewalls, and all sorts of DNS breakages that I've had to clean up as
 I went.
 
 For what it's worth, I had to drop back to using plain old auth=bsd for
 Amanda, not bsdtcp, as some of the clients are so ancient the
 Amanda-client packages they have don't grok bsdtcp yet, so I'm using
 the lcd to get everyone running on a consistent setup.  Once the
 ancients are retired I can upgrade all of them to something modern,
 but until then...

The other machine just like it, same box etc, has been using bsdtcp for 
several years.

About burned out, but I need this backup to work too.
 
 
 --
 Joi Owen
 System Administrator
 Pavlov Media, Inc
 
 
 -Original Message-
 From: owner-amanda-us...@amanda.org
 [mailto:owner-amanda-us...@amanda.org] On Behalf Of Gene Heskett Sent:
 Friday, July 18, 2014 1:36 PM
 To: amanda-users@amanda.org
 Subject: [BULK] Re: amrecover works, normal amanda backup, logging
 connection refused
 
 On Friday 18 July 2014 13:24:12 Debra S Baddorf did opine And Gene did 
reply:
   What do I check next?
   
   Thank you.
   
   Cheers, Gene Heskett
  
  Since Olivier wrote that he only used xinetd once,  I figured I'd
  best chime in. I use it all the time (not that I know very much
  about it).
  
   Here are parts of my CHECKLIST for a new node:
  yum install openssh-server
 
 Got that already
 
  yum install xinetd
 
 installed about an hour ago
 
  yum install  dump(xfsdump is problematic)
 
 Not using dump, tar-1.22 instead
 
  yum install mtx
 
 Not using tape
 
  yum install mt-st
 
 Not using tape
 
  yum remove xfsdump
  
  Add a file with the name .amandahosts to the backup-user home
  directory with these contents:
  
  backup-server.full.name  backup-user   amdump  amindexd
 
 backup user on the server is amanda, but neither client machine even
 has an amanda (or backup) user.  Presumably its backup:backup on the
 clients. The /var/backups/.amandahosts files were different, so I made
 the failing machine match the working machines version, no change,
 made the one in /etc match, again no change.  Neither file had
 amindexd listed, added that to each, one at a time, no change.
 
  chmod 600 /home/backup-user/.*amandahosts  #it insists on this
 
 Yup
 
  My   xinetd start file matches yours, as quoted in a recent email.
  service amanda
  {
  
  socket_type = stream
  protocol= tcp
  wait= no
  user= backup-user
  group   = root#whatever you are using
  server  = /usr/local/libexec/amanda/amandad
   
   #wherever your file actually IS server_args =
  
  -auth=bsdtcp amdump amindexd amidxtaped disable = no
  
  groups  = yes
  
  }
  
  /sbin/service xinetd restart # restart xinetd
  
  
  If they don't already exist, add these  in /etc/services amanda
  10080/udp # Dump server control amidxtape 10083/tcp # Amanda tape
  indexing amandaidx 10082/tcp # Amanda recovery program
  
  ON SERVER:   new node:
add to   disklist file
add to /etc/sysconfig/iptables  and restart with

   /sbin/service iptables restart # if you have
  
  iptables running add to  .amandahosts
 
 No iptables running.
 
  Test a simple backup (without using up a tape).  On SERVER:
  amdump   config   --no-taper  newclientnode  /# or any DLE
  that's small
 
 as root: su amanda -c amdump Daily --no-taper lathe /home
 
 returns no error in about 1 full second

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com wrote:

 I think you have a more basic network connectivity issue.  If it were a 
 simple .amandahosts issue, you'd get an error message to that affect, not 
 'connection reset by peer', which is a network thing.
 
 Don't forget to check the logs on the server and the client, see 
 /var/log/Amanda/*, find the newest files in there and see what they say.
 
 The first thing to do is verify that the server can backup itself as a 
 client.  If your server-side is not working, this will get that straightened 
 out.  Then check that the server and the client can resolve each other's 
 hostnames, and that they can ping each other (firewalls allowing.)  If you 
 can, put the client on the same network as the server and disable all 
 iptables/ufw firewalls, and verify it works that way.  Then move the client 
 back to its own network and test again.  If it breaks on the other network, 
 it has to be a firewall or network issue blocking you.
 
 In my own project here to install Amanda services everywhere, I've discovered 
 hosts running undocumented iptables, undocumented firewalls, and all sorts of 
 DNS breakages that I've had to clean up as I went.
 
 For what it's worth, I had to drop back to using plain old auth=bsd for 
 Amanda, not bsdtcp, as some of the clients are so ancient the Amanda-client 
 packages they have don't grok bsdtcp yet, so I'm using the lcd to get 
 everyone running on a consistent setup.  Once the ancients are retired I can 
 upgrade all of them to something modern, but until then...
 
 
 --
 Joi Owen
 System Administrator
 Pavlov Media, Inc


I’ve got clients in several flavors.  My server has all of the types of xinetd  
running,  and can listen to whatever the client is sending.
Of course,  I have to configure the amanda.conf  and disklist  to request of 
backup of the right type for each client.   Each client
can only do one kind  (in my experience).



for example  (only if you are interested any further)
AMANDA.CONF:
define dumptype dailyNormal {
BDglobal
 # includes auth bsd 
}

define dumptype dailyNormalBSDTCP  {
BDglobal
auth “bsdtcp”#overrides the “bsd
}

define dumptype dailyNormalKRB5  {
BDglobal
auth “krb5   #overrides the “bsd”
}

DISKLIST:

client1/dailyNormal
client2 /   dailyNormalBSDTCP
client3/dailyNormalKRB5


/ETC/XINETD.D   :I’m sure the filenames don’t matter, but these help me:

amanda-dgramfile:
##note the   auth=bsdon the server_args line

service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= operator
group   = root
server  = /usr/local/libexec/amanda/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
disable = no
groups  = yes
}


amanda-krb5   file:
##note the   auth=krb5on the server_args line

service k5amanda
{
socket_type = stream
protocol= tcp
wait= no
user= root
group   = root
server  = /usr/local/libexec/amanda/amandad
server_args = -auth=krb5 amdump amindexd amidxtaped
disable = no
groups  = yes
}


amanda-stream   file:
##note the   auth=bsdtcpon the server_args line

service amanda
{
socket_type = stream 
protocol= tcp
wait= no
user= operator
group   = root
server  = /usr/local/libexec/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
disable = no
groups  = yes
}

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 15:06:49 Debra S Baddorf did opine
And Gene did reply:
 On Jul 18, 2014, at 1:35 PM, Gene Heskett ghesk...@wdtv.com wrote:
  backup user on the server is amanda, but neither client machine even
  has an amanda (or backup) user.  Presumably its backup:backup on the
  clients. The /var/backups/.amandahosts files were different, so I
  made the failing machine match the working machines version, no
  change, made the one in /etc match, again no change.  Neither file
  had amindexd listed, added that to each, one at a time, no change.
 
 Well, whatever you have as the username   (I use operator and
 group=root) you need to have a user by that name.  It can be  no-login
but it has to be there.
 
 Does the client have any  /tmp/amanda log files? Certain such log
 files contain the  configured params at the top.   That would tell you
 what the backup user is supposed to be. grep   for   CLIENT_LOGIN
 
 Or did I miss you saying that you HAD created an account on the client
 node? Deb

The working machine has a  /tmp/amanda directory, the non-working one does 
not.

Both /tmp's are owned by root, and looks to be 0777 perms, the whole 
string shows drwxrwxrwt on both machines,  This is not a network 
showstopper, I am ssh -Y into both machines, checking diffs. ATM I haven't 
found and fixed any diffs between those two machines that did make a diff.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com wrote:

 Don't forget to check the logs on the server and the client, see 
 /var/log/Amanda/*, find the newest files in there and see what they say.


do a  locate(or a find /  -iname “*am*”  )   to find your amanda logs.

Joi  puts his in  /var/log/Amanda   apparently.
I have mine  in   /tmp/amanda   — which I *think*  is the default,  but who 
knows!

Some of the logs start with   “amandad.”  some are “amrecover”  (since you’ve 
got THAT working,  you can look where THOSE
logs get put).  Some start with   “selfcheck”  but those are the ones you 
aren’t reaching yet.

Deb Baddorf
Fermilab

Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

On Jul 18, 2014, at 2:13 PM, Gene Heskett ghesk...@wdtv.com wrote:

 On Friday 18 July 2014 14:51:39 Debra S Baddorf did opine
 And Gene did reply:
 On Jul 18, 2014, at 11:25 AM, Gene Heskett ghesk...@wdtv.com wrote:
 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address
 already in use (errno = 98)). service = amanda
 14/7/18@12:09:37: ERROR: 3859 {cnf_start_services} Service amanda
 failed to start and is deactivated.
 14/7/18@12:09:37: DEBUG: 3859 {cnf_start_services} mask_max = 0,
 services_started = 0
 14/7/18@12:09:37: CRITICAL: 3859 {init_services} no services.
 Exiting...
 
 I don’t like this part of your earlier email.
 Does tail  /var/log/messages  say anything about an error?
 After I use root and restart xinetd
 
 /sbin/service xinetd restart
 Stopping xinetd:   [  OK  ]
 Starting xinetd:   [  OK  ]
 
 
 
  my  /var/log/messages file says
 
 Jul 18 13:50:47 adback2 xinetd[32427]: Exiting...
 Jul 18 13:50:47 adback2 xinetd[32468]: xinetd Version 2.3.14 started
 with libwrap loadavg labeled-networking options compiled in. Jul 18
 13:50:47 adback2 xinetd[32468]: Started working: 8 available services
 
 
 Does yours say there are ANY services successfully running?
 Deb
 
 Nothing about xinetd in dmesg, or in messages.
 
 Cheers, Gene Heskett



Hmmm.   Do we have a running  xinet ?

 ps auxww | grep net
root  2758  0.0  0.0   2852   884 ?Ss   Jul11   0:00 xinetd 
-stayalive -pidfile /var/run/xinetd.pid

 /sbin/chkconfig --list  xinetd
xinetd  0:off   1:off   2:off   3:on4:on5:on6:off
 this tells what phases of reboot to start it with.   The  “ps”  will say 
if it is running NOW.

If you find   “inetd”  instead  (or whatever the older name was?)   THEN  we 
can proceed down that path.
Deb Baddorf

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 15:24:00 Debra S Baddorf did opine
And Gene did reply:
 On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com 
wrote:
  I think you have a more basic network connectivity issue.  If it were
  a simple .amandahosts issue, you'd get an error message to that
  affect, not 'connection reset by peer', which is a network thing.
  
  Don't forget to check the logs on the server and the client, see
  /var/log/Amanda/*, find the newest files in there and see what they
  say.
  
  The first thing to do is verify that the server can backup itself as
  a client.  If your server-side is not working, this will get that
  straightened out.  Then check that the server and the client can
  resolve each other's hostnames, and that they can ping each other
  (firewalls allowing.)  If you can, put the client on the same
  network as the server and disable all iptables/ufw firewalls, and
  verify it works that way.  Then move the client back to its own
  network and test again.  If it breaks on the other network, it has
  to be a firewall or network issue blocking you.
  
  In my own project here to install Amanda services everywhere, I've
  discovered hosts running undocumented iptables, undocumented
  firewalls, and all sorts of DNS breakages that I've had to clean up
  as I went.
  
  For what it's worth, I had to drop back to using plain old auth=bsd
  for Amanda, not bsdtcp, as some of the clients are so ancient the
  Amanda-client packages they have don't grok bsdtcp yet, so I'm using
  the lcd to get everyone running on a consistent setup.  Once the
  ancients are retired I can upgrade all of them to something modern,
  but until then...
  
  
  --
  Joi Owen
  System Administrator
  Pavlov Media, Inc
 
 I’ve got clients in several flavors.  My server has all of the types of
 xinetd  running,  and can listen to whatever the client is sending. Of
 course,  I have to configure the amanda.conf  and disklist  to request
 of backup of the right type for each client.   Each client can only do
 one kind  (in my experience).
 
No change in the disklist on the server for quite a few days, I had added 
an entry to grab /lib/firmware 2 or 3 weeks ago, before e2fsck gave the / 
partition on the drive a good mauling until it up and died.  New drive, 
new install.  No backup of /etc for either machine. Once I get it working, 
I'll add that to the disklist for both machines.  Hindsight, 20-10 you 
know.  :)
 
Humm, good box has inetutils-inetd installed, bad box does not.  
Installing it will remove xinetd. And now I am back to connection refused.

Anybody got a magic 
 
 for example  (only if you are interested any further)
 AMANDA.CONF:
 define dumptype dailyNormal {
 BDglobal
  # includes auth bsd
 }
 
 define dumptype dailyNormalBSDTCP  {
 BDglobal
 auth “bsdtcp”#overrides the “bsd
 }
 
 define dumptype dailyNormalKRB5  {
 BDglobal
 auth “krb5   #overrides the “bsd”
 }
 
 DISKLIST:
 
 client1/dailyNormal
 client2 /   dailyNormalBSDTCP
 client3/dailyNormalKRB5
 
 
 /ETC/XINETD.D   :I’m sure the filenames don’t matter, but these
 help me:
 
 amanda-dgramfile:
 ##note the   auth=bsdon the server_args line
 
 service amanda
 {
 socket_type = dgram
 protocol= udp
 wait= yes
 user= operator
 group   = root
 server  = /usr/local/libexec/amanda/amandad
 server_args = -auth=bsd amdump amindexd amidxtaped
 disable = no
 groups  = yes
 }
 
 
 amanda-krb5   file:
 ##note the   auth=krb5on the server_args line
 
 service k5amanda
 {
 socket_type = stream
 protocol= tcp
 wait= no
 user= root
 group   = root
 server  = /usr/local/libexec/amanda/amandad
 server_args = -auth=krb5 amdump amindexd amidxtaped
 disable = no
 groups  = yes
 }
 
 
 amanda-stream   file:
 ##note the   auth=bsdtcpon the server_args line
 
 service amanda
 {
 socket_type = stream
 protocol= tcp
 wait= no
 user= operator
 group   = root
 server  = /usr/local/libexec/amanda/amandad
 server_args = -auth=bsdtcp amdump amindexd
 amidxtaped disable = no
 groups  = yes
 }


Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, 

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 15:38:36 Debra S Baddorf did opine
And Gene did reply:
 On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com 
wrote:
  Don't forget to check the logs on the server and the client, see
  /var/log/Amanda/*, find the newest files in there and see what they
  say.
 
 do a  locate(or a find /  -iname “*am*”  )   to find your amanda
 logs.
 
 Joi  puts his in  /var/log/Amanda   apparently.
 I have mine  in   /tmp/amanda   — which I *think*  is the default,  but
 who knows!
 
 Some of the logs start with   “amandad.”  some are “amrecover”  (since
 you’ve got THAT working,  you can look where THOSE logs get put). 
 Some start with   “selfcheck”  but those are the ones you aren’t
 reaching yet.
 
 Deb Baddorf
 Fermilab
None of the return is logfiles, just the executables and docs.  On  both 
machines.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 15:49:47 Debra S Baddorf did opine
And Gene did reply:
  ps auxww | grep net

Except for PID's both machines are identical:
shop:
gene@shop:/etc$  ps auxww | grep net
root13  0.0  0.0  0 0 ?SJul11   0:00 [netns]
root  1128  0.0  0.0   1984   684 ?Ss   Jul11   0:00 /usr/sbin/inetd
gene 15807  0.0  0.0   3352   888 pts/5S+   16:03   0:00 grep 
--color=auto net

lathe:
gene@lathe:/etc$  ps auxww | grep net
root13  0.0  0.0  0 0 ?SJul17   0:00 [netns]
root  4386  0.0  0.0   2132   748 ?S15:45   0:00 
/usr/sbin/inetutils-inetd
gene  4427  0.0  0.0   3352   884 pts/1S+   16:03   0:00 grep 
--color=auto net

Humm,no they are not! but a bare inetd is not now available from the repos.
The shop box apparently has (its a 2 year old install) openbsd-inetd
whereas the lathe has inetdutils-inetd.  Shouldn't they work alike?

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[John Hein]

Gene Heskett gheskett-at-wdtv.com |amusersj-ml0| wrote at 15:07 -0400 on Jul 
18, 2014:
  On Friday 18 July 2014 14:22:48 John Hein did opine
  And Gene did reply:
   Gene Heskett wrote at 12:25 -0400 on Jul 18, 2014:
 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address
 already in use (errno = 98)). service = amanda
  
   More than one xinetd or inetd running?
  
   Maybe some basic background is in order.  The basic operation of
   *inetd is pretty simple, and if you understand the basics, you can
   really solve many of the common issues yourself.
  
   *inetd runs forever listening on the sockets you tell it to
   listen on (as configured by the xinetd or inetd config files).
   When requests (any activity) on that socket come in, it tries
   to run the service that is specified in its configuration.
  
   If something else owns that socket, *inetd can't do its job
   (i.e., can't start the service corresponds to that socket).
  
   If not, then *inetd will spawn off the configured service (amandad
   in amanda's case).
  
   Technically, you don't need *inetd.  You can kick off amandad to run
   on the client some other way (e.g., daemontools, ssh).  But the server
   expects something to be listening on the client when it comes time to
   do the dump.
  
   As others have mentioned, you have to configure things for the right
   type of socket - the configuration of the amanda server (primarily
   in amanda.conf / disklist) and client (typically inetd config and
   amanda-client.conf) should match (see amanda-auth(7) and
   amanda-client.conf(5)).
  
   Here's some other good info so you can maybe help yourself and
   understand better how things work:
  
   http://wiki.zmanda.com/index.php/Quick_start_%28old%29
 
  I just discovered that the failing box did NOT have an /etc/amanda-
  client.conf, so I copied the one from examples and edited it.  But the
  working machine doesn't have one either, so I nuked it. amcheck didn't
  care.

You got that out of my email?

What about the most important bits:

two inetd's running?
and the bind failure?

And the hint to use the background info to try digging on your own a
little.  You're doing lots of things and it seems you don't know why -
just guessing.  That's never a good recipe.

Your xinetd got a bind failure.  That has nothing to do with amanda.
Fix that first.

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 16:16:15 John Hein wrote:
 Gene Heskett gheskett-at-wdtv.com |amusersj-ml0| wrote at 15:07 -0400 on Jul 
 18, 2014:
   On Friday 18 July 2014 14:22:48 John Hein did opine
   
   And Gene did reply:
Gene Heskett wrote at 12:25 -0400 on Jul 18, 2014:
  14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed
  (Address already in use (errno = 98)). service = amanda

More than one xinetd or inetd running?

Maybe some basic background is in order.  The basic operation of
*inetd is pretty simple, and if you understand the basics, you can
really solve many of the common issues yourself.

*inetd runs forever listening on the sockets you tell it to
listen on (as configured by the xinetd or inetd config files).
When requests (any activity) on that socket come in, it tries
to run the service that is specified in its configuration.

If something else owns that socket, *inetd can't do its job
(i.e., can't start the service corresponds to that socket).

If not, then *inetd will spawn off the configured service (amandad
in amanda's case).

Technically, you don't need *inetd.  You can kick off amandad to
run on the client some other way (e.g., daemontools, ssh).  But
the server expects something to be listening on the client when
it comes time to do the dump.

As others have mentioned, you have to configure things for the
right type of socket - the configuration of the amanda server
(primarily in amanda.conf / disklist) and client (typically inetd
config and amanda-client.conf) should match (see amanda-auth(7)
and
amanda-client.conf(5)).

Here's some other good info so you can maybe help yourself and
understand better how things work:

http://wiki.zmanda.com/index.php/Quick_start_%28old%29
   
   I just discovered that the failing box did NOT have an /etc/amanda-
   client.conf, so I copied the one from examples and edited it.  But
   the working machine doesn't have one either, so I nuked it. amcheck
   didn't care.
 
 You got that out of my email?
 
 What about the most important bits:
 
 two inetd's running?
 and the bind failure?
 
 And the hint to use the background info to try digging on your own a
 little.  You're doing lots of things and it seems you don't know why -
 just guessing.  That's never a good recipe.
 
 Your xinetd got a bind failure.  That has nothing to do with amanda.
 Fix that first.

Lets go back to that netstat -na|grep 10080
shop:
tcp0  0 0.0.0.0:10080   0.0.0.0:*   LISTEN
lathe:
tcp6   0  0 :::10080:::*LISTEN

So my guess is that -inet_ipv6 option is killing ipv4 on the lathes machine.

Bingo!!! 
manda Backup Client Hosts Check

ERROR: lathe: [Can't open exclude file /GenesAmandaHelper-0.61/excludes (No 
such file or directory)]
ERROR: lathe: [Can't open exclude file /GenesAmandaHelper-0.61/excludes (No 
such file or directory)]
ERROR: lathe: [Can't open exclude file /GenesAmandaHelper-0.61/excludes (No 
such file or directory)]
ERROR: lathe: [Can't open exclude file /GenesAmandaHelper-0.61/excludes (No 
such file or directory)]
ERROR: lathe: [Can't open exclude file /GenesAmandaHelper-0.61/excludes (No 
such file or directory)]
Client check: 3 hosts checked in 2.107 seconds.  5 problems found.

(brought to you by Amanda 4.0.0alpha.svn.4761)

That subdir, which is part of my own scripting wrapped around amanda,
does not exist on the lathes box. nfs is working so I can fix that
from here with mc.  BRB.  Except I can't, only the /home dirs are nfs
shares, damn.

I'll figure out something.

Thanks, that ipv6 only option in the /etc/init.d/xinetd script was it.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: amrecover works, normal amanda backup, logging connection refused

[Debra S Baddorf]

On Jul 18, 2014, at 3:13 PM, Gene Heskett ghesk...@wdtv.com wrote:

 On Friday 18 July 2014 15:49:47 Debra S Baddorf did opine
 And Gene did reply:
 ps auxww | grep net
 
 Except for PID's both machines are identical:
 shop:
 gene@shop:/etc$  ps auxww | grep net
 root13  0.0  0.0  0 0 ?SJul11   0:00 [netns]
 root  1128  0.0  0.0   1984   684 ?Ss   Jul11   0:00 
 /usr/sbin/inetd
 gene 15807  0.0  0.0   3352   888 pts/5S+   16:03   0:00 grep 
 --color=auto net
 
 lathe:
 gene@lathe:/etc$  ps auxww | grep net
 root13  0.0  0.0  0 0 ?SJul17   0:00 [netns]
 root  4386  0.0  0.0   2132   748 ?S15:45   0:00 
 /usr/sbin/inetutils-inetd
 gene  4427  0.0  0.0   3352   884 pts/1S+   16:03   0:00 grep 
 --color=auto net
 
 Humm,no they are not! but a bare inetd is not now available from the repos.
 The shop box apparently has (its a 2 year old install) openbsd-inetd
 whereas the lathe has inetdutils-inetd.  Shouldn't they work alike?
 
 Cheers, Gene Heskett

Ahh!  OK — inetd   not  xinetd.


Heres an AMANDA specific instruction:

Steps
1. Edit /etc/inetd.conf and add this line to the end of the file, if there is 
any old amanda related lines comment them out:
amanda stream tcp nowait  amandabackup /usr/lib/amanda/amandad amandad 
-auth=bsdtcp amdump amindexd amidxtaped
   my comment:   change  “amandabackup”  to your username
 check that the location is right for you
  change to  “auth=bsd”   if that’s what the 
working node has

2. Edit /etc/services and add this line to the end of the file, if there is any 
old amanda related lines comment them out:
amanda 10080/tcp # amanda backup services

3. Restart the inetd demon and check for errors in the system log files


Deb Baddorf
I defer to anybody else who still uses this,  but if no other suggestions, try 
the above!
I used to use it;  and it does look familiar.

Re: amrecover works, normal amanda backup, logging connection refused

[Gene Heskett]

On Friday 18 July 2014 16:16:15 John Hein did opine
And Gene did reply:
 Gene Heskett gheskett-at-wdtv.com |amusersj-ml0| wrote at 15:07 -0400 on 
Jul 18, 2014:
   On Friday 18 July 2014 14:22:48 John Hein did opine
   
   And Gene did reply:
Gene Heskett wrote at 12:25 -0400 on Jul 18, 2014:
  14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed
  (Address already in use (errno = 98)). service = amanda

More than one xinetd or inetd running?

Maybe some basic background is in order.  The basic operation of
*inetd is pretty simple, and if you understand the basics, you can
really solve many of the common issues yourself.

*inetd runs forever listening on the sockets you tell it to
listen on (as configured by the xinetd or inetd config files).
When requests (any activity) on that socket come in, it tries
to run the service that is specified in its configuration.

If something else owns that socket, *inetd can't do its job
(i.e., can't start the service corresponds to that socket).

If not, then *inetd will spawn off the configured service (amandad
in amanda's case).

Technically, you don't need *inetd.  You can kick off amandad to
run on the client some other way (e.g., daemontools, ssh).  But
the server expects something to be listening on the client when
it comes time to do the dump.

As others have mentioned, you have to configure things for the
right type of socket - the configuration of the amanda server
(primarily in amanda.conf / disklist) and client (typically inetd
config and amanda-client.conf) should match (see amanda-auth(7)
and
amanda-client.conf(5)).

Here's some other good info so you can maybe help yourself and
understand better how things work:

http://wiki.zmanda.com/index.php/Quick_start_%28old%29
   
   I just discovered that the failing box did NOT have an /etc/amanda-
   client.conf, so I copied the one from examples and edited it.  But
   the working machine doesn't have one either, so I nuked it. amcheck
   didn't care.
 
 You got that out of my email?
 
 What about the most important bits:
 
 two inetd's running?
 and the bind failure?
 
 And the hint to use the background info to try digging on your own a
 little.  You're doing lots of things and it seems you don't know why -
 just guessing.  That's never a good recipe.
 
 Your xinetd got a bind failure.  That has nothing to do with amanda.
 Fix that first.

I found it! Call off the Bloodhounds  St. Bernards. :)

I had to reinstall xinetd, then remove the application of the -inet_ipv6 
option the startup script in /etc/init.d was applying to xinetd.

$DIETY damn them all to someplace really hot for trying to make a linux 
version released in 2010 as ipv6 only!  I knew I had fought with this crap 
4 years ago, but my shorter term memory doesn't get refreshed on a short 
enough cycle.  One of the hazards of outliving ALL your enemies.

But I am glad I have, altho that was touch and go about 6 weeks back when 
I found myself just barely aware on the bedroom floor and couldn't draw a 
breath.  Pulmonary embolism, blocked the artery from the right side of my 
heart going into the lungs, came very very close to punching my ticket.  
Blew the right side of my heart up to about 2x normal, but that seems to 
have fixed itself now.  The high priced clot-buster shot worked, so I am 
still here.  Lost some weight too  I feel better right now than I have in 
10 years.  On rat poison for blood thinner of course. ;-)

Thank you ALL for putting up with me when it wasn't even an amanda 
problem, please accept my apologies.

Cheers, Gene Heskett
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Genes Web page http://geneslinuxbox.net:6309/gene
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Re: [Amanda-users] Amanda Backup ssh_security could not find canonical name for

[Chris Hoogendyk]

We don't use wins or winbind on our network and recommend that windows users not try to use it. So, 
I'm not familiar with any details. However, google turns up 
http://www.samba.org/samba/docs/man/manpages-3/winbindd.8.html, which indicates the use of both in 
nsswitch.conf.


We run the smbd portion of samba, but not the nmbd portion on our Sun servers. However, as we move 
into Ubuntu, I've let the Ubuntu packagers have a bit more say so that I can rely on aptitude 
upgrades and not worry any more than necessary about custom local builds or configurations. I've 
managed to figure out a few interesting things about upstart and apparmor so that I can, for 
example, run multiple instances of mysql on different ports; but, with very few exceptions, I have 
taken package software rather than building my own. I did build Amanda, because that is what I am 
used to doing, and I want the freedom of choosing the latest Amanda. But, I'm straying from the 
point - on Ubuntu I have nmbd running. I should look at the local config and see what I can dial 
back to cut/control noise on the network.



On 10/8/13 6:18 PM, Jon LaBadie wrote:

On Tue, Oct 08, 2013 at 03:53:18PM -0400, Chris Hoogendyk wrote:

So, two machines that want to talk to one another (e.g. amanda
server and amanda client) need to know how to address one another.
If you don't have DNS within your private network, and you don't
have fixed IPs assigned (that you know) within the DHCP server, then
it seems to me you are really creating difficulties. Even on my home
network, I set fixed IPs so that I can do things like ssh and rsync
from one Mac to another. Without that, you're dependent on network
chatter and some vendor's auto discovery mechanism. But that's not a
protocol that's going to work with Amanda. You might jerry-rig a
complicated method for auto-discovery and transmitting information
to the Amanda server that gets put into /etc/hosts; but, then, why
not just implement fixed IPs and/or DNS. It seems like the more
traditional and well documented solution.

I use static IP's at home also.  Also my internet router is my DHCP
server and I associate each static IP with its MAC address to ensure
the server does not give out that IP to another host.  (that also
lets me use DHCP and get the same IP)

Samba on the Ubuntu amanda server could act as a WINS server.  But
I don't see anything in docs for the name service switch (nsswitch.conf)
that say it can use a WINS server.  Did I miss it?

Jon


On 10/8/13 3:04 PM, Jon LaBadie wrote:

On Tue, Oct 08, 2013 at 01:22:49PM -0400, Chris Hoogendyk wrote:

Just for reference, if you are running in a private network without
dns lookup, then you should put all the machines you want to backup
into /etc/hosts. That's what I had to do when my Amanda server was
on our private net and had no public address.

Can /etc/hosts be automatically updated if clients get their
IP addresses dynamically with DHCP?

Jon

That doesn't mean you don't have other issues that have to be dealt
with. There is a general trouble shooting page for possible issues
that result in selfcheck request failed --
http://wiki.zmanda.com/index.php/Selfcheck_request_failed.


On 10/8/13 5:08 AM, jefflau wrote:

Dear All,
I was learning on Amanda backup and facing issue for below. I planning using it 
in the workgroup without dns server.

I was Using Ubuntu 12 and installed it by using apt-get, by searching many of 
the issue resolved. Till this stage I do a month can't resolved it.

Hope someone able help me as soon as can


Amanda Backup Client Hosts Check

WARNING: backup: selfcheck request failed: ssh_security could not find 
canonical name for 'backup': Name or service not known
Client check: 1 host checked in 20.581 seconds.  1 problem found.

+--
|This was sent by jef...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--




--
---

Chris Hoogendyk

-
O__   Systems Administrator
   c/ /'_ --- Biology  Geology Departments
  (*) \(*) -- 347 Morrill Science Center
~~ - University of Massachusetts, Amherst

hoogen...@bio.umass.edu

---

Erdös 4

End of included message 


--
---

Chris Hoogendyk

-
   O__   Systems Administrator
  c/ /'_ --- Biology  Geology Departments
 (*) \(*) -- 347 Morrill Science Center
~~ - University of Massachusetts, Amherst

hoogen...@bio.umass.edu

---

Erdös 4

[Amanda-users] Amanda Backup ssh_security could not find canonical name for

[jefflau]

Dear All,
I was learning on Amanda backup and facing issue for below. I planning using it 
in the workgroup without dns server. 

I was Using Ubuntu 12 and installed it by using apt-get, by searching many of 
the issue resolved. Till this stage I do a month can't resolved it.

Hope someone able help me as soon as can


Amanda Backup Client Hosts Check

WARNING: backup: selfcheck request failed: ssh_security could not find 
canonical name for 'backup': Name or service not known
Client check: 1 host checked in 20.581 seconds.  1 problem found.

+--
|This was sent by jef...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: [Amanda-users] Amanda Backup ssh_security could not find canonical name for

[Debra S Baddorf]

Can you send the amanda.conf   file?We need a little more information here.
[ If you are already discussing this with somebody,  then never mind! ]
Deb


On Oct 8, 2013, at 4:08 AM, jefflau amanda-for...@backupcentral.com
 wrote:

 Dear All,
 I was learning on Amanda backup and facing issue for below. I planning using 
 it in the workgroup without dns server. 
 
 I was Using Ubuntu 12 and installed it by using apt-get, by searching many of 
 the issue resolved. Till this stage I do a month can't resolved it.
 
 Hope someone able help me as soon as can
 
 
 Amanda Backup Client Hosts Check
 
 WARNING: backup: selfcheck request failed: ssh_security could not find 
 canonical name for 'backup': Name or service not known
 Client check: 1 host checked in 20.581 seconds.  1 problem found.
 
 +--
 |This was sent by jef...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 

Re: [Amanda-users] Amanda Backup ssh_security could not find canonical name for

[Jon LaBadie]

On Tue, Oct 08, 2013 at 01:22:49PM -0400, Chris Hoogendyk wrote:
 Just for reference, if you are running in a private network without
 dns lookup, then you should put all the machines you want to backup
 into /etc/hosts. That's what I had to do when my Amanda server was
 on our private net and had no public address.

Can /etc/hosts be automatically updated if clients get their
IP addresses dynamically with DHCP?

Jon
 
 That doesn't mean you don't have other issues that have to be dealt
 with. There is a general trouble shooting page for possible issues
 that result in selfcheck request failed --
 http://wiki.zmanda.com/index.php/Selfcheck_request_failed.
 
 
 On 10/8/13 5:08 AM, jefflau wrote:
 Dear All,
 I was learning on Amanda backup and facing issue for below. I planning using 
 it in the workgroup without dns server.
 
 I was Using Ubuntu 12 and installed it by using apt-get, by searching many 
 of the issue resolved. Till this stage I do a month can't resolved it.
 
 Hope someone able help me as soon as can
 
 
 Amanda Backup Client Hosts Check
 
 WARNING: backup: selfcheck request failed: ssh_security could not find 
 canonical name for 'backup': Name or service not known
 Client check: 1 host checked in 20.581 seconds.  1 problem found.
 
 +--
 |This was sent by jef...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
 
 -- 
 ---
 
 Chris Hoogendyk
 
 -
O__   Systems Administrator
   c/ /'_ --- Biology  Geology Departments
  (*) \(*) -- 347 Morrill Science Center
 ~~ - University of Massachusetts, Amherst
 
 hoogen...@bio.umass.edu
 
 ---
 
 Erdös 4
 End of included message 

-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (609) 477-8330 (C)

Re: [Amanda-users] Amanda Backup ssh_security could not find canonical name for

[Jon LaBadie]

On Tue, Oct 08, 2013 at 03:53:18PM -0400, Chris Hoogendyk wrote:
 So, two machines that want to talk to one another (e.g. amanda
 server and amanda client) need to know how to address one another.
 If you don't have DNS within your private network, and you don't
 have fixed IPs assigned (that you know) within the DHCP server, then
 it seems to me you are really creating difficulties. Even on my home
 network, I set fixed IPs so that I can do things like ssh and rsync
 from one Mac to another. Without that, you're dependent on network
 chatter and some vendor's auto discovery mechanism. But that's not a
 protocol that's going to work with Amanda. You might jerry-rig a
 complicated method for auto-discovery and transmitting information
 to the Amanda server that gets put into /etc/hosts; but, then, why
 not just implement fixed IPs and/or DNS. It seems like the more
 traditional and well documented solution.

I use static IP's at home also.  Also my internet router is my DHCP
server and I associate each static IP with its MAC address to ensure
the server does not give out that IP to another host.  (that also
lets me use DHCP and get the same IP)

Samba on the Ubuntu amanda server could act as a WINS server.  But
I don't see anything in docs for the name service switch (nsswitch.conf)
that say it can use a WINS server.  Did I miss it?

Jon
 
 
 On 10/8/13 3:04 PM, Jon LaBadie wrote:
 On Tue, Oct 08, 2013 at 01:22:49PM -0400, Chris Hoogendyk wrote:
 Just for reference, if you are running in a private network without
 dns lookup, then you should put all the machines you want to backup
 into /etc/hosts. That's what I had to do when my Amanda server was
 on our private net and had no public address.
 Can /etc/hosts be automatically updated if clients get their
 IP addresses dynamically with DHCP?
 
 Jon
 That doesn't mean you don't have other issues that have to be dealt
 with. There is a general trouble shooting page for possible issues
 that result in selfcheck request failed --
 http://wiki.zmanda.com/index.php/Selfcheck_request_failed.
 
 
 On 10/8/13 5:08 AM, jefflau wrote:
 Dear All,
 I was learning on Amanda backup and facing issue for below. I planning 
 using it in the workgroup without dns server.
 
 I was Using Ubuntu 12 and installed it by using apt-get, by searching many 
 of the issue resolved. Till this stage I do a month can't resolved it.
 
 Hope someone able help me as soon as can
 
 
 Amanda Backup Client Hosts Check
 
 WARNING: backup: selfcheck request failed: ssh_security could not find 
 canonical name for 'backup': Name or service not known
 Client check: 1 host checked in 20.581 seconds.  1 problem found.
 
 +--
 |This was sent by jef...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
 
 
 -- 
 ---
 
 Chris Hoogendyk
 
 -
O__   Systems Administrator
   c/ /'_ --- Biology  Geology Departments
  (*) \(*) -- 347 Morrill Science Center
 ~~ - University of Massachusetts, Amherst
 
 hoogen...@bio.umass.edu
 
 ---
 
 Erdös 4
 End of included message 

-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (609) 477-8330 (C)

Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

[Leo Subscriptions]

Have installed the vendor's drivers following this link and the README
in the tar.

https://bbs.archlinux.org/viewtopic.php?id=101836


Will let you know how it goes.



On Sat, 2011-07-23 at 20:32 -0600, Trever L. Adams wrote:

 I'm almost positive the problem is the network card. I would suggest
 trying a tg3 or an e1000 based card. it fixed my problems.
 -- 
 Sent from my Android phone with K-9 Mail. Please excuse my brevity.
 
 
 Leo Subscriptions llsub...@zudiewiener.com wrote:
 
 Following are some of details of my system
 
 Motherboadr: Gigabyte GA-MA790FXT-UD5P
 CPU: AMD Phentom II X4 (4 CPUs)
 Memeory: 4BG
 Disks: All Western Digital drives, with 2TB Raid 1, 2 TB disk
 used for backup storage, 1TB  holding, all SMART enabled and
 monitored
 Network: Realtek RTL811/8168B PCI Express Gigabit Controller
 (rev 02)
 
 
 
 On Sat, 2011-07-23 at 08:39 -0600, Trever L. Adams wrote:
 
  On 7/23/2011 8:05 AM, Leo Subscriptions wrote: 
  
   I'm running Ubuntu 11.04 (64 bit) and experience the
   occasional 'system freeze'. By freeze I mean a complete
   freeze of the system (ie. no system log entries, but
   system [ie. disks] is still running).
   
   I have reported this is an Ubuntu bug a while ago, but
   have noticed that the three times this has happened an
   amanda backup was running. I even moved the time of the
   backup to prove the point
   
   I'm running a RAID1, with one of my folders encrypted.
   Both the holding disk and final backup disk are single
   disks.
   
   My question is if anybody could think that amanada could
   be the contributing factor for the failure and if so how.
   
   
  
  By chance are you using r8169? If so, that may be it. It was
  causing all sorts of hard locks and soft locks.
  
  Trever
 
 

Can amanda backup cause/contribute to a system 'freeze' in Linux

[Leo Subscriptions]

I'm running Ubuntu 11.04 (64 bit) and experience the occasional 'system
freeze'. By freeze I mean a complete freeze of the system (ie. no system
log entries, but system [ie. disks] is still running).

I have reported this is an Ubuntu bug a while ago, but have noticed that
the three times this has happened an amanda backup was running. I even
moved the time of the backup to prove the point

I'm running a RAID1, with one of my folders encrypted. Both the holding
disk and final backup disk are single disks.

My question is if anybody could think that amanada could be the
contributing factor for the failure and if so how.

Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

[Trever L. Adams]

On 7/23/2011 8:05 AM, Leo Subscriptions wrote:
 I'm running Ubuntu 11.04 (64 bit) and experience the occasional
 'system freeze'. By freeze I mean a complete freeze of the system (ie.
 no system log entries, but system [ie. disks] is still running).

 I have reported this is an Ubuntu bug a while ago, but have noticed
 that the three times this has happened an amanda backup was running. I
 even moved the time of the backup to prove the point

 I'm running a RAID1, with one of my folders encrypted. Both the
 holding disk and final backup disk are single disks.

 My question is if anybody could think that amanada could be the
 contributing factor for the failure and if so how.


By chance are you using r8169? If so, that may be it. It was causing all
sorts of hard locks and soft locks.

Trever


signature.asc
Description: OpenPGP digital signature

Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

[gene heskett]

On Saturday, July 23, 2011 10:55:03 AM Trever L. Adams did opine:

 On 7/23/2011 8:05 AM, Leo Subscriptions wrote:
  I'm running Ubuntu 11.04 (64 bit) and experience the occasional
  'system freeze'. By freeze I mean a complete freeze of the system (ie.
  no system log entries, but system [ie. disks] is still running).
  
  I have reported this is an Ubuntu bug a while ago, but have noticed
  that the three times this has happened an amanda backup was running. I
  even moved the time of the backup to prove the point
  
  I'm running a RAID1, with one of my folders encrypted. Both the
  holding disk and final backup disk are single disks.
  
  My question is if anybody could think that amanada could be the
  contributing factor for the failure and if so how.
 
 By chance are you using r8169? If so, that may be it. It was causing all
 sorts of hard locks and soft locks.
 
 Trever

If that's not it, I would check with the drive makers site and see if there 
is a firmware update available, checking all the drives.

Generally its a matter of downloading a small cd image for each drive, and 
rebooting to it once put on a cd.  But be aware that some such cd's are 
only capable of updating one drive per reboot.  About a year back, I had 2 
such drives that needed updated, the first one it updated was fine, but it 
scrambled the UUID's and partition names of the second drive pretty badly.

The data was all still there, but the data that was in /var was now in /opt 
etc etc.  Nothing precious even if it was my boot drive, as I had good 
amanda backups, so I did a bare necessity's install of a new distro (PCLOS) 
I wanted to try on that disk, pulled enough amanda from another drive  
recovered my data.

That is what amanda is all about.

Cheers, gene
-- 
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
There is only one way to console a widow.  But remember the risk.
-- Robert Heinlein

Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

[Jon LaBadie]

On Sun, Jul 24, 2011 at 12:05:50AM +1000, Leo Subscriptions wrote:
 I'm running Ubuntu 11.04 (64 bit) and experience the occasional 'system
 freeze'. By freeze I mean a complete freeze of the system (ie. no system
 log entries, but system [ie. disks] is still running).
 
 I have reported this is an Ubuntu bug a while ago, but have noticed that
 the three times this has happened an amanda backup was running. I even
 moved the time of the backup to prove the point
 
 I'm running a RAID1, with one of my folders encrypted. Both the holding
 disk and final backup disk are single disks.
 
 My question is if anybody could think that amanada could be the
 contributing factor for the failure and if so how.
 

The workload caused by amanda may stress some parts of the system.
I'd look at memory with memtest86+.  The heavy load may also be
revealing defects in the raid/encryption software or hardware.

Jon
-- 
Jon H. LaBadie  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

[Leo Subscriptions]

Following are some of details of my system

Motherboadr: Gigabyte GA-MA790FXT-UD5P
CPU: AMD Phentom II X4 (4 CPUs)
Memeory: 4BG
Disks: All Western Digital drives, with 2TB Raid 1, 2 TB disk used for
backup storage, 1TB  holding, all SMART enabled and monitored
Network: Realtek RTL811/8168B PCI Express Gigabit Controller (rev 02)



On Sat, 2011-07-23 at 08:39 -0600, Trever L. Adams wrote:

 On 7/23/2011 8:05 AM, Leo Subscriptions wrote: 
 
  I'm running Ubuntu 11.04 (64 bit) and experience the occasional
  'system freeze'. By freeze I mean a complete freeze of the system
  (ie. no system log entries, but system [ie. disks] is still
  running).
  
  I have reported this is an Ubuntu bug a while ago, but have noticed
  that the three times this has happened an amanda backup was running.
  I even moved the time of the backup to prove the point
  
  I'm running a RAID1, with one of my folders encrypted. Both the
  holding disk and final backup disk are single disks.
  
  My question is if anybody could think that amanada could be the
  contributing factor for the failure and if so how.
  
  
 
 By chance are you using r8169? If so, that may be it. It was causing
 all sorts of hard locks and soft locks.
 
 Trever

Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

[Trever L. Adams]

I'm almost positive the problem is the network card. I would suggest trying a 
tg3 or an e1000 based card. it fixed my problems.
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Leo Subscriptions llsub...@zudiewiener.com wrote:

Following are some of details of my system

Motherboadr: Gigabyte GA-MA790FXT-UD5P
CPU: AMD Phentom II X4 (4 CPUs)
Memeory: 4BG
Disks: All Western Digital drives, with 2TB Raid 1, 2 TB disk used for backup 
storage, 1TB  holding, all SMART enabled and monitored
Network: Realtek RTL811/8168B PCI Express Gigabit Controller (rev 02)



On Sat, 2011-07-23 at 08:39 -0600, Trever L. Adams wrote:

On 7/23/2011 8:05 AM, Leo Subscriptions wrote: 

I'm running Ubuntu 11.04 (64 bit) and experience the occasional 'system 
freeze'. By freeze I mean a complete freeze of the system (ie. no system log 
entries, but system [ie. disks] is still running).

I have reported this is an Ubuntu bug a while ago, but have noticed that the 
three times this has happened an amanda backup was running. I even moved the 
time of the backup to prove the point

I'm running a RAID1, with one of my folders encrypted. Both the holding disk 
and final backup disk are single disks.

My question is if anybody could think that amanada could be the contributing 
factor for the failure and if so how.


By chance are you using r8169? If so, that may be it. It was causing all sorts 
of hard locks and soft locks.

Trever

Amanda Backup USB?

[Christ Schlacta]

I'm evaluating possible solutions for Drop in USB backup.  as an
existing amanda user, I was interested by the possibility of having
amanda run a backup of a flash drive whenever it's connected.  I've
got a few simple requirements for this backup operation.  1) a backup
should happen whenever a Known usb drive is connected.  I have a
good idea how to do this with a generic UDEV rule and a script.  2) an
option to backup a drive in either block level (for encrypted
drives/filesystems) or file level mode.  amanda supports both,
though how to enable that option in configuration settings I'm a bit
unsure, but it doesn't seem insurmountable.  3) a simple web interface
(Again, I can whip something up), and 4) non-interactive operation.
with a script, most things can be done non-interactively for backups.
5) Backup mode.  when a user goes to a website and picks their drive
out of the list and specifies Backup mode,  they should get the
version of files the specified back from the drive, optionally backing
up first.  6) when a backup or restore is done, users should get a
notification in their inbox that it's done.  this is again ahndled by
a no-longer trivial script called from udev.

5 is where I forsee the most issues.  firstly, can a restore be run
completely non-interactively like that, on an entire directory tree,
recursively?  I've never had to do ti yet, so I don't recall.  The
interface will be a smidge tricky, but doable.
Managing the the number of configuration sets needed to maintain this
system, even automatedly seems like it might be prone to errors.

What does the amanda list think, is this using a sledge hammer to push
in a thumbtack, or is amanda well suited to this task, and the issues
just need to be more fleshed out?  I ahve a few alternatives,
including using simple OS tools to backup to a directory that's in
turn backed up by amanda with other data, and looking for some
pre-existing solution, which I haven't yet found.

Re: Error while installing amanda-backup-client on RHEL 5 64-bit

[Julian C. Dunn]

On 11/17/2010 08:23 AM, Yogesh Hasabnis wrote:

Hi All,

I am trying to install amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm
on an RHEL 5 64-bit system. But I get an error as follows:

# rpm -ivh --test amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm
error: Failed dependencies:
libtermcap.so.2 is needed by amanda-backup_client-2.6.1p2-1.rhel5.x86_64

The libtermcap-devel-2.0.8-46.1.x86_64.rpm package which contains the
libtermcap.so.2 has already been installed. Still the problem is
observed. Can you kindly suggest any solution or workaround to this
problem ?

I checked the archives for a similar question. But the suggestions given
there didn't work for me.


Did you try yum localinstall 
amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm instead? This will 
automatically resolve any dependencies.


Could be an architecture issue -- maybe you have i386 versions of the 
termcap libraries installed by accident.


- Julian

Re: Error while installing amanda-backup-client on RHEL 5 64-bit

[Robert Heller]

At Wed, 24 Nov 2010 23:17:43 -0500 Julian C. Dunn li...@aquezada.com wrote:

 
 On 11/17/2010 08:23 AM, Yogesh Hasabnis wrote:
  Hi All,
 
  I am trying to install amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm
  on an RHEL 5 64-bit system. But I get an error as follows:
 
  # rpm -ivh --test amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm
  error: Failed dependencies:
  libtermcap.so.2 is needed by amanda-backup_client-2.6.1p2-1.rhel5.x86_64
 
  The libtermcap-devel-2.0.8-46.1.x86_64.rpm package which contains the
  libtermcap.so.2 has already been installed. Still the problem is
  observed. Can you kindly suggest any solution or workaround to this
  problem ?
 
  I checked the archives for a similar question. But the suggestions given
  there didn't work for me.
 
 Did you try yum localinstall 
 amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm instead? This will 
 automatically resolve any dependencies.
 
 Could be an architecture issue -- maybe you have i386 versions of the 
 termcap libraries installed by accident.

Or (more likely) the OP has *only* the i386 (or only the x86_64)
versions of the termcap libraries, when he should have both the i386
AND the x86_64 versions:

sauron.deepsoft.com% rpm -q --queryformat 
%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n libtermcap
libtermcap-2.0.8-46.1.x86_64
libtermcap-2.0.8-46.1.i386

One should not need the -devel versions unless one is building
something. 

 
 - Julian
 
   
 

-- 
Robert Heller -- 978-544-6933 / hel...@deepsoft.com
Deepwoods Software-- http://www.deepsoft.com/
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments


   

Re: Error while installing amanda-backup-client on RHEL 5 64-bit

[Yogesh Hasabnis]

Hello,

They have already been installed.

# rpm -qa | grep termcap
libtermcap-2.0.8-46.1
libtermcap-devel-2.0.8-46.1
termcap-5.5-1.20060701.1

Thanks in advance,
Yogesh

--- On Fri, 11/19/10, Paddy Sreenivasan pa...@zmanda.com wrote:

From: Paddy Sreenivasan pa...@zmanda.com
Subject: Re: Error while installing amanda-backup-client on RHEL 5 64-bit
To: Yogesh Hasabnis yhmai...@yahoo.co.in
Cc: amanda-users amanda-users@amanda.org
Date: Friday, November 19, 2010, 7:09 AM

I think you should install termcap and libtermcap packages. Use yum.

Paddy

On Wed, Nov 17, 2010 at 11:09 PM, Yogesh Hasabnis yhmai...@yahoo.co.in wrote:


Hi All,

I would appreciate your suggestions if any.

Thanks in advance,
Yogesh

--- On Wed, 11/17/10, Yogesh Hasabnis yhmai...@yahoo.co.in wrote:


From: Yogesh Hasabnis yhmai...@yahoo.co.in
Subject: Error while installing amanda-backup-client on RHEL 5 64-bit

To: amanda-users@amanda.org
Date: Wednesday, November 17, 2010, 6:53 PM


Hi All,

I am trying to install amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm on an 
RHEL 5 64-bit system. But I get an error as follows:

# rpm -ivh --test 
 amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm 
error: Failed dependencies:
    libtermcap.so.2 is needed by amanda-backup_client-2.6.1p2-1.rhel5.x86_64


The libtermcap-devel-2.0.8-46.1.x86_64.rpm package which contains the 
libtermcap.so.2 has already been installed. Still the problem is observed. Can 
you kindly  suggest any solution or workaround to this problem ? 


I checked the archives for a similar question. But the suggestions given there 
didn't work for
 me.

Thanks in advance,
Yogesh Hasabnis



  


  


-- 
Amanda http://amanda.zmanda.com 
ZRM for MySQL http://www.zmanda.com/backup-mysql.html





  

Re: Error while installing amanda-backup-client on RHEL 5 64-bit

[Paddy Sreenivasan]

I think you should install termcap and libtermcap packages. Use yum.

Paddy

On Wed, Nov 17, 2010 at 11:09 PM, Yogesh Hasabnis yhmai...@yahoo.co.inwrote:

 Hi All,

 I would appreciate your suggestions if any.

 Thanks in advance,
 Yogesh

 --- On *Wed, 11/17/10, Yogesh Hasabnis yhmai...@yahoo.co.in* wrote:


 From: Yogesh Hasabnis yhmai...@yahoo.co.in
 Subject: Error while installing amanda-backup-client on RHEL 5 64-bit
 To: amanda-users@amanda.org
 Date: Wednesday, November 17, 2010, 6:53 PM


 Hi All,

 I am trying to install amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm on
 an RHEL 5 64-bit system. But I get an error as follows:

 # rpm -ivh --test  amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm
 error: Failed dependencies:
 libtermcap.so.2 is needed by
 amanda-backup_client-2.6.1p2-1.rhel5.x86_64

 The libtermcap-devel-2.0.8-46.1.x86_64.rpm package which contains the
 libtermcap.so.2 has already been installed. Still the problem is observed.
 Can you kindly  suggest any solution or workaround to this problem ?

 I checked the archives for a similar question. But the suggestions given
 there didn't work for me.

 Thanks in advance,
 Yogesh Hasabnis





-- 
Amanda http://amanda.zmanda.com
ZRM for MySQL http://www.zmanda.com/backup-mysql.html

Error while installing amanda-backup-client on RHEL 5 64-bit

[Yogesh Hasabnis]

Hi All,

I am trying to install amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm on an 
RHEL 5 64-bit system. But I get an error as follows:

# rpm -ivh --test  amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm 
error: Failed dependencies:
    libtermcap.so.2 is needed by amanda-backup_client-2.6.1p2-1.rhel5.x86_64

The libtermcap-devel-2.0.8-46.1.x86_64.rpm package which contains the 
libtermcap.so.2 has already been installed. Still the problem is observed. Can 
you kindly  suggest any solution or workaround to this problem ? 

I checked the archives for a similar question. But the suggestions given there 
didn't work for me.

Thanks in advance,
Yogesh Hasabnis



  

Re: Error while installing amanda-backup-client on RHEL 5 64-bit

[Yogesh Hasabnis]

Hi All,

I would appreciate your suggestions if any.

Thanks in advance,
Yogesh

--- On Wed, 11/17/10, Yogesh Hasabnis yhmai...@yahoo.co.in wrote:

From: Yogesh Hasabnis yhmai...@yahoo.co.in
Subject: Error while installing amanda-backup-client on RHEL 5 64-bit
To: amanda-users@amanda.org
Date: Wednesday, November 17, 2010, 6:53 PM

Hi All,

I am trying to install amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm on an 
RHEL 5 64-bit system. But I get an error as follows:

# rpm -ivh --test  amanda-backup_client-2.6.1p2-1.rhel5.x86_64.rpm 
error: Failed dependencies:
    libtermcap.so.2 is needed by amanda-backup_client-2.6.1p2-1.rhel5.x86_64

The libtermcap-devel-2.0.8-46.1.x86_64.rpm package which contains the 
libtermcap.so.2 has already been installed. Still the problem is observed. Can 
you kindly  suggest any solution or workaround to this problem ? 

I checked the archives for a similar question. But the suggestions given there 
didn't work for
 me.

Thanks in advance,
Yogesh Hasabnis



  


  

amanda backup of virtual machine under citrix

[Brian Cuttler]

We are running amanda server on Solaris 10 and the
client on a citrix box and trying to backup a virtual
machine on citrix.

Our config on the server is identical to similar setup
we have on another network

define dumptype zwc {
auto bsdtcp
maxdumps 1
compress client fast
programDUMP
}

but when we run amcheck against the client we get

amcheck-clients: amanda/tcp unknown protocol

A snoop of the server shows the following traffic between the
server and client pair

bunsen - 150.142.85.127 NBT NS Query Request for WCQA02[0], Success.

We seem to be missing something in our config but I'm not finding
the key in the wiki. What should I be looking for ?

thanks,

Brian
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amanda backup of virtual machine under citrix

[Dustin J. Mitchell]

On Tue, May 25, 2010 at 12:05 PM, Brian Cuttler br...@wadsworth.org wrote:
 We seem to be missing something in our config but I'm not finding
 the key in the wiki. What should I be looking for ?

I'm guessing that amanda/tcp isn't in your services db?  On most
systems, that's /etc/services, but on Sun it might be via NIS or
something.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: amanda backup of virtual machine under citrix

[Brian Cuttler]

Dustin,

Genious!

Of course we had upd defined in /etc/services but we
neglected to add a second definition on the same socket
id for upd.

It was of course present on the parallel system that was
working for PC but non-citrix clients.

thank you,

Brian


On Tue, May 25, 2010 at 12:22:17PM -0500, Dustin J. Mitchell wrote:
 On Tue, May 25, 2010 at 12:05 PM, Brian Cuttler br...@wadsworth.org wrote:
  We seem to be missing something in our config but I'm not finding
  the key in the wiki. What should I be looking for ?
 
 I'm guessing that amanda/tcp isn't in your services db?  On most
 systems, that's /etc/services, but on Sun it might be via NIS or
 something.
 
 Dustin
 
 -- 
 Open Source Storage Engineer
 http://www.zmanda.com
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amanda backup of virtual machine under citrix

[Chris Hoogendyk]

Dustin J. Mitchell wrote:

On Tue, May 25, 2010 at 12:05 PM, Brian Cuttler br...@wadsworth.org wrote:
  

We seem to be missing something in our config but I'm not finding
the key in the wiki. What should I be looking for ?



I'm guessing that amanda/tcp isn't in your services db?  On most
systems, that's /etc/services, but on Sun it might be via NIS or
something.



I've got it in /etc/services on Solaris 10 u7 SPARC.

But, Brian's been running Amanda on Solaris 10 for quite a while, and, I 
think, just adding the citrix virtual system as a client. So, it would 
seem the message is with reference to the specific client, and the 
configuration issue would be on that client.


I don't mean to question Dustin. Maybe Brian has set up a new Amanda 
server and missed this step? But, maybe the server tried to connect and 
got turned back because of unknown protocol at the other end?



--
---

Chris Hoogendyk

-
  O__   Systems Administrator
 c/ /'_ --- Biology  Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~ - University of Massachusetts, Amherst 


hoogen...@bio.umass.edu

--- 


Erdös 4

Re: amanda backup of virtual machine under citrix

[Dustin J. Mitchell]

On Tue, May 25, 2010 at 12:44 PM, Chris Hoogendyk
hoogen...@bio.umass.edu wrote:
 I don't mean to question Dustin

I rather enjoy being questioned, so don't worry about that!

This was a guess, and apparently I was correct this time around.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: amanda backup of virtual machine under citrix

[Brian Cuttler]

Chris,

No and Yes.

I have been running an amanda server on this particular system
for a while, but its not the system where I have been running
an amanda server that included PC/windows clients.

The system that has been working includes in /etc/services
the following.

 grep amand /etc/services
amanda  10080/udp   # amanda
amanda  10080/tcp   # amanda
amandaidx   10082/tcp   # amanda
amidxtape   10083/tcp   # amanda

Where the system I was adding the citrix based vitual
clients to had not included the amanda 10080/upd line
and had not previously had windows nor citrix clients.

Dispite some consolidation and the move to larger amanda server
platforms (including Sun X4500) and larger tape systems (SL24/LTO4
jukeboxeswe, and even one x4500 with VTapes) we still have some 20+
amanda servers on multiple platform types and even the newer
ones on similar servers are somewhat different in their config.

This was a failure in my process as the 10080/upd must have
been a question I asked about prior to today and wasn't so much
specific to the client and to the authentication type/server pair.

thank you,

Brian




On Tue, May 25, 2010 at 01:44:28PM -0400, Chris Hoogendyk wrote:
 
 
 Dustin J. Mitchell wrote:
 On Tue, May 25, 2010 at 12:05 PM, Brian Cuttler br...@wadsworth.org 
 wrote:
   
 We seem to be missing something in our config but I'm not finding
 the key in the wiki. What should I be looking for ?
 
 
 I'm guessing that amanda/tcp isn't in your services db?  On most
 systems, that's /etc/services, but on Sun it might be via NIS or
 something.
 
 
 I've got it in /etc/services on Solaris 10 u7 SPARC.
 
 But, Brian's been running Amanda on Solaris 10 for quite a while, and, I 
 think, just adding the citrix virtual system as a client. So, it would 
 seem the message is with reference to the specific client, and the 
 configuration issue would be on that client.
 
 I don't mean to question Dustin. Maybe Brian has set up a new Amanda 
 server and missed this step? But, maybe the server tried to connect and 
 got turned back because of unknown protocol at the other end?
 
 
 -- 
 ---
 
 Chris Hoogendyk
 
 -
   O__   Systems Administrator
  c/ /'_ --- Biology  Geology Departments
 (*) \(*) -- 140 Morrill Science Center
 ~~ - University of Massachusetts, Amherst 
 
 hoogen...@bio.umass.edu
 
 --- 
 
 Erd?s 4
 
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

[Amanda-users] Amanda backup on SL24

[ga jimenez55]

Dustin J. Mitchell wrote:
 On Thu, Apr 30, 2009 at 10:06 AM, ga jimenez55
 amanda-forum  at  backupcentral.com wrote:
 
  amtape BackupSL24 update (or show)
  amtape: scanning all 5 slots in tape-changer rack:
  amtape: slot   5: Error reading Amanda header
  amtape: slot   2: Error reading Amanda header
  
 
 Do those tapes have Amanda headers on them?
 
 Dustin
 
 -- 
 Open Source Storage Engineer
 http://www.zmanda.com


I solved this problem label tape

+--
|This was sent by tavog...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

[Amanda-users] Amanda backup on SL24

[ga jimenez55]

i have this  problem when i use those command i have this error

amtape BackupSL24 update (or show)
amtape: scanning all 5 slots in tape-changer rack:
amtape: slot   5: Error reading Amanda header
amtape: slot   2: Error reading Amanda header

I am trying that amanda read the tape's barcode of the SL24 

/opt/csw/sbin/mtx -f /dev/scsi/changer/c1t5d1 inquiry
Product Type: Medium Changer
Vendor ID: 'HP  '
Product ID: 'MSL G3 Series   '
Revision: 'D.00'
Attached Changer: No

amanda have a specific command for med-changer, in this example i do not show 
load drive

/opt/csw/sbin/mtx -f /dev/scsi/changer/c1t5d1 status
 Storage Changer /dev/scsi/changer/c1t5d1:1 Drives, 24 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
 Storage Element 1:Full :VolumeTag=APL4
 Storage Element 2:Full :VolumeTag=AP0004L4
 Storage Element 3:Full :VolumeTag=AP0001L4
 Storage Element 4:Full :VolumeTag=AP0002L4
 Storage Element 5:Full :VolumeTag=AP0003L4
 Storage Element 6:Empty
 Storage Element 7:Empty
 Storage Element 8:Empty
 Storage Element 9:Empty
 Storage Element 10:Empty
 Storage Element 11:Empty
 Storage Element 12:Empty
 Storage Element 13:Empty
 Storage Element 14:Empty
 Storage Element 15:Empty
 Storage Element 16:Empty
 Storage Element 17:Empty
 Storage Element 18:Empty
 Storage Element 19:Empty
 Storage Element 20:Empty
 Storage Element 21:Empty
 Storage Element 22:Empty
 Storage Element 23:Empty
 Storage Element 24:Empty

+--
|This was sent by tavog...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: [Amanda-users] Amanda backup on SL24

[Dustin J. Mitchell]

On Thu, Apr 30, 2009 at 10:06 AM, ga jimenez55
amanda-fo...@backupcentral.com wrote:
 amtape BackupSL24 update (or show)
 amtape: scanning all 5 slots in tape-changer rack:
 amtape: slot   5: Error reading Amanda header
 amtape: slot   2: Error reading Amanda header

Do those tapes have Amanda headers on them?

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

[Amanda-users] Amanda backup problem - a tape error occured

[mandaillou]

Thanks for your prompt replies.

Dustin J. Mitchell wrote:
 On Fri, Dec 19, 2008 at 4:06 AM, mandaillou
 amanda-forum  at  backupcentral.com wrote:
 
  On the forum, I found people facing the same problem and the error was 
  related to the tapecycle. Mine is 12 and I have 12 reusable tapes.
  
 
 Right -- if you're doing 14 backups (2 weeks, every day), you're not
 going to fit that on 12 tapes.  You need 15 tapes.
 

I wasn't clear enough. I run a backup every working day (monday to friday), 
which means 10 backup per cycle so I guess 12 tapes is enough.


Dustin J. Mitchell wrote:
 
 Furthermore, it looks like you don't have enough holding-disk space:
 
  FAILED [no more holding disk space]
  
 which is causing your dumps to go straight to tape, which isn't very 
 efficient.
 

I confess I haven't configurated this part. I understood (maybe I'm wrong) that 
it would work anyway.


Dustin J. Mitchell wrote:
 
 Furthermore, your tape only wrote a bit over 1G:
 
  DailySet-05   2:11  1140224K   28.8 1 0
  
 which is 28% of the length you specified in your tapetype definition.
 Is there a problem with the tape?  Or is the tapetype definition
 incorrect?
 

I'm using 4Go tapes. They are all new and I have the same problem for every 
tape. I've used amtapetype for amanda.conf configuration.
Below is the extract from amanda.conf related to the tapetype definition.

 define tapetype HP-C1537A{
 length 3868 mbytes
 filemark 225 kbytes
 speed 491 kps
 }
 



Jean-Louis Martineau wrote:
 mandaillou wrote:
 Quote:
 NOTES:
 taper: tape DailySet-05 kb 1783648 fm 2 writing file: No space left on
 device
 
 The tape got full after 1783648 was written, you need bigger tape.
 

The capacity of all my tapes is 4Go. I feel like Amanda doesn't overwrite the 
tape but just fill the tape until it's full and then exit with the previous 
error message : The tape got full after 1783648 was written, you need bigger 
tape.

PS:can anybody tell me why I can't see my original post but only the replies ?

+--
|This was sent by mandail...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: [Amanda-users] Amanda backup problem - a tape error occured

[Jean-Louis Martineau]

Are you sure of the size of your tape? 4Gb is with compression or not, 
Do your data are compressible or not, are you using software compression?


Jean-Louis

mandaillou wrote:

Thanks for your prompt replies.

Dustin J. Mitchell wrote:
  

On Fri, Dec 19, 2008 at 4:06 AM, mandaillou
amanda-forum  at  backupcentral.com wrote:



On the forum, I found people facing the same problem and the error was related 
to the tapecycle. Mine is 12 and I have 12 reusable tapes.

  

Right -- if you're doing 14 backups (2 weeks, every day), you're not
going to fit that on 12 tapes.  You need 15 tapes.




I wasn't clear enough. I run a backup every working day (monday to friday), 
which means 10 backup per cycle so I guess 12 tapes is enough.


Dustin J. Mitchell wrote:
  

Furthermore, it looks like you don't have enough holding-disk space:



FAILED [no more holding disk space]

  

which is causing your dumps to go straight to tape, which isn't very efficient.




I confess I haven't configurated this part. I understood (maybe I'm wrong) that 
it would work anyway.


Dustin J. Mitchell wrote:
  

Furthermore, your tape only wrote a bit over 1G:



DailySet-05   2:11  1140224K   28.8 1 0

  

which is 28% of the length you specified in your tapetype definition.
Is there a problem with the tape?  Or is the tapetype definition
incorrect?




I'm using 4Go tapes. They are all new and I have the same problem for every 
tape. I've used amtapetype for amanda.conf configuration.
Below is the extract from amanda.conf related to the tapetype definition.

  

define tapetype HP-C1537A{
length 3868 mbytes
filemark 225 kbytes
speed 491 kps
}






Jean-Louis Martineau wrote:
  

mandaillou wrote:
Quote:
NOTES:
taper: tape DailySet-05 kb 1783648 fm 2 writing file: No space left on
device

The tape got full after 1783648 was written, you need bigger tape.




The capacity of all my tapes is 4Go. I feel like Amanda doesn't overwrite the tape but 
just fill the tape until it's full and then exit with the previous error message : 
The tape got full after 1783648 was written, you need bigger tape.

PS:can anybody tell me why I can't see my original post but only the replies ?

+--
|This was sent by mandail...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


  

[Amanda-users] Amanda backup problem - a tape error occured

[mandaillou]

Hi everybody :D
This is my first post in this forum and maybe not the last.
I'm a newbie using Amanda and I'm facing a problem with my backup.
I'm working with Amanda 2.5.2p1.1 under RHEL 3.
My backup strategy is really simple :
- full backup every day on 1 tape
- dumpcycle : 2 weeks
- tapecycle : 12 tapes

The first cycle went ok but then when a tape has to be overwritten, I get the 
following message :


 These dumps were to tape DailySet-05.
 *** A TAPE ERROR OCCURRED: [No more writable valid tape found].
 Some dumps may have been left in the holding disk.
 Run amflush to flush them to tape.
 The next tape Amanda expects to use is: DailySet-06.
 
 FAILURE AND STRANGE DUMP SUMMARY:
   asmtls2.sda-akka.net  /opt/cvsroot/lev 0
 FAILED [out of tape]
   asmtls2.sda-akka.net  /opt/cvsroot/lev 0
 FAILED [data write: Broken pipe]
   asmtls2.sda-akka.net  /opt/cvsroot/lev 0
 FAILED [dump to tape failed]
   asmtls1.sda-akka.net  /home/fer/   lev 1
 FAILED [no more holding disk space]
   asmtls1.sda-akka.net  /UserBig/CVS_WORKSPACES/fer_cvs_workspaces/  lev 1
 FAILED [no more holding disk space]
 
 
 STATISTICS:
   Total   Full  Incr.
       
 Estimate Time (hrs:min)0:00
 Run Time (hrs:min) 2:58
 Dump Time (hrs:min)2:11   2:11   0:00
 Output Size (meg)1113.5 1113.50.0
 Original Size (meg)  1113.5 1113.50.0
 Avg Compressed Size (%) -- -- --
 Filesystems Dumped1  1  0
 Avg Dump Rate (k/s)   145.0  145.0--
 
 Tape Time (hrs:min)2:11   2:11   0:00
 Tape Size (meg)  1113.5 1113.50.0
 Tape Used (%)  28.8   28.80.0
 Filesystems Taped 1  1  0
 
 Chunks Taped  0  0  0
 Avg Tp Write Rate (k/s)   144.9  144.9--
 
 USAGE BY TAPE:
   Label Time  Size  %NbNc
   DailySet-05   2:11  1140224K   28.8 1 0
 
 
 FAILED AND STRANGE DUMP DETAILS:
 
 /--  asmtls2.sda-akka.net /opt/cvsroot/ lev 0 FAILED [data write: Broken
 pipe]
 sendbackup: start [asmtls2.sda-akka.net:/opt/cvsroot/ level 0]
 sendbackup: info BACKUP=/bin/tar
 sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
 sendbackup: info end
 \
 
 
 NOTES:
   taper: tape DailySet-05 kb 1783648 fm 2 writing file: No space left on
 device
 
 
 DUMP SUMMARY:
 DUMPER STATS   TAPER
 STATS
 HOSTNAME   DISK   L ORIG-KB  OUT-KB  COMP%  MMM:SS   KB/s MMM:SS
 KB/s
 --- -
 -
 asmtls1.sd -r_cvs_workspaces/ 1 FAILED
 
 asmtls1.sd /UserBig/fer/  0 1140200 1140224--   131:06  144.9 131:06
 144.9
 asmtls1.sd /home/fer/ 1 FAILED
 
 asmtls2.sd /opt/cvsroot/  0 FAILED
 
 
 (brought to you by Amanda version 2.5.2p1)
 

On the forum, I found people facing the same problem and the error was related 
to the tapecycle. Mine is 12 and I have 12 reusable tapes.
Here is the tapelist from today, after the backup failure of last night:

 20081219 DailySet-05 reuse
 20081217 DailySet-04 reuse
 20081216 DailySet-03 reuse
 20081211 DailySet-02 reuse
 20081210 DailySet-01 reuse
 20081209 DailySet-12 reuse
 20081204 DailySet-11 reuse
 20081202 DailySet-10 reuse
 20081201 DailySet-09 reuse
 20081128 DailySet-08 reuse
 20081127 DailySet-07 reuse
 20081126 DailySet-06 reuse
 


From what I see, the tape 05 was the one to use and the rule the tape can't 
be used again before (tapecycle-1) other tapes are used, is respected.
So I don't have any clue how to solve this problem.
Thanks in advance for your help and sorry for the english mistakes.

Sylvain

+--
|This was sent by mandail...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: [Amanda-users] Amanda backup problem - a tape error occured

[Dustin J. Mitchell]

On Fri, Dec 19, 2008 at 4:06 AM, mandaillou
amanda-fo...@backupcentral.com wrote:
 On the forum, I found people facing the same problem and the error was 
 related to the tapecycle. Mine is 12 and I have 12 reusable tapes.

Right -- if you're doing 14 backups (2 weeks, every day), you're not
going to fit that on 12 tapes.  You need 15 tapes.

Furthermore, it looks like you don't have enough holding-disk space:
  FAILED [no more holding disk space]
which is causing your dumps to go straight to tape, which isn't very efficient.

Furthermore, your tape only wrote a bit over 1G:
   DailySet-05   2:11  1140224K   28.8 1 0
which is 28% of the length you specified in your tapetype definition.
Is there a problem with the tape?  Or is the tapetype definition
incorrect?

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com

Re: [Amanda-users] Amanda backup problem - a tape error occured

[Jean-Louis Martineau]

mandaillou wrote:

NOTES:
  taper: tape DailySet-05 kb 1783648 fm 2 writing file: No space left on
device


The tape got full after 1783648 was written, you need bigger tape.

Re: [Amanda-users] Question corrupt amanda backup / tape speed / etc..help!

[Dustin J. Mitchell]

On Tue, Oct 28, 2008 at 1:39 PM, rory_f [EMAIL PROTECTED] wrote:
 We managed to up our speed of dumping and writing a whole lot by using a 
 holding disk, which is great. However, the data we wrote, around 245gb, 
 failed a amcheckdump and i couldnt, therefore, not amrestore anything.

What was the output of amcheckdump?

 After the amtapetest, i was given an output of this:

 define tapetype ibm #123;
 nbsp; nbsp; comment just produced by tapetype prog #40;hardware 
 compression off#41;
 nbsp; nbsp; length 402432 mbytes
 nbsp; nbsp; filemark 0 kbytes
 nbsp; nbsp; speed 57497 kps
 #125;

Note that amtapetype overwrites the tape..

Also, it's very hard to read the above with all of the HTML entities
in it.  The logfile you excerpted was unreadable.

dustin

-- 
Storage Software Engineer
http://www.zmanda.com

[Amanda-users] Question corrupt amanda backup / tape speed / etc..help!

[rory_f]

This is an edited version of a previous post


Hi,

We managed to up our speed of dumping and writing a whole lot by using a 
holding disk, which is great. However, the data we wrote, around 245gb, failed 
a amcheckdump and i couldnt, therefore, not amrestore anything.

After the amtapetest, i was given an output of this:

define tapetype ibm {
comment just produced by tapetype prog (hardware compression off)
length 402432 mbytes
filemark 0 kbytes
speed 57497 kps
}

However, it says in the amreport we wrote to tape at :
Avg Tp Write Rate (k/s) 90801.790801.7-- 
Here is some of our amdump output:
diver: result time 6482.541 from taper: PARTDONE 00-2 AmaTor-004 5 41943040 
[sec 449.501801 kb 41943040 kps 93310.059952]
driver: state time 6950.318 free kps: 10 space: 719002550 taper: writing 
idle-dumpers: 1 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers
driver: interface-state time 6950.318 if default: free 10
driver: hdisk-state time 6950.318 hdisk 0: free 719002550 dumpers 0
driver: result time 6950.332 from taper: PARTDONE 00-2 AmaTor-004 6 
41943040 [sec 466.669805 kb 41943040 kps 89877.338432]
driver: state time 7023.335 free kps: 10 space: 719002550 taper: writing 
idle-dumpers: 1 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers
driver: interface-state time 7023.335 if default: free 10
driver: hdisk-state time 7023.335 hdisk 0: free 719002550 dumpers 0
driver: result time 7023.350 from taper: PARTDONE 00-2 AmaTor-004 7 5813290 
[sec 71.901664 kb 5813290 kps 80850.562791]
driver: state time 7023.350 free kps: 10 space: 719002550 taper: writing 
idle-dumpers: 1 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers
driver: interface-state time 7023.350 if default: free 10
driver: hdisk-state time 7023.350 hdisk 0: free 719002550 dumpers 0


How can this be? our holding disk is a sata1, 1tb disk. That write rate is 
above what sata1 can give data out at, right? is this the reason for our data 
corruption?

What else could it be? Do you need anymoer info to help diagnose this? We're 
gonna hopefully try with a sata2 disk soon to see if that makes any difference. 
The tapespeed variable in amanda.conf, to my understanding, would not allow me 
to write at 9k~. Nor would the speed of a sata1  disk.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--

Re: [Amanda-users] Question corrupt amanda backup / tape speed / etc..help!

[Dustin J. Mitchell]

Amanda writes data to tape as quickly as the tape drive will allow.
The tapespeed is not currently used.

The data may be in local cache, explaining some of the high speed.  I
don't know SATA-1 rates off the top of my head to know if that's too
fast.

Whatever goes on, data corruption should not result.  I'm interested
to hear what sort of corruption you're seeing.

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com

Amanda backup for Lustre file systems

[Ram TK Krishnamurthy]

Hi
Are there users on the list using Amanda to backup Lustre file systems?
I would be interested in connecting to understand some of the details.


Thanks
tk


-

Ram TK Krishnamurthy
[EMAIL PROTECTED]

Re: AMANDA backup fails silently with taper: Received signal 1

[Francis Galiegue]

Le Friday 18 January 2008 17:27:52, vous avez écrit :
 In this case, I am starting amdump test by running:

 $amdump periodic

 I did exit the shell, so perhaps the  command is not enough to
 prevent the SIGUP from being processed?


It is not. Putting a process in the background does NOT close stdin, stdout 
and stderr and therefore they still point to the controlling terminal.

zsh knows about !, which reopens all three to /dev/null (I think) but you 
mentioned screen: that's the right way to do it imho.

-- 
Francis Galiegue, [EMAIL PROTECTED] - Ingénieur système
[ATTENTION : CHANGEMENT DE COORDONNÉES !]
One2team - 42 Av. Raymond Poincaré - 75116 PARIS CEDEX
+33683877875, +33178945552

Re: AMANDA backup fails silently with taper: Received signal 1

[Jordan Desroches]

In this case, I am starting amdump test by running:

$amdump periodic

I did exit the shell, so perhaps the  command is not enough to  
prevent the SIGUP from being processed?


Thanks,

Jordan

On Jan 18, 2008, at 10:48 AM, John E Hein wrote:


Jordan Desroches wrote at 10:09 -0500 on Jan 18, 2008:

Greetings all,

In experimenting with AMANDA I've been running into a problem where
I'll start a backup, everything will go swimmingly, and sometime down
the line, the backup is stopped, and no AMANDA processes are running.
No failure report is sent, the backup just stops. When I run a manual
amreport, there is a suspicious message taper: Received signal 1.
This error does not happen all the time. In this case, I had blown
away all the log, index and gnutar-lists files to try to start  
afresh.

Any ideas what maybe causing this?

My amanda system:

Ubuntu 7.10 server install
Amanda 2.5.2p1
GNU Tar 1.18
IBM LTO-3 drive
netapp filer nfs mounted. network: gig-e, MTU9000, rsize and wsize
both 32768

I've attached the amreport results and the taper debug file.


Signal 1 is SIGHUP.

The shell, if it exits, will send SIGHUP to processes under it's
control unless they have detached from the shell as process group
leader.

Ways around this include nohup(1), daemon(8) (not available on all
OS's), run in the background in a subshell... among others.

Usually people start amdump in a cron job, and cron probably detaches
its jobs so they are parented by init(8) or parented by a forked cron
process which is parented by init (OS-dependent, but typical).  It's
not typical (I won't say it's not possible since I haven't checked the
code for this behavior) that init or cron is sending SIGHUP.

Anyway, SIGHUP appears to be getting sent to taper by something.  I am
not aware of anything in amanda sends SIGHUP, but someone here who has
looked will supply the correct information on that point I'm sure.

How do you start amdump?


Another cause of random process death is running out of memory/swap.
Some OS's will kill processes when under low memory pressure.
Typically that will be a SIGTERM (15) and/or SIGKILL (9) that is sent,
however.  I'm not sure about Linux's behavior in this situation, but
examining resource usage (with a script that records vmstat(8) /
top(1) types of info) may be useful.

Re: AMANDA backup fails silently with taper: Received signal 1

[John E Hein]

Jordan Desroches wrote at 10:09 -0500 on Jan 18, 2008:
  Greetings all,
  
  In experimenting with AMANDA I've been running into a problem where  
  I'll start a backup, everything will go swimmingly, and sometime down  
  the line, the backup is stopped, and no AMANDA processes are running.  
  No failure report is sent, the backup just stops. When I run a manual  
  amreport, there is a suspicious message taper: Received signal 1.  
  This error does not happen all the time. In this case, I had blown  
  away all the log, index and gnutar-lists files to try to start afresh.  
  Any ideas what maybe causing this?
  
  My amanda system:
  
  Ubuntu 7.10 server install
  Amanda 2.5.2p1
  GNU Tar 1.18
  IBM LTO-3 drive
  netapp filer nfs mounted. network: gig-e, MTU9000, rsize and wsize  
  both 32768
  
  I've attached the amreport results and the taper debug file.

Signal 1 is SIGHUP.

The shell, if it exits, will send SIGHUP to processes under it's
control unless they have detached from the shell as process group
leader.

Ways around this include nohup(1), daemon(8) (not available on all
OS's), run in the background in a subshell... among others.

Usually people start amdump in a cron job, and cron probably detaches
its jobs so they are parented by init(8) or parented by a forked cron
process which is parented by init (OS-dependent, but typical).  It's
not typical (I won't say it's not possible since I haven't checked the
code for this behavior) that init or cron is sending SIGHUP.

Anyway, SIGHUP appears to be getting sent to taper by something.  I am
not aware of anything in amanda sends SIGHUP, but someone here who has
looked will supply the correct information on that point I'm sure.

How do you start amdump?


Another cause of random process death is running out of memory/swap.
Some OS's will kill processes when under low memory pressure.
Typically that will be a SIGTERM (15) and/or SIGKILL (9) that is sent,
however.  I'm not sure about Linux's behavior in this situation, but
examining resource usage (with a script that records vmstat(8) /
top(1) types of info) may be useful.

Re: AMANDA backup fails silently with taper: Received signal 1

[Jordan Desroches]

John,

After looking up what you suggested, I'm almost entirely sure you're  
right. If I start the job manually, I'll use nohup, disown or screen.  
Thanks so much for your help!


Jordan

On Jan 18, 2008, at 10:48 AM, John E Hein wrote:


Jordan Desroches wrote at 10:09 -0500 on Jan 18, 2008:

Greetings all,

In experimenting with AMANDA I've been running into a problem where
I'll start a backup, everything will go swimmingly, and sometime down
the line, the backup is stopped, and no AMANDA processes are running.
No failure report is sent, the backup just stops. When I run a manual
amreport, there is a suspicious message taper: Received signal 1.
This error does not happen all the time. In this case, I had blown
away all the log, index and gnutar-lists files to try to start  
afresh.

Any ideas what maybe causing this?

My amanda system:

Ubuntu 7.10 server install
Amanda 2.5.2p1
GNU Tar 1.18
IBM LTO-3 drive
netapp filer nfs mounted. network: gig-e, MTU9000, rsize and wsize
both 32768

I've attached the amreport results and the taper debug file.


Signal 1 is SIGHUP.

The shell, if it exits, will send SIGHUP to processes under it's
control unless they have detached from the shell as process group
leader.

Ways around this include nohup(1), daemon(8) (not available on all
OS's), run in the background in a subshell... among others.

Usually people start amdump in a cron job, and cron probably detaches
its jobs so they are parented by init(8) or parented by a forked cron
process which is parented by init (OS-dependent, but typical).  It's
not typical (I won't say it's not possible since I haven't checked the
code for this behavior) that init or cron is sending SIGHUP.

Anyway, SIGHUP appears to be getting sent to taper by something.  I am
not aware of anything in amanda sends SIGHUP, but someone here who has
looked will supply the correct information on that point I'm sure.

How do you start amdump?


Another cause of random process death is running out of memory/swap.
Some OS's will kill processes when under low memory pressure.
Typically that will be a SIGTERM (15) and/or SIGKILL (9) that is sent,
however.  I'm not sure about Linux's behavior in this situation, but
examining resource usage (with a script that records vmstat(8) /
top(1) types of info) may be useful.

Re: AMANDA backup fails silently with taper: Received signal 1

[Jordan Desroches]

John,

I was using:
$amdump periodic 

After looking up what you suggested, I'm almost entirely sure you're  
right. If I start the job manually, I'll use nohup, disown or screen.  
Thanks so much for your help!


Jordan

On Jan 18, 2008, at 10:48 AM, John E Hein wrote:


Jordan Desroches wrote at 10:09 -0500 on Jan 18, 2008:

Greetings all,

In experimenting with AMANDA I've been running into a problem where
I'll start a backup, everything will go swimmingly, and sometime down
the line, the backup is stopped, and no AMANDA processes are running.
No failure report is sent, the backup just stops. When I run a manual
amreport, there is a suspicious message taper: Received signal 1.
This error does not happen all the time. In this case, I had blown
away all the log, index and gnutar-lists files to try to start  
afresh.

Any ideas what maybe causing this?

My amanda system:

Ubuntu 7.10 server install
Amanda 2.5.2p1
GNU Tar 1.18
IBM LTO-3 drive
netapp filer nfs mounted. network: gig-e, MTU9000, rsize and wsize
both 32768

I've attached the amreport results and the taper debug file.


Signal 1 is SIGHUP.

The shell, if it exits, will send SIGHUP to processes under it's
control unless they have detached from the shell as process group
leader.

Ways around this include nohup(1), daemon(8) (not available on all
OS's), run in the background in a subshell... among others.

Usually people start amdump in a cron job, and cron probably detaches
its jobs so they are parented by init(8) or parented by a forked cron
process which is parented by init (OS-dependent, but typical).  It's
not typical (I won't say it's not possible since I haven't checked the
code for this behavior) that init or cron is sending SIGHUP.

Anyway, SIGHUP appears to be getting sent to taper by something.  I am
not aware of anything in amanda sends SIGHUP, but someone here who has
looked will supply the correct information on that point I'm sure.

How do you start amdump?


Another cause of random process death is running out of memory/swap.
Some OS's will kill processes when under low memory pressure.
Typically that will be a SIGTERM (15) and/or SIGKILL (9) that is sent,
however.  I'm not sure about Linux's behavior in this situation, but
examining resource usage (with a script that records vmstat(8) /
top(1) types of info) may be useful.

Re: cleaning tapes and integration into Amanda backup scheme?

[Chris Hoogendyk]

Craig Dewick wrote:

On Mon, 22 Oct 2007, Olivier Nicole wrote:


My Sun L9 array has told me it needs a cleaning tape run. I have one so
that's no problem but what I'd like to know is if there is a way that
Amanda can receive info from the tape drive about the requirement for
cleaning and co-ordinate cleaning tape runs as part of the overall 
backup

stragegy?


My strategy, all human based, is to have the cleaning tape on the pile
of the next set of 6 tapes to be used.

I have my tapes pool divided into 3 sets of 6, once I have run through
the current set, I move the stack to the back and come up with a new
stack, on top of which is the cleaning tape.


My L9 tape array has DLT-4 tapes in the first 8 slots, and today I've 
put a brand new cleaning tape into the 9th slot. There's nothing in my 
tape server's amanda.conf file relating to cleaning tapes, so I'm 
wondering where in the Amanda config schema the info about location of 
cleaning tapes needs to be. Does Amanda itself need to know, or does 
mtx need to know directly? 


I have a 16 slot library. I configured Amanda daily backups to work with 
slots 1-15, so it would never look at slot 16. Originally, I had the 
cleaning tape in 16, but I've only had to use it once in a year, and 
that was when I had a faulty tape get caught in the drive. So, I've just 
removed it, and I use the 16th slot for archive runs and other special 
cases.


From just scanning the wiki with google, it appears that the chg 
scripts have the capacity to call a cleaning tape, and that can be 
defined for the scripts, but it isn't built into Amanda per se. With 
modern drives, it shouldn't be needed much and my inclination is that I 
would like to be in manual control of it. If the drive is misbehaving 
and seems to need cleaning, I don't want an automated process to keep it 
out of sight (out of mind) until it fails and needs major work. That's 
just my opinion.



---

Chris Hoogendyk

-
  O__   Systems Administrator
 c/ /'_ --- Biology  Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~ - University of Massachusetts, Amherst 


[EMAIL PROTECTED]

--- 


Erdös 4

Re: cleaning tapes and integration into Amanda backup scheme?

[Craig Dewick]

On Mon, 22 Oct 2007, Olivier Nicole wrote:


My Sun L9 array has told me it needs a cleaning tape run. I have one so
that's no problem but what I'd like to know is if there is a way that
Amanda can receive info from the tape drive about the requirement for
cleaning and co-ordinate cleaning tape runs as part of the overall backup
stragegy?


My strategy, all human based, is to have the cleaning tape on the pile
of the next set of 6 tapes to be used.

I have my tapes pool divided into 3 sets of 6, once I have run through
the current set, I move the stack to the back and come up with a new
stack, on top of which is the cleaning tape.


My L9 tape array has DLT-4 tapes in the first 8 slots, and today I've put 
a brand new cleaning tape into the 9th slot. There's nothing in my tape 
server's amanda.conf file relating to cleaning tapes, so I'm wondering 
where in the Amanda config schema the info about location of cleaning 
tapes needs to be. Does Amanda itself need to know, or does mtx need to 
know directly?


Craig.

--
Post by Craig Dewick (tm). Web @ http://lios.apana.org.au/~cdewick;.
Email 2 [EMAIL PROTECTED]. SunShack @ http://www.sunshack.org;
Galleries @ http://www.sunshack.org/gallery2;. Also lots of tech data, etc.
Sun Microsystems webring at http://n.webring.com/hub?ring=sunmicrosystemsu;.

Re: can amanda backup symlink?

[Chris Hoogendyk]

Frank Smith wrote:

fedora wrote:
  

Hi huys..

I have 2 situations:

1) default directory for MySQL is /var/lib/mysql. If this directory is link
to /var2/db/mysql and if I put /var/lib/mysql in disklist, can amanda do
backup? I think this should be can backup. May I know which directory is the
best to put in disklist for this case?



Amanda will back up the link, but you probably want it to back up the data,
so you should use /var2/db/mysql as your disklist entry. Or you may want
both, so if you are rebuilding the entire server you would get the link
as well, but in that case you might want most or all of /var and not just
the database link.
  

2) how about this one. In /var/lib/mysql has databases but certain databases
in linking to /var3/mysql like:

lrwxrwxrwx1 root root   42 May 16  2007 AngelClub -
/var3/mysql/AngelClub
drwx--2 mysqlmysql4096 Nov 13 11:55 BabyMobile
drwx--2 mysqlmysql4096 Nov 13 11:55 BestClub

If I put only /var/lib/mysql in disklist, can amanda backup for /var3/mysql?
Or should add both /var/lib/mysql and /var3/mysql in disklist? Please
advise.



You would need both.  /var/lib/mysql would pick up the BabyMobile and
BestClub databases, but would only record the link to AngelClub and not
the database itself, so you would have to add /var3/mysql/AngelClub to
get that database.



This requires just a bit of clarification.

Amanda calls on native tools to do the backups. On Solaris, people 
typically choose to use ufsdump. On Linux, people typically choose to 
use gnutar. So the question depends on the behavior of those tools and 
possibly the parameters Amanda calls them with, though I doubt Amanda 
would call gnutar with --dereference and --create.


ufsdump will faithfully backup a partition. That is, it backs up links 
as links and restores them as links. It backs up mount points as mount 
points and doesn't follow them into other mounted partitions. It deals 
properly with weird things such as doors. So, to paraphrase, when you 
ask ufsdump to do a partition, you get the partition, the whole 
partition, and nothing but the partition.


I'm less familiar with all the gnuances of gnutar, and some people will 
substitute star or a wrapper of their own. But gnutar will typically 
backup a symlink as a symlink, though it has parameters that can be 
tweaked to do otherwise. Gnutar also typically follows mount points into 
other mounted partitions, though I'm going to take a guess that Amanda 
passes it the parameter that tells it not to do that. It would seem 
contrary to the concept of the way DLE's are configured to have gnutar 
expanding mount points.


Aside from the above, I go along with Frank's response.

In addition, you should read the backup reports. Check the sizes of your 
partitions with `df -k` and then compare those with what the Amanda 
reports as the amount of data having been backed up. See if they make 
sense. And do trial recoveries to confirm that what you think got backed 
up really did get backed up and that you can recover it.


Also, since you are doing mySQL, be sure you are taking into account the 
peculiarities of backing up databases.



---

Chris Hoogendyk

-
  O__   Systems Administrator
 c/ /'_ --- Biology  Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~ - University of Massachusetts, Amherst 


[EMAIL PROTECTED]

--- 


Erdös 4