Jon yes maybe I was a bit hasty on my email, and should have thought about it more.
you are correct regarding amandad running on udp rather than tcp. Here is a output of my email from the amanda user after a amdump is run. this may give a better idea of what is going on. regards Joseph These dumps were to tape daily1-001. The next 4 tapes Amanda expects to used are: daily1-002, daily1-003, daily1-004, daily1-005. FAILURE AND STRANGE DUMP SUMMARY: olbs2.in.t /usr lev 0 FAILED [disk /usr offline on olbs2.in?] olbs2.in.t /home lev 0 FAILED [disk /home offline on olbs2.in?] olbs1.in.t /usr lev 0 FAILED [disk /usr offline on olbs1.in?] olbs1.in.t /export2 lev 0 FAILED [disk /export2 offline on olbs1.in?] olbs1.in.t /home lev 0 FAILED [disk /home offline on olbs1.in?] STATISTICS: Total Full Daily -------- -------- -------- Estimate Time (hrs:min) 0:00 Run Time (hrs:min) 0:00 Dump Time (hrs:min) 0:00 0:00 0:00 Output Size (meg) 0.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.0 Avg Compressed Size (%) -- -- -- Filesystems Dumped 0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min) 0:00 0:00 0:00 Tape Size (meg) 0.0 0.0 0.0 Tape Used (%) 0.0 0.0 0.0 Filesystems Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- USAGE BY TAPE: Label Time Size % Nb daily1-001 0:00 0.0 0.0 0 NOTES: planner: Adding new disk olbs1.in.:/home. planner: Adding new disk olbs1.in:/export2. planner: Adding new disk olbs1.in:/usr. planner: Adding new disk olbs2.in:/home. planner: Adding new disk olbs2.in:/usr. driver: WARNING: got empty schedule from planner taper: tape daily1-001 kb 0 fm 0 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -------------------------- --------------------------------- ------------ olbs1.in.tel /export2 0 FAILED --------------------------------------- olbs1.in.tel /home 0 FAILED --------------------------------------- olbs1.in.tel /usr 0 FAILED --------------------------------------- olbs2.in.tel /home 0 FAILED --------------------------------------- olbs2.in.tel /usr 0 FAILED --------------------------------------- (brought to you by Amanda version 2.4.4) ----- Original Message ----- From: "Jon LaBadie" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 03, 2003 12:04 PM Subject: Re: having problems connecting to clients > On Tue, Jun 03, 2003 at 11:55:03AM +1000, Joseph Sirucka wrote: > > Hi All > > > > seems my amanda server has problems trying to connect to my amanda > clients. > > > > Client and server are 2.4.4 and have the rightfull entries in the > /etc/inetd.conf. > > > > I have tried to telnet to each client upon port 10080 with connection > refused. > > > > A futile effort at best. Telnet is a tcp application. Check your > entries > in the services file. amanda on port 10080 is udp. You have no tcp > applications > on that port so of course a telnet is refused. > > Why you are having problems I have no idea. However, some actual > results > rather than anecdotal "it doesn't work" is always a good idea. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road (609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) >
