[jadmin] Jabberd14-1.6.1, was: Jabberd14 s2s crash

[Ingo Schwarze]

Hi Matthias,

Matthias Wimmer wrote on Fri, Mar 16, 2007 at 06:41:46PM +0100:

> Soon. It's already feature complete. Just debugging, bug fixing and 
> updating documentation is left.

In that case, i should like to ask whether the following NOTICE
is still up to date:

  schwarze at athene[4.1cb] $ jabberd14 --version
  jabberd14 version 1.6.0

  The following optional features have been enabled:
  - support for TLS using OpenSSL
  - logging to syslog

  Default config file is: /etc/jabberd14/jabber.xml
  Locales are in: /usr/local/share/locale

  For more information please visit http://jabberd.org/
  If you need support, check out http://jabberd.org/gettingSupport

  NOTICE: With the next release of this software, this package
          will get renamed to 'xmppd'. (http://xmppd.org/)

Will jabberd14 actually be called "xmppd" in release 1.6.1?

The reason why i'm asking is that i'm currently working on an
OpenBSD port of jabberd14.  What i have done so far is based
on OpenBSD 4.1-current and jabberd14-1.6.0.  It configures,
builds, installs, deinstalls, and runs fine as far as i can see
from tests on an internal server.  Before publishing the port,
i would want to migrate our Internet server to it, testing it
under real-life conditions.  Once that is done, i would submit
it to the OpenBSD team for inclusion in the ports tree (which
doesn't guarantee it will be taken up, but we shall see).
Now, in case it will be renamed, i should start using the new
name right from the beginning.  Renaming CVS directories is all
but fun.

Btw - which is off topic in this thread, but possibly not on this
list - we are considering to migrate off jabberd2 because of
experiencing instability in various respects:
 * A colleague fixed a connection closing bug in jabberd2/s2s
   long ago.  That bug badly bit us in production, eating up
   file descriptors and CPU.  See
   http://j2.openaether.org/bugzilla/show_bug.cgi?id=23
   When i last checked, jabberd2.1 still contained the same
   bug; we never heard anything from anybody upstream.
 * Mike Erdely collected ample evidence for additional file
   descriptor leaks in jabberd2-2.0s11 which reproducibly
   brought down his server even with our patch applied,
   see the openbsd-ports list archives for (part of) the details.
 * The contents of the jabberd2-2.0 bug tracking system was
   never migrated to the new jabberd2-2.1 bug tracking system.
 * Trying to upgrade the OpenBSD jabberd2-2.0s11 port to
   the newer release jabberd2-2.1, both Mike Erdely and myself
   failed miserably.  It seems as if new problems have been added
   which do not look trivial to sort out.  I'm well aware it is
   unfortunate that i cannot explain this more precisely, but i
   simply do not yet fully understand what goes wrong.  The port
   builds all right, but the server crashes due to some linkage
   problems we do not yet understand.
 * Finally, the official maintainer of the OpenBSD jabberd2 port,
   Gerardo Santana, gave up on the port; as far as i understand,
   because he feared to be unable to assure reliability for
   production use.

For these reasons, we guessed that giving jabberd14 a try might
be easier than fixing jabberd2.  Up to this point, it looks
promising indeed.

Yours,
  Ingo

-- 
Ingo Schwarze <schwarze at usta.de>
Serverbetrieb usta.de / studis.de