Dave Brooks ([EMAIL PROTECTED]):
>>If you are using inetd, then make sure you restarted or reloaded >>inetd. >> > Oh yes, many times. =] >>In either case, check /tmp/amanda for a amandad.*.debug file to see if >>the connection is even starting amandad. If the file exists, it may >>give you more insight to where the problem is. >> > Actually, if I HUP the inetd process, the /tmp/amandad*debug files are not > even created. If I go back to my errorful ways of starting amandad by hand, > it creates the file, but of course that's not the correct way to start > amandad. > On top of that, I can't telnet to port 10080 (connection refused), and I do > not have any sort of packet filtering or tcpwrappers on the machine at the > moment. Did you build the client on the machine it's running on (you said it was the backup server, so I assume you built it there, but it's safe to check)? Make sure that the hostname that the server is looking for is right. I had several clients that had different hostnames from 'hostname' on the client than from nslookup on the server. Since it's the same host it *probably* is the same, but it might not be. My backup server thinks it's a different hostname than all the clients do. You can grab a copy of nmap (http://www.insecure.org/) and try to have it connect to UDP port 10080. Telnet won't connect because (a) amandad is using UDP, not TCP, and (b) it's not a telnet server (I don't think). I have one bum client left that I can't get to work and nmap tells me it's not responding (port closed) if I scan a range of ports, but it tells me it's open, running amandad if I scan just the 10080 port. So that's all the tips I can give you. If I can figure out this last client, I'll let you know. -- Jeremy Wadsack Wadsack-Allen Digital Group
