Dave, That's a perfectly normal response from amandad. She doesn't like you because you're not a socket, which is the only kind of connection she understands. You'll need to get her hooked into xinetd (or inetd) correctly, then you can telnet to the port she's on to see if amandad is being launched correctly. The next step after that is to get an AMANDA server to try to connect to that port to request a backup.
Good Luck, Paul > -----Original Message----- > From: Dave Brooks [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 26, 2001 4:32 PM > To: [EMAIL PROTECTED] > Subject: amandad simply does not like me. > > > Greetings! > > I'm trying to get amanda 2.4.2p2 rolling on one of my servers > here, but I'm > having a little issue with amandad (and possibly xinetd, > though I think I > could work around that). > > 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 > > 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. > > Thanks! > Dave Brooks > > > -- > david a. brooks > * systems administrator > * stayonline.net > * voice: .. 770/933-0600 x217 > * email: .. [EMAIL PROTECTED] > * :wq! >
