>The first time, i was able to login via telnet on port 10082, so that's why
>i think it
>must be now also possible?!?
I was mistaken. You can telnet to 10082, but it's not going to be able
to do much. However, I don't know why it would have said this right away:
amindexd: could not open conf file "amanda.conf": No such file or directory
Did you type anything to telnet before it reported this?
>I can't interpret the following lines of /tmp/amanda/amindexd.debug:
>
>amindexd: debug 1 pid 705 ruid 37 euid 37 start time Wed Feb 21 09:30:07
>2001
>amindexd: version 2.4.1p1
If that's all there was, then it died right away for some reason.
Try running amindexd by hand as root and see what that has to say.
If it just sits there, enter "QUIT".
>Why is it not possible to run amdump DailySet1 without running in between
>amcleanup?
I don't know. You didn't provide enough information.
I suspect amreport is failing, but wouldn't have any idea why.
>The first time, it was not required! It also seems to me that no dump is
>finished correctly.
Again, you didn't provide enough information. Why do you think none
of the dumps finished correctly?
>The amanda.conf is in the /etc/amanda/DailySet1 directory, so is that the
>right place because
>the server doesn't find it? ...
That depends on how you built Amanda. It needs to go in the directory
you gave ./configure with --with-configdir. If you didn't specify that
parameter, it defaults to $sysconfdir/amanda where $sysconfdir comes from
--with-sysconfdir and defaults to $prefix/etc which comes from --prefix
and defaults to /usr/local.
>The rights for it are set to root.
They need to allow access from the Amanda user.
>Best regards, Jörn Hildebrandt
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
