-
Notifications
You must be signed in to change notification settings - Fork 16
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
The 2015-02-22 update broke something #65
Comments
The changes were pretty minor and affected threads that are not yet enabled in production, so they at least shouldn't have caused the problem. Could it be that the znc somehow opened the connection to the server twice when the connection was lost? |
I've also tried that now and still everything comes twice. |
Whatever, I tried it now.
and I just used KVIrc 4.2.0 in Windows instead of Quassel, same story. |
OK, last comment for now: |
OK, I seem to have fixed it now, seems to be either a problem with znc or the combo. I installed oulu locally to try to reproduce it.
so no clue if you changed something since yesterday or just the reconnecting to another oulu instance made it, but it works now. Simple reconnect wouldn't. |
Reopening because I just had this again. Got disconnected (as it often happens, but I wouldn't care)
I've been using this version of znc and quassel for months without problems, but since the weekend it's kind of broken. |
The logs would seem to indicate that we're getting 2 connections/logins within a couple of milliseconds from the znc. If you look at the znc with e.g. lsof or netstat, does it also show two established connections? I'll try to install znc to see if I can reproduce it. |
Hi,
when connecting this morning (talking about team wywy on flowdock.com) everything looked ok, until...
Reconnecting does not fix it. This happens
a) when I write on irc
b) when I write on flowdock.com
While my setup is a bit convoluted (quasselclient connects to remote quasselcore, quasselcore connects to local znc, znc connects to flowdock) it has worked until this morning on irc and flowdock.
The text was updated successfully, but these errors were encountered: