Re: mu-conference, gna, future

Does anybody know what happened or is happening with GNA? Might it be coming back? Apparently it went away quite a while ago, and it's not coming back. Is anybody still using mu-conference? (I'm not personally, but do know of one significant-size installation.) No one spoke up. Is

mu-conference, gna, future

mu-conference is an implementation of xmpp conference rooms. It worked with jabberd 1.4 (and might still) and works with jabberd 2. It might be the standard approach for conferencing with jabberd2: https://github.com/jabberd2/jabberd2/wiki/InstallGuide-MU-Conferencing Around 2013 hosting

Re: jabberd-2.5.0 release

Thanks for making a release. Updated in pkgsrc, and tested on netbsd-6 i386 (in a Xen domU, not that it should matter). Now, sm starts on boot. I do see 'reopening log' in the log, so it must still be getting the HUP. But nothing is amiss, and I can log into my server without having to

sm crashing on startup

I have a NetBSD 6 system, with jabberd 2.4.0 (built for netbsd 5 still. Although binary compat at this level is almost beyond suspicion, I am rebuilding all packages) . Jabberd mostly works fine, but on boot sm crashes. I have adjusted sequencing, although in theory it should not matter (and

Re: stale connections, keepalive?

Tomasz Sterna writes: > See io.keepalive [1][2] options. > Setting this up will flush single whitespace character over the wire > when the connection dangs idle. This triggers the TCP layer connection > validation. I set this up as: check every 300 close connections idle

Re: stale connections, keepalive?

Tomasz Sterna writes: > jabberd2 has support for application layer keepalives. > > See io.keepalive [1][2] options. > Setting this up will flush single whitespace character over the wire > when the connection dangs idle. This triggers the TCP layer connection > validation.

Re: stale connections, keepalive?

Christof Meerwald <cme...@cmeerw.org> writes: > On Sun, Aug 28, 2016 at 02:13:34PM +0200, Tomasz Sterna wrote: >> W dniu 27.08.2016, sob o godzinie 14∶55 -0400, użytkownik Greg Troxel >> napisał: >> >   should jabberd2 force TCP keepalive on? >> I'm not sure

stale connections, keepalive?

I have a server running 2.3.6 on NetBSD. It has been basically working fine. I connect to it with Conversations on Android, and the nature of phones is that they switch from wifi to cellular a lot, and I think this leads to dangling connections. keepalive is apparently not default on NetBSD,

Re: Future of jabberd

I'd also like to see multi-user conferencing integrated. I did a little maintenance on the muc plugin a few years ago, but the code is still too scary.

Re: jabberd-2.4.0 release

Tomasz Sterna writes: > Next jabberd2 release is available. > > Get 2.4.0 release at GitHub: > https://github.com/jabberd2/jabberd2/releases > > This is a bugfix release. Does this imply that it should be safe, aside from cautions in NEWS, to update a machine running 2.3.x to

Re: XMPP SPAM

Simon Josefsson writes: > I'm running my own jabberd2 server since a couple of months. For the > past 2-3 weeks I've been starting to receive XMPP spam (a couple of > times per week). Is there some configuration that could help here, or > do how people handle this?

Re: crashing at startup?

e...@cirr.com (Eric Schnoebelen) writes: I've not see anything like that on NetBSD 6_STABLE/alpha. I do see mu-conference crashing semi-regularly, as well as it occasionally running away (but not nearly as much after the last set of patches.) It's cool you are running this on alpha. The

crashing at startup?

On a netbsd-5 i386 box (xen domU) that is otherwise stable, with jabberd 2.3.2 and mu-conference 0.8.81, on boot we saw: Feb 6 05:33:34 foo /netbsd: pid 317 (sm), uid 1001: exited on signal 11 (core not dumped, err = 13) Feb 6 05:34:26 foo /netbsd: pid 540 (mu-conference), uid 1001: exited on