Dave Brooks ([EMAIL PROTECTED]):
>>So you started amandad, which started listening for requests, didn't hear >>any within 30 seconds, and so quit. That's normal. >> > The daemon terminates itself if it doesnt receive any requests within 30 > seconds? So you have to restart it? Surely that can't be. It's run by inetd (or xinetd) so it is started anytime a new connection comes in. If it doesn't get anything from the connection it stops. Otherwise, you could end up filling up the memory / process space with amandad instances by nudging the port and then not connecting. >>The setup debugging tool of choice is amcheck, not manual amandad. What >>does 'amcheck CONFIG' say about your setup? >> > 'amcheck std' produces no errors other than a timeout when trying to connect > to the client daemon. > The pertinent lines on the client's /etc/inetd.conf (which, for the time being, > happens to be the server as well) are as follows: > amanda dgram udp wait amanda /usr/lib/amanda/amandad > amandad > amandaidx dgram tcp wait amanda /usr/lib/amanda/amandaidx > amandaidx > amidxtape dgram tcp wait amanda /usr/lib/amanda/amidxtape > amidxtape > ...on three lines instead of six, though, obviously. Uh, you said before that you were using xinetd. If so, don't you need to add a config file to /etc/xinet.d/ for the amanda connections? If you are using inetd, then make sure you restarted or reloaded inetd. 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. There is a whole list of steps in the FAQ that you can run through to see where the problem might be. -- Jeremy Wadsack Wadsack-Allen Digital Group
