Hi,
amcheck fails, whether 'backup03m' is in my hosts file or not.
But, anyway, 'backup03m' is in the DNS and can be resolved correctly.
'backup03m' is the only name of the host, it has no aliases.
Nice greetings,
Christoph
Am Donnerstag, 6. November 2003 11:05 schrieben Sie:
> On Thursday 06 November 2003 04:35, Christoph Brunner wrote:
> >Hi,
> >
> >my amanda file in /etc/xinet.d/ looks exactly like this, the options
> > are set correctly, too. I am not running inetd, only xinetd.
> >Only the localhost (backup03m) is not passed correctly in amcheck,
> > other hosts are ok.
> >I tried the disklist file with 'localhost' instead of 'backup03m':
> > The amcheck passes, but i get errors in starting amrecover, that
> > backup03m isn't in disklist.
> >To me it seemed easier to change 'localhost' to 'backup03m' in the
> > disklist file than change anything else in the configuration.
> >But why can't amcheck connect to the host it is running on?
>
> Do you have backup03m defined in your hosts file? And is this the
> cannonical name of the machine? I'm using the short alias here for
> both machines, and both are defined in teh /etc/hosts file.
>
> Using localhost, as you found, will bite you.
>
> >Nice greetings,
> >Christoph
> >
> >Am Donnerstag, 6. November 2003 10:21 schrieben Sie:
> >> On Thursday 06 November 2003 03:57, Christoph Brunner wrote:
> >> >Hi,
> >> >
> >> >when i run amcheck, i get an error, that the host, i am currently
> >> > working on, is not available:
> >> >
> >> >====================================================
> >> >amanda@backup03m amanda $ amcheck -c DailySet1
> >> >
> >> >Amanda Backup Client Hosts Check
> >> >--------------------------------
> >> >WARNING: backup03m: selfcheck request timed out. Host down?
> >> >Client check: 2 hosts checked in 30.201 seconds, 1 problem found
> >> >
> >> >(brought to you by Amanda 2.4.4p1)
> >> >====================================================
> >> >
> >> >A nslookup|dig|host can resolve the hostname, so that can't be
> >> > the problem. If i write the FQDN of the host name in the
> >> > disklist, the error is the same.
> >> >
> >> >Does anyone know, where the problem is?
> >>
> >> Are you running on a system that uses xinetd?
> >>
> >> If so, my guess is that you need a file, located in /etc/xinetd.d,
> >> called amanda, probably owned by amanda:disk, that resembles this
> >> one:
> >> ------------------------------------
> >> # default = off
> >> #
> >> # description: Part of the Amanda server package
> >> # This is the list of daemons & such it needs
> >> service amanda
> >> {
> >> disable = no
> >> socket_type = dgram
> >> protocol = udp
> >> wait = yes
> >> user = amanda
> >> group = disk
> >> groups = yes
> >> server = /usr/local/libexec/amandad
> >> }
> >> service amandaidx
> >> {
> >> disable = no
> >> socket_type = stream
> >> protocol = tcp
> >> wait = no
> >> user = amanda
> >> group = disk
> >> groups = yes
> >> server = /usr/local/libexec/amindexd
> >> }
> >> service amidxtape
> >> {
> >> disable = no
> >> socket_type = stream
> >> protocol = tcp
> >> wait = no
> >> user = amanda
> >> group = disk
> >> groups = yes
> >> server = /usr/local/libexec/amidxtaped
> >> }
> >> ---------------------------------------
> >>
> >> Modify the paths to suit your system of course, and the 'user' and
> >> 'group' to match yours.
> >>
> >> Of course if you're still running things from an inetd list, the
> >> docs contain the info to set that up. Either must be restarted to
> >> take effect of course.
> >>
> >> >Nice greetings,
> >> >Christoph Brunner
--
InterNetX GmbH
Christoph Brunner
System Administration
Maximilianstrasse 6
D-93047 Regensburg
Tel. +49 941 59559-0
Fax +49 941 59559-457
eMail: christoph.brunner AT internetx DOT de
|
