Recently a contact of mine sent me an e-mail saying that he didn't see me online for weeks, asking whether something's broken with my Jabber server. I started investigating and found out that indeed server-to-server connections between my host and <> didn't work since I rebooted the server machine on December 20.

First I thought that the problem was based on , because jabber.ccc.de requires support for them. There is a nice howto page on the <> about <>, but running the provided <> showed that SRV already worked quite fine on my server.

Peeking into the log files I saw messages about a module called PKIX1Explicit88 and that it could not be loaded. On Gentoo, stuff like that is caused mostly by that were broken when updating packages, and solved by updating dependent software. So what I did was to try re- and , only to find out that the ejabberd compile would die.

Enter <>. I found two bugs about this problem, namely <> which basically says uhm, it's somehow broken with Erlang 12B, but we don't know why, and <> which explained why only a handfull of people experienced this bug: It seems like you have to use the unstable branch of Gentoo and the "hardened" profile, and ejabberd. As <> on the bug: Well, this completely breaks SSL support on hardened, causing b0rkage w/ stuff like net-im/ejabberd.

I now had three choices: Wait for the developers to resolve the problem, work on the bug myself or downgrade Erlang. Since I was in a bit of a hurry, I decided for the latter, and now my Jabber server works flawlessly again.

Oh, by the way, I must admit that I'm a bit (or maybe more) scared about what is being said in the first bug, starting from <>: I feel that ejabberd would benefit from a maintainer with actual erlang knowledge. [...] Christian, Jan, are you interested in maintaining this? — I have zero erlang knowledge [...] — I only maintain Erlang because of sense of duty...I know nothing about it.