Differences between revisions 3 and 4
Revision 3 as of 2013-09-08 22:16:58
Size: 1918
Editor: host109
Comment: clarify that xmlconsole debugging can be added or removed when already connected
Revision 4 as of 2014-09-22 20:12:35
Size: 1640
Editor: dx
Comment: remove comment that makes 3.0.3 sound like it's bleeding edge
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
Annoyingly, non-debugging (i.e. the --debug= configure setting) binaries don't produce as much debugging output as debugging binaries. Or at least, this was the case until and including version 3.0.3. If you're using the nightly snapshots from code.bitlbee.org, you're fine.

Getting debugging info out of BitlBee

For long, this has been hard or even impossible. Unfortunately, depending on what you want, it still is. As I'm rewriting parts of BitlBee, I'm adding debugging hooks to them now. Since BitlBee is a daemon, it will always be a little more complicated to get debugging output though.

In all cases, be careful. The output is not stripped from private info like your IM passwords. If you're sharing info on something like pastebin, make sure you strip out the passwords first.

First of all, ignore the debug setting. It's useless. It should probably be removed.

XMPP/Jabber debugging

This one's easy, and works even if you're on a public server.

Before connecting, you can enable xmlconsole to get raw XMPP traffic in a PM window from the _xmlconsole contact:

account jabber set xmlconsole true

Or, if already connected, you can add and remove the _xmlconsole contact like this:

add jabber _xmlconsole
remove _xmlconsole

Also, it will let you send raw XML to the server yourself. But be careful, if you send something invalid the server on the other end will probably disconnect you!

Other debugging

To get debug output, you have to launch BitlBee by hand instead of from the init script, with the BITLBEE_DEBUG=1 environment variable set. Also, you should pass some flags so it won't daemonise (and close stdout, stderr, etc.).

In short, something like this:

BITLBEE_DEBUG=1 /usr/sbin/bitlbee -nD

Again, be careful when sharing this output on the bug tracker/pastebin/etc as it may contain your password.

BitlBee Wiki: Debugging (last edited 2016-10-12 23:10:01 by dx)