Stan's not alone on this one. I have two OpenBSD 4.5 machines also on Sun
SPARC hardware. I had this same trouble a couple months ago with 2.6.1, but
didn't have time to look deeper. After seeing this discussion, I built
amanda-2.6.2alpha-20090812 (can't get 0820 to compile). I'm getting exactly
the same errors. I tried dump with and without compression.

My Amanda server is on Solaris 10, and I have a mix of Solaris, Linux, and
OpenBSD systems. Except for the above-mentioned build, everything is at
2.6.1p1. There are no firewalls on the Amanda server or the OpenBSD clients.

I know "me too" responses aren't usually helpful, but maybe this will rule
out the firewall question, at least.


On Fri, Aug 21, 2009 at 1:37 PM, stan <st...@panix.com> wrote:

> On Fri, Aug 21, 2009 at 01:23:29PM -0600, John Hein wrote:
> > stan wrote at 13:56 -0400 on Aug 21, 2009:
> >  > OK, I reproduced the failure with only a crossover cable between the
> test
> >  > client and the Amanda Master:
> >
> > Just because you're using a crossover cable doesn't rule out firewall
> > or other such socket level interference.  I'm not saying that's your
> > problem, but using a crossover cable doesn't rule it out.
> >
> Fair enough, but I think we can rule that out in this case. First, I
> control the 2 computersin question. The Master backus up 55 machines a day
> taht consist of a diverse nix of OS'es, and Amanda versions. It's a Linux
> machine, and I am not running a firwall on it. The client is an OpenBSD
> machine. I use these for my firewalls, so I am familiar with configuring
> firewalls on them, Doing so requires (as a minimum) running pf. I am not
> running pf on the test machine at all.
>
> I am not certain whether the sendbackup executable, or amandad opens the
> port on the client side. My guess is that it is not suceding in doing this.
> Thus when the Master tries to connect to it, there is no port for it to
> connect to.
>
> --
> One of the main causes of the fall of the roman empire was that, lacking
> zero, they had no way to indicate successful termination of their C
> programs.
>

Reply via email to