Amanda-Users

Re: R: Illegal slot?

2005-12-30 08:34:36
Subject: Re: R: Illegal slot?
From: Gene Heskett <gene.heskett AT verizon DOT net>
To: amanda-users AT amanda DOT org
Date: Fri, 30 Dec 2005 08:23:43 -0500
On Friday 30 December 2005 08:06, Montagni, Giovanni wrote:
>> -----Messaggio originale-----
>> Da: owner-amanda-users AT amanda DOT org
>> [mailto:owner-amanda-users AT amanda DOT org] Per conto di Gene Heskett
>> Inviato: venerdì 30 dicembre 2005 12.58
>> A: amanda-users AT amanda DOT org
>> Oggetto: Re: Illegal slot?
>>
>> On Thursday 29 December 2005 02:57, Montagni, Giovanni wrote:
>> >Yesterday I've setup a new config with chg-manual and
>>
>> runtapes 2.  Both
>>
>> >yesterday and tonight, amverifyrun had failed with this error:
>> >
>> >Tapes:
>> >Errors found:
>> >amtape: could not load slot <none>: /usr/lib/amanda/chg-manual:
>> >illegal slot: -1
>> >
>> >amverify bkalfa-all
>> >Thu Dec 29 02:52:01 CET 2005
>> >
>> >Loading -1 slot...
>> >** Error loading slot -1
>> >amtape: could not load slot <none>: /usr/lib/amanda/chg-manual:
>> >illegal slot: -1
>> >
>> >This error is strange because if i specify slot number on
>>
>> the command
>>
>> >line all works (it want to check the second tape that it wasn't
>> >written but this is not a problem...). I've checked
>>
>> changer-status and
>>
>> >changer-status-slot files but it's  all ok. I suppose there's a
>> > file somewhere where amverify (o
>> > amverifyrun) take the (wrong) current slot number...
>> >
>> >How can i fix this problem? I would run amverify from cron...
>>
>> I don't know if running it from cron is a good idea, because
>> the backup
>> may not be finished & closed out when cron wants to run it.
>> I do that
>> from the same script invocation that does the backup so that the
>> sequencing is correct, and the backup is well and truely done
>> before the amverify is performed.  It works well here.
>
>Sorry i explained things so bad. The configuration is slighty
> different. Amverify and amdump is not executed directly from cron,
> but cron run a script with those two commands in sequence. So when
> backup has finished, verify starts and hung up with illegal slot
> error.

Ahh, then see the calling syntax required for amverify.  The docs were 
quite obtuse at the time I was doing this, and may still be. You will 
have to maintain in your script, the starting slot as a local var, and 
pass that to the amverify pass invocation from your script.  The lack 
of that is why its returning a -1 slot I believe.

I'd post mine, but its both long, and to me, butt ugly due to the 
methods I used to extract some of the local vars used, and now 
somewhat double uglied because the tape stuff is still there but 
commented since I'm using vtapes now.  I don't think it would help the 
confusion factor, but contact me off list if you'd like to see it.

>> >Thanks to all of you.
>> >
>> >Giovanni
>> >
>> >
>> >------------------------------------------------------------------
>> >--- - Il contenuto della presente comunicazione è riservato e
>> > destinato esclusivamente ai destinatari indicati. Nel caso in cui
>> > sia
>>
>> ricevuto
>>
>> >da persona diversa dal destinatario sono proibite la diffusione,
>> > la distribuzione e la copia. Nel caso riceveste la presente per
>>
>> errore,
>>
>> >Vi preghiamo di informarci e di distruggerlo e/o cancellarlo dal
>> >Vostro computer, senza utilizzare i dati contenuti.
>> >
>> >La presente comunicazione (comprensiva dei documenti allegati) non
>> >avrà valore di proposta contrattuale e/o accettazione di proposte
>> >provenienti dal destinatario, nè rinuncia o riconoscimento
>>
>> di  diritti,
>>
>> >debiti e/o crediti, nè sarà impegnativa, qualora non sia
>>
>> sottoscritto
>>
>> >successivo accordo da chi può validamente obbligarci.  Non
>> > deriverà alcuna responsabilità precontrattuale a ns. carico, se 
>> > la
>>
>> presente non
>>
>> >sia seguita da contratto sottoscritto dalle parti.
>> > -----------------------------------------------------------------
>> >--- -- The contents of the present communication is strictly
>>
>> confidential
>>
>> >and reserved solely to the referred addressees. In the event was
>> >received by person different from the addressee, it is
>>
>> forbidden the
>>
>> >diffusion, distribution and copy. In the event you have received
>> > it mistakenly we ask you to inform us and to destroy and/or to
>>
>> delete  it
>>
>> >by your computer, without using the data herein contained.
>> >
>> >The present message (eventual annexes inclusive) shall not be
>> >considered any contractual proposal and/or acceptance of
>>
>> offer  coming
>>
>> >from the addressee, nor waiver neither recognizance of
>>
>> rights, debts
>>
>> >and/or credits, and it shall not be binding, when it  is not
>>
>> executed a
>>
>> >subsequent agreement by person who could lawfully  represent us.
>> > No pre-contractual liability shall derive to us, when  the
>> > present communication is not followed by any binding agreement 
>> > between the parties.
>>
>> --
>> Cheers, Gene
>> People having trouble with vz bouncing email to me should add
>> the word 'online' between the 'verizon', and the dot which
>> bypasses vz's stupid bounce rules.  I do use spamassassin
>> too. :-) Yahoo.com and AOL/TW attorneys please note,
>> additions to the above message by Gene Heskett are: Copyright
>> 2005 by Maurice Eugene Heskett, all rights reserved.
>
>Thanks again :-)
>
>
>---------------------------------------------------------------------
>- Il contenuto della presente comunicazione è riservato e destinato
> esclusivamente ai destinatari indicati. Nel caso in cui sia ricevuto
> da persona diversa dal destinatario sono proibite la diffusione, la
> distribuzione e la copia. Nel caso riceveste la presente per errore,
> Vi preghiamo di informarci e di distruggerlo e/o cancellarlo dal
> Vostro computer, senza utilizzare i dati contenuti.
>
>La presente comunicazione (comprensiva dei documenti allegati) non
> avrà valore di proposta contrattuale e/o accettazione di proposte
> provenienti dal destinatario, nè rinuncia o riconoscimento di
> diritti, debiti e/o crediti, nè sarà impegnativa, qualora non sia
> sottoscritto successivo accordo da chi può validamente obbligarci.
> Non deriverà alcuna responsabilità precontrattuale a ns. carico, se
> la presente non sia seguita da contratto sottoscritto dalle parti.
> --------------------------------------------------------------------
>-- The contents of the present communication is strictly confidential
> and reserved solely to the referred addressees. In the event was
> received by person different from the addressee, it is forbidden the
> diffusion, distribution and copy. In the event you have received it
> mistakenly we ask you to inform us and to destroy and/or to delete
> it by your computer, without using the data herein contained.
>
>The present message (eventual annexes inclusive) shall not be
> considered any contractual proposal and/or acceptance of offer
> coming from the addressee, nor waiver neither recognizance of
> rights, debts and/or credits, and it shall not be binding, when it
> is not executed a subsequent agreement by person who could lawfully
> represent us. No pre-contractual liability shall derive to us, when
> the present communication is not followed by any binding agreement
> between the parties.

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

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