Hi, John. > Do you have amindexd and amidxtaped configured in inetd.conf or xinetd? > Yes ,i have. > > If you run "netstat -a | grep amandaidx" is something listening? What > about if you grep for amidxtape? In the client: #netstat -a | grep amandaidx tcp 0 0 *:amandaidx *:* LISTEN #netstat -a | grep amidxtape tcp 0 0 *:amidxtape *:* LISTEN In the server: #netstat -a | grep amandaidx tcp 0 0 *:amandaidx *:* LISTEN #netstat -a | grep amidxtape tcp 0 0 *:amidxtape *:* LISTEN > Does /tmp/amanda/amindexd*debug get updated on the server? If so, > what's in it? There isn't any amindexd*debug in the server. Thanks.
- Re: amrecover: Unexpected server end of file John R. Jackson
- Re: amrecover: Unexpected server end of file Paul Lussier
- Re: amrecover: Unexpected server end of file John R. Jackson
- amrecover: Unexpected server end of file Paul Brannigan
- Re: amrecover: Unexpected server end of file John R. Jackson
- Re: amrecover: Unexpected server end of file Paul Brannigan
- RE: amrecover: Unexpected server end of file James Stevens
- Re: amrecover: Unexpected server end of file Paul Brannigan
- amrecover: Unexpected server end of file Vicente Vives
- Re: amrecover: Unexpected server end of file John R. Jackson
- Re: amrecover: Unexpected server end of file Vicente Vives
- Re: amrecover: Unexpected server end of file John R. Jackson
- Re: amrecover: Unexpected server end of file Alexandre Oliva
- Re: amrecover: Unexpected server end of file Vicente Vives
- amrecover: Unexpected server end of file Jason Joines
- Re: amrecover: Unexpected server end of file bhlewis
- Re: amrecover: Unexpected server end of file Jason Joines
- Re: amrecover: Unexpected server end of file Jason Joines
- Re: amrecover: Unexpected server end of file bhlewis
- Re: amrecover: Unexpected server end of file Jason Joines
- amrecover: Unexpected server end of file Jason Joines