Subject: jabberd 1.4.2 fails on netbsd-4
To: None <firstname.lastname@example.org>
From: Greg Troxel <email@example.com>
Date: 04/17/2007 12:53:16
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.