Project

General

Profile

Bug #1249

Quassel occasionally gets stuck while reconnecting to Freenode after a pingout

Added by mamarley over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Quassel Core
Target version:
-
Start date:
10/21/2013
Due date:
% Done:

100%

Estimated time:
Version:
0.9-pre
OS:
Linux

Description

I am running a Quasselcore compiled from the latest code from git (as of 20131021) and I have an issue where Quassel will sometimes get stuck while reconnecting to Freenode after a pingout. Quassel will say that it is connecting to the server, but will remain in this state for multiple hours without either connecting or timing out and making another attempt. The only way I have been able to get it to reconnect was to press the "Disconnect" button several times until "Connect" becomes available, and then press "Connect."

If it matters, I am using SSL and IPv6.

Associated revisions

Revision 9b8923e3 (diff)
Added by mamarley over 6 years ago

Enable the ping timeout as soon as the connection to IRC is open.

This fixes the problem where Quassel would get stuck while connecting
if the socket is closed by the server but the core is, for whatever
reason, not notified of this. This patch works by enabling the ping
timeout as soon as the connection is open, but not actually sending any
PINGs until the IRC authentication is complete. This will cause the core
to reconnect if at any point it doesn't receive data from the server for
more than the usual ping timeout interval.

Fixes #1249

Revision d8c55414 (diff)
Added by mamarley over 6 years ago

Enable the ping timeout as soon as the connection to IRC is open.

This fixes the problem where Quassel would get stuck while connecting
if the socket is closed by the server but the core is, for whatever
reason, not notified of this. This patch works by enabling the ping
timeout as soon as the connection is open, but not actually sending any
PINGs until the IRC authentication is complete. This will cause the core
to reconnect if at any point it doesn't receive data from the server for
more than the usual ping timeout interval.

Fixes #1249

History

#1 Updated by mamarley over 6 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset quassel|commit:9b8923e3625b5634163b5c164df8fa6a3760f660.

Also available in: Atom PDF