Hi John
I will download the latest cvs and compile it. I hope it won't have any
problems working with 2.4.1p1 (the version I'm currently using). The only
caveat. It will take me at ;east until middle of next week to finish this
(too much real work to do). Guilty as charged,
I upgraded the SSH client server from 2.3.0p1 to 2.5.2p2 :) In the mean time
I found a couple of other clues: syslog reports the following:
Mar 22 18:22:07 dexter amandad[10069]: open debug file
"/tmp/amanda/amandad.debug": File exists
Mar 22 18:22:07 dexter inetd[10028]: amanda/udp server failing (looping or
being flooded), service terminated for 10 min
1. killing inetd and restarting it didn't help.
2. trying to view the debug information in /tmp/amanda game me the error:
Input/output error. Trying to `rm` `file` gave the same error.
Hope this helps.
"John R. Jackson" wrote:
> >send req failed: Connection refused
> >protocol packet receive: Connection refused
> >protocol packet receive: Connection refused
>
> I can tell you what Amanda is doing, but not why your system is reporting
> this error to Amanda.
>
> Amanda has created a socket and then done a sendto() to ship a UDP packet
> from your server to one of the clients, presumably "dexter". That call
> reported back "Connection refused", which Amanda retried several times
> but eventually gave up on.
>
> I've added a whole lot more debugging messages in the network code.
> Is there any chance I could convince you to get the latest 2.4.2 CVS
> sources and at least build them (you would not need to actually install)?
> You could "chown root" and "chmod u+s" that version of amcheck and run it
> from the build area (make sure you use the binary, not the funny shared
> library wrapper script of the same name, but use the wrapper script to
> run it, or you can build with --disable-shared to turn all this off just
> for testing), then look at /tmp/amanda/amcheck*debug to see what it did.
>
> >BTW: The isn't a new one and nothing changed in the environment.
>
> Yeah, right. How often have I heard that story. :-)
>
> Clearly something related to "dexter" has changed that is causing packets
> to not be able to be delivered (in fact, they are being explicitly
> refused). I'd start checking that client to make sure inetd is happy
> and listening to the Amanda port, that there are no firewall problems,
> that the name <-> IP mapping is right from the server, and so on.
>
> > Paolo
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
