Amanda-Users

Re: 501 Could not read config file /etc/amanda/amindexd/amanda.conf!

2009-04-03 13:11:38
Subject: Re: 501 Could not read config file /etc/amanda/amindexd/amanda.conf!
From: Jukka Salmi <j+amanda AT 2009.salmi DOT ch>
To: amanda-users AT amanda DOT org
Date: Fri, 3 Apr 2009 19:05:10 +0200
Jean-Louis Martineau --> amanda-users (2009-04-03 12:43:36 -0400):
> Change it to:
> amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
> amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
>
> Other arguments should only be used for amandad.

Indeed, works fine now, thanks a lot!

Hmm, I wonder why the Debian package adds those arguments to the
amandaidx and amidxtape services...  Seems to be a bug, doesn't it?


Regards, Jukka

> Jean-Louis
>
> Jukka Salmi wrote:
>> Jean-Louis Martineau --> amanda-users (2009-04-03 11:49:53 -0400):
>>   
>>> amrecover from 2.5.2p1 and 2.4.4p3 use different protocol to 
>>> communicate  with the server.
>>>
>>> What's the xinetd configuration for the amindexd and amidxtaped 
>>> network  services on the server?
>>>     
>>
>> (The systems in question use obsd inetd instead of xinetd, but this shouldn't
>> matter AFAICT...)
>>
>> amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd 
>> amindexd -auth=bsd amdump amindexd amidxtaped
>> amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped 
>> amidxtaped -auth=bsd amdump amindexd amidxtaped
>>
>>
>> Regards, Jukka
>>
>>   
>>> Jean-Louis
>>>
>>> Jukka Salmi wrote:
>>>     
>>>> Hello,
>>>>
>>>> I'm having a problem with amrecover(8) on Linux systems.  The backup
>>>> server runs Amanda 2.5.2p1 on Debian lenny, the backup client runs
>>>> Amanda 2.4.4p3 on Debian sarge.  Running amrecover(8) on the server
>>>> works fine:
>>>>
>>>> $ amrecover -C myconf -s srv -t srv
>>>> AMRECOVER Version 2.5.2p1. Contacting server on srv ...
>>>> 220 srv AMANDA index server (2.5.2p1) ready.
>>>> [...]
>>>>
>>>> But running it on the client does not:
>>>>
>>>> $ amrecover -C myconf -s srv -t srv
>>>> AMRECOVER Version 2.4.4p3. Contacting server on srv ...
>>>> 501 Could not read config file /etc/amanda/amindexd/amanda.conf!
>>>>
>>>> The relevant amindexd.*.debug on the server then looks like this:
>>>>
>>>> amindexd: debug 1 pid 28092 ruid 34 euid 34: start at Fri Apr  3 17:31:45 
>>>> 2009
>>>> amindexd: version 2.5.2p1
>>>> could not open conf file "/etc/amanda/amindexd/amanda.conf": No such file 
>>>> or directory
>>>> amindexd: time 0.003: < 501 Could not read config file 
>>>> /etc/amanda/amindexd/amanda.conf!
>>>> amindexd: time 0.003: < 220 srv AMANDA index server (2.5.2p1) ready.
>>>> amindexd: time 0.003: ? read error: Connection reset by peer
>>>> amindexd: time 0.003: pid 28092 finish time Fri Apr  3 17:31:45 2009
>>>>
>>>> That file (/etc/amanda/amindexd/amanda.conf) indeed does not exist on
>>>> the server, but I can't find any references to it in the documentation.
>>>> What am I missing?
>>>>
>>>>
>>>> TIA, Jukka
>>>>       
>>
>>   
>

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~

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