|
⇤ ← Revision 1 as of 2011-12-02 11:16:06
Size: 1697
Comment:
|
Size: 1776
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| This one's easy, and works even if you're on a public server. Just add `xmlconsole` to your contact list and you'll get raw XMPP traffic from that contact. 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! | This one's easy, and works even if you're on a public server. Make sure `acc $jabber set xmlconsole true` is enabled in the account settings, and add `xmlconsole` to your contact list and you'll get raw XMPP traffic from that contact. 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! |
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. Make sure acc $jabber set xmlconsole true is enabled in the account settings, and add xmlconsole to your contact list and you'll get raw XMPP traffic from that contact. 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
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.
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.