On Tuesday 08 January 2002 10:51 am, Joseph Myers wrote: >I have AMANDA working on the server just fine. It is capable of > backing up two computers already. Now I have to work on the other 4. > The problem is the first 2 are running RedHat 7.1 and are thus using > xinetd while the next 4 are running RedHat 6.2 and are thus using > inetd. I can not figure out what the heck is wrong. Here is some > info: > >in inetd.conf: > >amanda dgram udp wait amanda /usr/local/libexec/amandad amandad >amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindex >d > amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amid >xtaped > >Here's the results from "netstat -a | grep -i amanda": > > >tcp 0 0 *:amandaidx *:* > LISTEN > >udp 0 0 *:amanda *:* > > >I have the permissions set on all of the files so that Amanda can > read, write, and execute them. The .rhosts and .amandahosts files > which are in both the root and amanda directories look like this: > >xxx.ornl.gov amanda > >On the server, in /tmp/amanda/*.debug, I get this message: > >amcheck: debug 1 pid 15215 ruid 1000 euid 0 start time Tue Jan 8 > 10:26:10 2002 >amcheck: dgram_bind: socket bound to 0.0.0.0.769 >amcheck: pid 15215 finish time Tue Jan 8 10:26:40 2002 > >The other two servers still work when I run amcheck so I don't think > that there's anything wrong with the server side. It appears to be a > client side problem. I am running the same version of Amanda on all > of the machines. Another thing that I've heard people talk about is > the IPChains firewall. We use an IPChains firewall.. but one of the > other computers I back up is the firewall and the all of the > computers are behind this firewall. So I can already backup another > computer that is behind the firewall with no changes made to the > IPChains so I don't believe that this is the problem. Please help me > as soon as you can. I am stuck and this is holding up a major > project. Thanks for any help you can give me.
One possibility that I can think of would happen if you just put the newest version of xinetd on the machine thats failing. This new version of xinetd *must* have the glibc-2.2.4-20 (the whole kit and kaboodle) installed before it will run. It does NOT show up in the dependencies, only when tyou try to run it. Cheers, Gene
