Re: Amrecover: 500 Access not allowed
On Tue, Jul 08, 2003 at 02:19:05PM -0500, Rebecca Pakish Crum wrote: > My backup server was installed and configured with a different name, > because it was built online to replace an existing box. Server 1: > web.isymmetrics.com; Server 2 built as webby.isymmetrics.com. > [...] > So I added 'webby' with the [same] ip addy to my /etc/hosts > file on web, > [...] > [EMAIL PROTECTED] libexec]# amrecover isymmdaily > AMRECOVER Version 2.4.2p2. Contacting server on webby ... > 220 web AMANDA index server (2.4.2p2) ready. > 500 Access not allowed: [ip address 10.1.8.9 is not in the ip list for > web] I'm not familiar with that message. But just as an off-the-cuff guess, try adding "webby" as a CNAME for "web" in the DNS (as opposed to simply in the machine's own /etc/hosts file). Or rebuild Amanda :-( -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: Amrecover: 500 Access not allowed
On Tue, 8 Jul 2003 at 2:19pm, Rebecca Pakish Crum wrote > [EMAIL PROTECTED] libexec]# amrecover isymmdaily > AMRECOVER Version 2.4.2p2. Contacting server on webby ... > 220 web AMANDA index server (2.4.2p2) ready. > 500 Access not allowed: [ip address 10.1.8.9 is not in the ip list for > web] What happens if you try 'amrecover isymmdaily -s web -t web'? > WHAT? It is 10.1.8.9...all of the index files live on 10.1.8.9. Is there > something cached somewhere with webby's name and IP that I can tinker > with? > HELP. If something is cached anywhere, it's in the DNS server. Can you fiddle with that? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Amrecover: 500 Access not allowed
> What happens if you try 'amrecover isymmdaily -s web -t web'? Hang on, I'll try it... > > > WHAT? It is 10.1.8.9...all of the index files live on 10.1.8.9. Is > > there something cached somewhere with webby's name and IP > that I can > > tinker with? HELP. > > If something is cached anywhere, it's in the DNS server. Can > you fiddle > with that? I tried listing webby CNAME to web in the DNS...dig finds it just fine pointing to web and resolving to 10.1.8.9.
RE: Amrecover: 500 Access not allowed
> What happens if you try 'amrecover isymmdaily -s web -t web'? > This worked like a charm. I think I'm in. I was able to set disk and set host based on this. Where are these options listed. I had previously checked out the man page for amrecover looking for some option to set my index and tape server, but didn't see anything?!?! I should probably rebuild amanda, eh?
RE: Amrecover: 500 Access not allowed
On Tue, 8 Jul 2003 at 2:42pm, Rebecca Pakish Crum wrote > > What happens if you try 'amrecover isymmdaily -s web -t web'? > > > This worked like a charm. I think I'm in. I was able to set disk and set > host based on this. Where are these options listed. I had previously > checked out the man page for amrecover looking for some option to set my > index and tape server, but didn't see anything?!?! They're right at the top of amrecover(8) on my system (2.4.4)... > I should probably rebuild amanda, eh? Not necessarily. Building amanda just sets defaults for those options (you can see them if you do ./configure --help). If you can remember to do them by hand when you amrecover, there's no need for the defaults to be "right". -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
