Amanda-Users

Re: amanda can't find its' own disk?

2003-01-02 18:58:27
Subject: Re: amanda can't find its' own disk?
From: John Oliver <joliver AT john-oliver DOT net>
To: amanda-users AT amanda DOT org
Date: Thu, 2 Jan 2003 15:25:48 -0800
On Thu, Jan 02, 2003 at 11:52:15AM -0500, Jon LaBadie wrote:
> You really seem to have problems not with amrecover, but much earlier.
> And they seem related to hostname resolution.

[root@backup root]# ./gethostbyname backup
name backup -> backup
               backup.indyme.local (alias)
               192.168.2.171 (addr)
[root@backup root]# ./gethostbyname backup.indyme.local
name backup.indyme.local -> backup
                            backup.indyme.local (alias)
                            192.168.2.171 (addr)
[root@backup root]# ./gethostbyaddr 192.168.2.171
addr 192.168.2.171 -> backup
                      backup.indyme.local (alias)
                      192.168.2.171 (addr)

So, what now?  It *still* doesn't see the disk in the local machine.
And amrecover is *still* trying to talk to "localhost".

[root@backup root]# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 backup AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2003-01-02)
200 Working date set to 2003-01-02.
200 Config set to DailySet1.
501 No index records for host: backup.indyme.local. Invalid?
Trying backup ...
501 No index records for host: backup. Invalid?
Trying backup.indyme.local ...
501 No index records for host: backup.indyme.local. Invalid?

There has to be some other config somewhere...

> I'm unclear about the reason such a program was needed, but John
> pointed out that most programs used to test connectivity, like ping,
> use exactly the same name resolution mechanisms as amanda.  Not that
> amanda is particularly unique, just there is more than one.  So his
> gethostbyname is an extraction of the core elements of amanda's name
> resolution routines you can use to check if a name should work or not.

amanda is almost certainly using the resolver on the machine.  These
little programs just make the C calls and rturn results.  dig will do
that, too.

> I've attached 3 files, the *.c files are from John, the makefile is
> just what I use on Solaris.  Your linux needs will probably vary.

That Makefile worked just fine... :-)

-- 
John Oliver, CCNA                            http://www.john-oliver.net/
Linux/UNIX/network consulting         http://www.john-oliver.net/resume/
***               sendmail, Apache, ftp, DNS, spam filtering         ***
****                Colocation, T1s, web/email/ftp hosting          ****

<Prev in Thread] Current Thread [Next in Thread>