> > >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.
That is correct, and you don't have to restart it. It's a client daemon, so the transaction goes like this: 1. User (or cron) starts amdump. 2. amdump (using other parts of amanda) sends requests to each client asking for backups or size estimates 3. Each client catches those requests through the daemon and fills them. It's just like telnetd: there's no reason to load it until it's called for over. > > >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. Do you have only one client listed in disklist at this point? That would be cleanest for testing. > > 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 Here are mine for comparison (RedHat 6.2): amanda dgram udp wait amanda /usr/libexec/amandad amandad amandaidx stream tcp nowait amanda /usr/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/libexec/amidxtaped amidxtaped You might want to try changing inetd.conf. > > ...on three lines instead of six, though, obviously. > > -Dave > > -- > david a. brooks > * systems administrator > * stayonline.net > * voice: .. 770/933-0600 x217 > * email: .. [EMAIL PROTECTED] > * :wq! >
