On Tue, 2006-01-31 at 11:57 -0800, Ram "TK" Krishnamurthy wrote:
> What does amidxtaped.*.debug contain in /tmp/amanada [assuming thats 
> where you server log files are]? Do you check all you xinetd/inetd 
> settings for services?
> 

Well, it was the inetd and services settings that were causing the
error. amidxtaped wasn't listed in /etc/services or
in /etc/inet/inetd.conf. I added amidxtaped and got rid of the protocol
error, but amrecover exited with an error because it couldn't read the
tape. Now the tape is stuck in the drive with the "Busy" light blinking,
amanda thinks the tape drive is empty, and the eject button doesn't
work. Bad hardware, I suppose.

Thanks,
Shang-Lin 

> Thanks
> tk
> 
> 
> Shang-Lin Chen wrote:
> > On Tue, 2006-01-31 at 10:15 -0800, Ram "TK" Krishnamurthy wrote:
> > 
> >>Looks like an issue with the services. What do the logs say?
> >>Does amcheck run without errors?
> >>
> > 
> > The logs of format /var/amanda/adm/amdump* contain lines like:
> > pid 14829 setsockopt(SO_RCVLOWAT): Option not supported by protocol .
> > The logs with names like /var/amanda/adm/log.date.level don't show any
> > problems. amcheck doesn't give any errors, either.
> > 
> > Thanks,
> > Shang-Lin
> > 
> > 
> >>Thanks
> >>tk
> >>
> >>
> >>Shang-Lin Chen wrote:
> >>
> >>>Hi,
> >>>
> >>>I'm trying to test our Amanda setup by restoring files. I can get into
> >>>amrecover from the client, browse and list the backed up files, and run
> >>>the "add" command. But when I try to run "extract", I get an error after
> >>>being prompted for the tape:
> >>>  amidxtape/tcp unknown protocol - config error?
> >>>  amrecover - can't talk to tape server
> >>>
> >>>Can someone help?
> >>>
> >>>Thanks,
> >>>Shang-Lin Chen
> >>>
> >>>
> >>>
> >>>
> >>
> > 
>