On Wed, 26 Sep 2001 at 4:32pm, Dave Brooks wrote > Basically, if I try to manually invoke amandad from the command line, > everything seems well for about the first 30 seconds, at which time the > process terminates and leaves the following ditty in > /tmp/amanda/amandad*debug: > > amandad: dgram_recv: timeout after 30 seconds > amandad: error receiving message: timeout > error receiving message: timeout > amandad: pid 16566 finish time Wed Sep 26 15:30:11 2001
So you started amandad, which started listening for requests, didn't hear any within 30 seconds, and so quit. That's normal. > The amandad process is being invoked as root. Same happens if invoked with > the amanda user. Any ideas on what could be going awry? This of course > causes problems because amanda then can't connect to the client daemon > (which, in this case, happens to be on the same machine) and nothing gets > written to tape. The setup debugging tool of choice is amcheck, not manual amandad. What does 'amcheck CONFIG' say about your setup? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
