On Mon, 3 Jun 2002 at 2:08pm, Rebecca Pakish wrote > Where the heck is 10082/tcp amandaidx???
Try this. Do '/etc/init.d/xinetd restart'. Then, look in /var/log/messages for the messages from xinetd, ending with a line like this: Jun 3 15:27:23 $HOST xinetd[29922]: Started working: 3 available services Look for any error messages, and check to see if that number matches the number of xinetd based services listed as "on" by 'chkconfig --list'. > >Try telneting to the port again. Then go to /tmp/amanda and locate > >the amindexd.<bunchanumbers>.debug file. Look in there for a hint. > >There are probably lots of these files so be sure to get the right > >one. (OR just delete all of them before telnetting :-) > > amrecover.bunchanumbers.debug: > amrecover: debug 1 pid 1602 ruid 0 euid 0 start time Mon Jun 3 13:56:07 > 2002 > amrecover: stream_client: connect(10082) failed: Connection refused > cannot connect to slaw.unterlaw.com: Connection refused > amrecover: pid 1602 finish time Mon Jun 3 13:56:07 2002 That's not so interesting. What we're looking for is amindexd*debug. That file just tells us that amrecover fails, which we knew already. :) > /var/log secure: > <snip> > Jun 3 13:52:22 slaw xinetd[843]: START: amidxtape pid=1595 from=10.1.7.23 > > is all that was in there from the last time I tried amrecover Hrrm. When I run amrecover, all I see on my server is amandaidx starting up. > I saw this in there from this morning: > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1134 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1135 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1136 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1137 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1138 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1139 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1140 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1141 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1142 from=0.0.0.0 > Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1143 from=0.0.0.0 That looks like a service that is looping and getting shut off for a while. Hmmm.... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
