This is my inetd.conf!
#inetd.conf of saturn
# amanda backup server with indexing capabilities
amandaidx stream tcp nowait root /usr/lib/amanda/amindexd
amindexd
amidxtape stream tcp nowait root /usr/lib/amanda/amidxtaped
amidxtaped
#
# amanda backup client
amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad
#
When all the daemons mentioned above are set to the user amanda, it also
doesn't work.
(after init 1/2)
also tried:
saturn:/usr/lib/amanda # ./amindexd -t
220 saturn AMANDA index server (2.4.1p1) ready.
thank you again,
jörn h.
-----Ursprüngliche Nachricht-----
>i didn't type anything to telnet before i got this report for port 10082:
>
>saturn:~ # telnet saturn 10082
>Trying 10.0.0.56...
>Connected to saturn.
>Escape character is '^]'.
>amindexd: could not open conf file "amanda.conf": No such file or directory
>Connection closed by foreign host.
Please post your inetd.conf line for amindexd. I suspect you have an
extra argument on it that is confusing things.
>When i try to run amindexd by hand, this happens:
>
>saturn:/usr/lib/amanda # ./amindexd
>amindexd: getpeername: Socket operation on non-socket
Sorry. I should have told you to use the "-t" option so it would read
commands from stdin instead of thinking it was connected to a socket.
But I don't think this is related to any of your problems.
>does it mean, that the amindexd daemon is never started?
No. The daemon is starting, it is just not happy about something.
>Has it to run permanently or only when i want to execute amrecover?
It is only started by inetd when amrecover connects to it.
>the index-files themselves are in /var/lib/amanda/DailySet1/index ...
You're not getting that far.
>i started up amreport, but he can't find the log file.
That's probably because you had already run amcleanup.
>i know the first time there was always also only a "log" file,
>now there is only one temporary when i run <amdump DailySet1>!
>when i am doing a dump and have a look in the "log" file via another
>console,
>it remains there.
I don't understand. There should be a file named "log" while amdump is
running. Amreport renames it to log.YYYYMMDD.N at the end of the script.
>i also can't exlpain why i have to run amcleanup DailySet1 in between i am
>doing a few dumps.
Why do you think you have to run it? Are you not getting the E-mail
report from the amdump? Is there a "log" or "amdump" file still laying
around after amdump is done?
>ok, here is the an extract of the dump session:
Except for the "socket ignored" message, which is taken care of in
current Amadna releases, I don't see anything wrong in this report.
>Jörn
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
