Subject: Re: jabberd 1.4.2 fails on netbsd-4
To: Greg Troxel <firstname.lastname@example.org>
From: David Brownlee <abs@NetBSD.org>
Date: 04/18/2007 11:12:26
On Tue, 17 Apr 2007, Greg Troxel wrote:
> I have a machine running jabberd 1.4.2nb5 and squid. It was 3.99.15,
> and I just upgraded it to 4.0_BETA2 (cvs from yesterday). It's
> XEN2_DOMU, but I suspect that doesn't matter.
> jabberd accepted connections on 5223 but apparently didn't read the
> data. ps said it was in pipewait. I rebuilt jabberd fresh on another
> netbsd-4 machine (running binaries built from the same build as the
> jabber server), but it behaved the same way.
> I know jabberd has its own pth, so I suspect some bad pth interaction.
> This server is too important, so I downgraded to the netbsd-3 branch and
> it's now running fine.
> I'll look into this on another netbsd-4 machine.
> If anyone has advice about how to debug this other than running jabberd
> under gdb or ktrace (which I'll try), experience with jabberd under
> netbsd-4, or advice about updating to jabberd 2 or something else (I
> need SSL/TLS, and to require on the server that only SSL/TLS connections
> are accepted), I'd appreciate it.
I have two NetBSD 4.0_BETA2 machines running jabberd 2,
one of which is running a native jabberd-2.0s11 package
and the other (for reasons outside of my direct control)
is running a jabberd-2.0s4 compiled under NetBSD 2.0.
Both enforce 'old style' SSL connections on port 5223
David/absolute -- www.NetBSD.org: No hype required --