On Mon, Feb 25, 2002 at 12:17:23PM -0500, Joshua Baker-LePain wrote:
> Date: Mon, 25 Feb 2002 12:17:23 -0500 (EST)
> From: Joshua Baker-LePain <[EMAIL PROTECTED]>
> To: Graham Dunn <[EMAIL PROTECTED]>
> cc: [EMAIL PROTECTED]
> Subject: Re: Strange failure to connect to client
> 
> On Mon, 25 Feb 2002 at 12:06pm, Graham Dunn wrote
> 
> > amcheck shows no errors, but the amdump log reports a problem...
> > ideas?
> > 
> > FAIL driver oshaberi /usr/local/mailman 0 20020225[could not connect
> > to oshaberi]
> > FAIL driver oshaberi ad0s1a 0 20020225[could not connect to oshaberi]
> > INFO taper tape DailySet103 kb 320 fm 2 [OK]
> > FINISH driver date 20020225 time 366.114
> > 
> > Amanda Backup Client Hosts Check
> > --------------------------------
> > Client check: 3 hosts checked in 0.557 seconds, 0 problems found
> > 
> Is there anything in /tmp/amanda/amanda*debug on oshaberi created at the 
> time of the amdump attempth?  How about sendsize*debug?

Nothing in there... I'm getting a new error now:

DISK planner oshaberi ad0s1a
DISK planner oshaberi /usr/local/mailman
START driver date 20020225
DISK planner axp500 da0a
DISK planner tsuyoi ad0s1a
START planner date 20020225
INFO planner Adding new disk oshaberi:ad0s1a.
INFO planner Adding new disk oshaberi:/usr/local/mailman.
FINISH planner date 20020225
STATS driver startup time 0.894
ERROR taper no-tape [new tape not found in rack]
FAIL driver oshaberi /usr/local/mailman 20020225 0 [can't switch to
incremental
dump]
FAIL driver oshaberi ad0s1a 20020225 0 [can't switch to incremental
dump]
SUCCESS dumper axp500 da0a 20020225 1 [sec 0.267 kb 160 kps 597.3
orig-kb 160]
SUCCESS dumper tsuyoi ad0s1a 20020225 1 [sec 0.312 kb 130 kps 416.1
orig-kb 130]FINISH driver date 20020225 time 259.533

And I haven't changed anything in the amanda config (I know, I know, I
don't believe that when my users say it either, but seriously) on the
server or client.

Looking through the FM, I see "can't switch to incremental mode" on a
new filesystem usually means there's something wrong with the tape. Is
this what the "[new tape not found in rack]" error is?

There's no way the previous tapes are full and in contrast to my
previous message, there's no INFO taper ... line at the end of this
log (/usr/adm/amanda/DailySet1/log.20020225.3).

Graham

Reply via email to