Re: amindexd
That's the fix.
Thankyou.
Quoting Matt Hyclak <[EMAIL PROTECTED]>:
> On Tue, Jul 19, 2005 at 11:48:14AM -0600, [EMAIL PROTECTED] enlightened us:
> > I've tried different ownership for amindexd.
> >
> > Here's the xinetd configuration for amindexd.
> >
> > Thanks
> > Rich
> >
> >
> > [EMAIL PROTECTED] xinetd.d]# cat amandaidx
> > # default: off
> > #
> > # description: Part of the Amanda server package
> >
> > service amandaidx
> > {
> > socket_type = stream
> > protocol= tcp
> > wait= no
> > user= amanda
> > group = disk
> > server = /usr/lib/amanda/amindexd
> > disable = yes
> > }
> ^
>
> Doesn't work so good when it's disabled ;-)
>
> Change to no, restart xinetd, and hope you didn't mess up the permissions on
> amindexd. It should be 0755 by amanda:disk.
>
> Matt
>
> --
> Matt Hyclak
> Department of Mathematics
> Department of Social Work
> Ohio University
> (740) 593-1263
>
Re: amindexd
I've tried different ownership for amindexd.
Here's the xinetd configuration for amindexd.
Thanks
Rich
[EMAIL PROTECTED] xinetd.d]# cat amandaidx
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
server = /usr/lib/amanda/amindexd
disable = yes
}
Quoting Matt Hyclak <[EMAIL PROTECTED]>:
> On Tue, Jul 19, 2005 at 10:48:23AM -0600, [EMAIL PROTECTED] enlightened us:
> > Well.
> > I have checked the docs and faq.
> >
> >
> > I'm running the command as root as specified by the faq
> > http://amanda.sourceforge.net/cgi-bin/fom?_recurse=1&file=5
> >
> >
> > >You see, I had 127.0.0.1 configured for user amanda for amdump. Amrecover
> HAS
> > to be run as root.
> >
> >
> > Also running the command specifying index server and tape server fails in
> the
> > same way as if it were localhost.
> >
> > #amrecover CCC -s fastkernel.chem.utah.edu -t fastkernel.chem.utah.edu
> > AMRECOVER Version 2.4.4p1. Contacting server on fastkernel.chem.utah.edu
> ...
> > amrecover: cannot connect to fastkernel.chem.utah.edu: Connection refused
> > [EMAIL PROTECTED] xinetd.d]# cat /var/lib/amanda/.amandahosts
> > ##127.0.0.1 root
> > fastkernel.chem.utah.edu root
> >
> > Thanks for your help
> > Rich
>
> It looks like amindexd isn't listening. What is your xinetd configuration
> for amanda?
>
> Matt
>
> --
> Matt Hyclak
> Department of Mathematics
> Department of Social Work
> Ohio University
> (740) 593-1263
>
[no subject]
Well. I have checked the docs and faq. I'm running the command as root as specified by the faq http://amanda.sourceforge.net/cgi-bin/fom?_recurse=1&file=5 >You see, I had 127.0.0.1 configured for user amanda for amdump. Amrecover HAS to be run as root. Also running the command specifying index server and tape server fails in the same way as if it were localhost. #amrecover CCC -s fastkernel.chem.utah.edu -t fastkernel.chem.utah.edu AMRECOVER Version 2.4.4p1. Contacting server on fastkernel.chem.utah.edu ... amrecover: cannot connect to fastkernel.chem.utah.edu: Connection refused [EMAIL PROTECTED] xinetd.d]# cat /var/lib/amanda/.amandahosts ##127.0.0.1 root fastkernel.chem.utah.edu root Thanks for your help Rich
amrecover fails with stream_client_privileged Connection refused
Hi. I'd installed amanda a short time ago. Backups are working fine, however now I'm testing the recover and I'm not able to get the server to access itself. I've changed the user in /root/.amandahosts, commented out the localhost entry as well. And played with ownershop of amandaidx. All to no avail. # amrecover CCC AMRECOVER Version 2.4.4p1. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused cat amrecover.20050719094728.debug amrecover: debug 1 pid 2019 ruid 0 euid 0: start at Tue Jul 19 09:47:28 2005 amrecover: stream_client_privileged: connect to 127.0.0.1.10082 failed: Connection refused amrecover: cannot connect to localhost: Connection refused amrecover: pid 2019 finish time Tue Jul 19 09:47:28 2005
Re: which tape changer for Qualtstar TLS-4210
> mt works on tape devices, not generic SCSI devices. Try > 'mt -f /dev/nst0'. > > > I'd thought the command: > > # mtx -f /dev/sg0 unload 12 1 > > would not need to function together with mt. > > It depends on the loader (and, sometimes, the loader's firmware settings). > Sometimes you can just send an 'unload' to the robot and it'll tell the > tape drive to eject the tape, and sometimes you need to explicitly > 'mt -f /dev/nst0 offline' before the 'mtx unload' will work. that seems to have been the case here. Thankyou very much. I'm off to the next problem. Rich
which tape changer for Qualtstar TLS-4210
Hello. I've been trying to get a tape changer TLS-4210 to work for a while for amanda. I'm unable to get the tape changer to work. For now I've been using the mtx command on a linux machine. The problem is that as soon as I mount a drive. The tape gets stuck and will not eject. Am I using the wrong protocol. The jukebox has worked well before. thankyou Rich #mtx -f /dev/sg0 inquiry Product Type: Medium Changer Vendor ID: 'QUALSTAR' Product ID: 'TLS-4210' Revision: '2.12' Attached Changer: No # mtx -f /dev/sg0 status Storage Changer /dev/sg0:2 Drives, 12 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 5 Loaded) Data Transfer Element 1:Full (Storage Element 12 Loaded) Storage Element 1:Full Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Empty Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full Storage Element 11:Full Storage Element 12:Empty
