Hello,
thanks for your answer!
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.
When i try to run amindexd by hand, this happens:
saturn:/usr/lib/amanda # ./amindexd
amindexd: getpeername: Socket operation on non-socket
what should i do?
does it mean, that the amindexd daemon is never started?
Has it to run permanently or only when i want to execute amrecover?
the index-files themselves are in /var/lib/amanda/DailySet1/index,
they are definitely created. the indexdir is also set right is the
amanda.conf.
i started up amreport, but he can't find the log file.
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.
-rw------- 1 amanda disk 5218 Feb 22 09:38 amdump.1
-rw------- 1 amanda disk 5162 Feb 21 14:28 amdump.2
drwxr-xr-x 3 amanda disk 4096 Feb 21 14:27 curinfo
-rw-rw-r-- 1 amanda disk 41 Feb 21 13:15 disklist
drwxr-xr-x 2 amanda disk 4096 Feb 21 14:23 index
-rw------- 1 amanda disk 911 Feb 21 14:28 log.20010221.0
-rw------- 1 amanda disk 961 Feb 22 09:38 log.20010222.0
-rw------- 1 amanda disk 54 Feb 22 09:35 tapelist
-rw------- 1 amanda disk 27 Feb 21 14:25 tapelist.yesterday
saturn:/var/lib/amanda/DailySet1 # amreport DailySet1 log.2001022.0
amreport: could not open log /var/lib/amanda/DailySet1/log: No such file or
dire
ctory
i also can't exlpain why i have to run amcleanup DailySet1 in between i am
doing a few dumps.
the rights now also allow access from amanda.
ok, here is the an extract of the dump session:
Subject: DailySet1 AMANDA MAIL REPORT FOR February 22, 2001
These dumps were to tape DailySet101.
Tonight's dumps should go onto 1 tape: DailySet102.
FAILURE AND STRANGE DUMP SUMMARY:
saturn.sys / lev 0 STRANGE
.......
.....
...
FAILED AND STRANGE DUMP DETAILS:
/-- saturn.sys / lev 0 STRANGE
sendbackup: start [saturn.systemelektronik.de:/ level 0]
sendbackup: info BACKUP=/bin/tar
/-- saturn.sys / lev 0 STRANGE
sendbackup: start [saturn.systemelektronik.de:/ level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
? gtar: ./var/run/.nscd_socket: socket ignored
| Total bytes written: 182712320 (174MB, 1.5MB/s)
sendbackup: size 178430
sendbackup: end
\--------
NOTES:
taper: tape DailySet101 kb 178464 fm 1 [OK]
ok, i hope you can help me!
thanks
Jörn, a trainee at system elektronik
AW: coherency between amindexd and amrecover
>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]
