The pathes are hardcoded in the script

-----Ursprüngliche Nachricht-----
Von: Christoph Scheeder [mailto:christoph.scheeder AT scheeder DOT de] 
Gesendet: Donnerstag, 14. April 2005 10:44
An: Sebastian Kösters
Cc: amanda-users AT amanda DOT org
Betreff: Re: AW: AW: AW: Problem with tape and labeling (archiving)

Sebastian Kösters schrieb:
> I just tried to do exactlly all the Steps that cron makes and everything
> works...i do not understand it.
> 

what about the pathes of the programs used in your scripts,
are they hardcoded in the script or do you depend on the PATH
variable to be set correct?
if the later, it will not work from user-crontabs ,
as these normaly get executed without the normal user environment set.
does that ring a bell?
Christoph

> Cron:
> 
> 0 1 * * 0 /etc/amanda/label.sh (with DailySet1004)
> 15 1 * * 0 /usr/sbin/amcheck -a full-Sonntag
> 
> Amanda Tape Server Host Check
> -----------------------------
> ERROR: /dev/nst0: reading label: Input/output error
>        (expecting tape DailySet1001 or a new tape)
> NOTE: skipping tape-writable test
> Server check took 0.198 seconds
> 
> Amanda Backup Client Hosts Check
> --------------------------------
> Client check: 1 host checked in 0.032 seconds, 0 problems found
> 
> (brought to you by Amanda 2.4.4p4)
> 
> Manually:
> 
> bash-3.00$ /etc/amanda/label.sh (with DailySet1004)
> rewinding, reading label, reading label: Input/output error
> rewinding, writing label DailySet1004, checking label, done.
> 
> bash-3.00$ amcheck full-sonntag
> Amanda Tape Server Host Check
> -----------------------------
> NOTE: skipping tape-writable test
> Tape DailySet1004 label ok
> Server check took 0.022 seconds
> 
> Amanda Backup Client Hosts Check
> --------------------------------
> Client check: 1 host checked in 0.024 seconds, 0 problems found
> 
> (brought to you by Amanda 2.4.4p4)
> 
> 
> Cron does exactly the same....?!
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: owner-amanda-users AT amanda DOT org [mailto:owner-amanda-users AT 
> amanda DOT org]
Im
> Auftrag von Sebastian Kösters
> Gesendet: Donnerstag, 14. April 2005 08:11
> An: amanda-users AT amanda DOT org
> Betreff: AW: AW: AW: Problem with tape and labeling (archiving)
> 
> labelstr "^DailySet1[0-9][0-9][0-9]*$"
> 
> Tapelist:
> 
> 20050327 DailySet1003 reuse
> 20050313 DailySet1002 reuse
> 20050306 DailySet1001 reuse
> 
> -----Ursprüngliche Nachricht-----
> Von: owner-amanda-users AT amanda DOT org [mailto:owner-amanda-users AT 
> amanda DOT org]
Im
> Auftrag von Jon LaBadie
> Gesendet: Mittwoch, 13. April 2005 18:22
> An: amanda-users AT amanda DOT org
> Betreff: Re: AW: AW: Problem with tape and labeling (archiving)
> 
> On Wed, Apr 13, 2005 at 11:57:53AM -0400, Gene Heskett wrote:
> 
>>On Wednesday 13 April 2005 06:10, Sebastian  Kösters wrote:
>>
>>>The "1" is in the file counter (see Script - 1001, 1002 .....)
>>>DailySet$counter == DailySet1xxx
>>
>>Are you saying that 'counter' was seeded with the number 1000 to start 
>>this method up?  That is not obvious from the prior postings.  In 
>>this event, we need to see the labelstr from the amanda.conf which 
>>has not been supplied to the list yet, at least in the messages I 
>>just rechecked.
> 
> 
> Definitely show the labelstr,
> 
> and I'd like to see the contents of your 'tapelist' file created
> by all those successful amlabels.
>