Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection lost to bitlbee on account on #23

Closed
AshCarnelian opened this issue Mar 31, 2016 · 5 comments
Closed

Connection lost to bitlbee on account on #23

AshCarnelian opened this issue Mar 31, 2016 · 5 comments
Labels

Comments

@AshCarnelian
Copy link

on acc discord on or acc on, irc immediately loses connection to bitlbee. Upon reconnect, bitlbee has forgotten about the account.

0319 @johnny acc add discord (EMAIL) (PASS)
0319 @root Account successfully added with tag discord

0319 @johnny acc discord on
0319 -- irc: disconnected from server

0321 @root Password accepted, settings and accounts loaded
0321 @root No accounts known. Use `account add' to add one.

@sm00th
Copy link
Owner

sm00th commented Mar 31, 2016

Looks like you stumbled upon something interesting. Might be some unexpected discord "server" configuration. Can you try getting a backtrace as described here? (you don't have to rebuild bitlbee in this case)

@rookiejet
Copy link

Similar issue, libwebsockets compiled from git

#0 0x00007fffe7e3f7ab in ?? () from /usr/lib/bitlbee/discord.so
#1 0x00007fffe7c28d1c in lws_create_vhost () from /usr/lib/libwebsockets.so.7
#2 0x00007fffe7c29391 in lws_create_context ()
from /usr/lib/libwebsockets.so.7
#3 0x00007fffe7e3fad6 in discord_ws_init () from /usr/lib/bitlbee/discord.so
#4 0x00007fffe7e3e636 in ?? () from /usr/lib/bitlbee/discord.so
#5 0x000055555557a2ef in ?? ()
#6 0x00005555555790e5 in ?? ()
#7 0x00007ffff760bc3a in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#8 0x00007ffff760bfe0 in ?? () from /usr/lib/libglib-2.0.so.0
#9 0x00007ffff760c302 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#10 0x0000555555563e87 in main ()

@sm00th
Copy link
Owner

sm00th commented Apr 6, 2016

Found a couple of problems in this area:

  • Discord now reports gate without the trailing "/" so it upsets libwebsockets, fixed by 83167e3
  • Current libwebsockets seem to has ssl connections broken.

@rookiejet, although none of the above seem to be related to your backtrace, can you try to build a stable version of libwebsockets (1.7.5 seems to work, you can check it out by running git checkout v1.7.5) and then pull the fix and rebuild bitlbee-discord?

@rookiejet
Copy link

It does seem to work with libwebsockets v1.7.5, it no longer segfaults. Thanks for the help! It logs this on successful connection though, I don't know how meaningful it is:

discord_ws_callback: unknown rsn=22

But it is working fine so far.

@sm00th sm00th added the bug label Apr 8, 2016
@sm00th
Copy link
Owner

sm00th commented Apr 8, 2016

discord_ws_callback: unknown rsn=22

That is just a debug message and is normal.

Closing this issue for now, @JohnnyWarpzone if you still experience problems with connecting you can reopen it.

@sm00th sm00th closed this as completed Apr 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants