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

The 2015-02-22 update broke something #65

Open
winks opened this issue Feb 23, 2015 · 7 comments
Open

The 2015-02-22 update broke something #65

winks opened this issue Feb 23, 2015 · 7 comments

Comments

@winks
Copy link

winks commented Feb 23, 2015

Hi,
when connecting this morning (talking about team wywy on flowdock.com) everything looked ok, until...

[10:16:46] <Florian> o_O
[10:16:47] <Florian> o_O
[10:16:54] <Florian> I see evry line twice. doh
[10:16:54] <Florian> I see evry line twice. doh

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.

@tsilen
Copy link
Contributor

tsilen commented Feb 23, 2015

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?

@winks
Copy link
Author

winks commented Feb 23, 2015

I've also tried that now and still everything comes twice.
I'll see if I can reproduce it on something else connected to znc later

@winks
Copy link
Author

winks commented Feb 23, 2015

Whatever, I tried it now.
my znc is

ii  znc                              0.092-3

and I just used KVIrc 4.2.0 in Windows instead of Quassel, same story.

@winks
Copy link
Author

winks commented Feb 23, 2015

OK, last comment for now:
I created a new user on the same box, created a 100% new znc config, connected with KVIrc - every message arrives a second time, no matter if I send it via web or irc.

@winks
Copy link
Author

winks commented Feb 24, 2015

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.

  • znc1 reconnecting: no change
  • znc2: reconnecting: no change
  • znc2: connect to own oula, works
  • znc2: connecto to flowdock, works
  • znc1: connect to own oula, works
  • znc1: connecto to flowdock, works

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.

@winks winks closed this as completed Feb 24, 2015
@winks winks reopened this Feb 24, 2015
@winks
Copy link
Author

winks commented Feb 24, 2015

Reopening because I just had this again.

Got disconnected (as it often happens, but I wouldn't care)

[17:16:52] * #xxx/yyy: No such nick/channel
  • Reconnect, everything arrives duplicate.
  • go to znc webadmin, change server to anything, reconnect
  • change server back to irc.flowdock.com +6697 and it works.

I've been using this version of znc and quassel for months without problems, but since the weekend it's kind of broken.

@tsilen
Copy link
Contributor

tsilen commented Feb 24, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants