Amanda-Users

new tape not found in rack & network services goes down after runing amdump

2005-03-17 09:22:12
Subject: new tape not found in rack & network services goes down after runing amdump
From: Jack$on <jackson AT ukrcard.com DOT ua>
To: amanda-users AT amanda DOT org
Date: Thu, 17 Mar 2005 16:05:03 +0200
Hello amanda-users,

sorry for my importunity...
but another 2 problem appeared...

I'm had 2 amanda config -- daily & weekly backups.

Policies of both of them -- full dump (or tar) of my partitions or
directories.

I have HP autoloader 1/8, Ultrium 320 tape...
I'm configure at Amanda my changer, it working good... but i have
troubles with switching from one config to another :(.

Amanda labes on tapes:

Daily1
Daily2
Daily3
Daily4
Daily5
Not Labeled
Weekly1
Weekly2

for example: i run weekly backup at tape Weekly1.
after yhis I try run daily backup, and a had this errors from amcheck:

amcheck-server: fatal slot 7: Unloading Data Transfer Element into Storage 
Element 7...mtx: Request Sense: Long Report=yes
ERROR: new tape not found in rack
       (expecting a new tape)

and errors from reports:

*** A TAPE ERROR OCCURRED: [new tape not found in rack].
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: a new tape.
The next new tape already labelled is: Daily3.

after run amflush, again i had errors:
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: a new tape.
The next new tape already labelled is: Daily3.

And only after I'm manually unload tape 7 from changer,
load tape 3, and run amflush dump on tape run correctly...

my changer config:

#cat /etc/amanda/daily/changer.conf
firstslot=1
lastslot=6
cleanslot=-1
driveslot=0
autoclean=0
autocleancount=99
offline_before_unload=0
poll_drive_ready=3
max_drive_wait=120
initial_poll_delay=5

#cat /etc/amanda/weekly/changer.conf
firstslot=7
lastslot=8
cleanslot=-1
driveslot=0
autoclean=0
autocleancount=99
offline_before_unload=0
poll_drive_ready=3
max_drive_wait=120
initial_poll_delay=5

It's my first problem...

another problem -- after I'm run both of my backups (weekly, or daily)
my network services on Amanda server station gone to the strange
state...
sshd, sendmail, inetd -- both didn't work, and only after SIGHUP came
work correctly...

at system messages i have:

Mar 13 03:05:13 lib /kernel: pid 26007 (sendmail), uid 0: exited on signal 11
Mar 13 03:35:11 lib /kernel: pid 26029 (sendmail), uid 0: exited on signal 11
Mar 13 03:35:11 lib /kernel: pid 26031 (sendmail), uid 0: exited on signal 11
.....
from sendmail daemon

and

Mar 13 12:17:29 lib sshd[26448]: error: ssh_dss_sign: sign failed
Mar 13 12:17:29 lib sshd[26448]: fatal: mm_answer_sign: key_sign failed
Mar 13 12:17:37 lib sshd[26450]: error: ssh_dss_sign: sign failed
Mar 13 12:17:37 lib sshd[26450]: fatal: mm_answer_sign: key_sign failed
...

from ssh daemon.

may be my configuration at amanda.conf allocated too much resources to
amdump?

can you help me? I can't find how to resolve it at amanda.org, or
google :(.  

-- 
Best regards,
 Jack$on                          mailto:jackson AT ukrcard.com DOT ua


<Prev in Thread] Current Thread [Next in Thread>