Project

General

Profile

Bug #729

No ping reply in 90 seconds

Added by MJ94 over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
06/24/2009
Due date:
% Done:

0%

Estimated time:
Version:
0.4.2
OS:
Any

Description

Quassel is constantly pinging out. Is that Quassel's default ping out message? Normally, in fact every time, unless the user was using Quassel, ping timeout is the quit. Not no ping reply in 90 seconds? What is this new quit? Quassel needs to PONG better. I'm constantly getting disconnected and others are too! Thanks for a great client!

History

#1 Updated by dalbers over 10 years ago

Please run the core with --loglevel=Debug and provide the output here.

#2 Updated by MJ94 over 10 years ago

dalbers wrote:

Please run the core with --loglevel=Debug and provide the output here.

Same as normal:

mj94@negative:~$ screen ./quassel -p 4250 --loglevel=Debug
2009-07-03 20:03:02 Warning: SslServer: Certificate file /home/mj94/.config/quassel-irc.org/quasselCert.pem does not exist
2009-07-03 20:03:02 Warning: SslServer: Unable to set certificate file
Quassel Core will still work, but cannot provide SSL for client connections.
Please see http://quassel-irc.org/faq/cert to learn how to enable SSL support.
2009-07-03 20:03:02 Warning: SslServer: Certificate file /home/mj94/.config/quassel-irc.org/quasselCert.pem does not exist
2009-07-03 20:03:02 Info: Storage Backend is ready. Quassel Schema Version: 14
2009-07-03 20:03:02 Info: Listening for GUI clients on IPv4 0.0.0.0 port 4250 using protocol version 9
2009-07-03 20:03:02 Info: Restoring previous core state...
2009-07-03 20:03:16 Info: Client connected from <IP REMOVED>
2009-07-03 20:03:16 Debug: Using compression for Client: <IP REMOVED>
2009-07-03 20:03:22 Info: Client <IP REMOVED> initialized and authenticated successfully as "MJ94" (UserId: 1).

Same as always, and I always see these types of ping outs from Quassel. From #Quassel:

<-- kysh (n=) has quit ("No Ping reply in 90 seconds.")
<-- scarabeus (n=scarab@gentoo/developer/scarabeus) has quit ("No Ping reply in 90 seconds.")
<-- otih (n=otih@CAcert/Assurer/otih) has quit ("No Ping reply in 90 seconds.")

Those are examples of the Quassel specific ping timeout. No other client shows the ("No Ping reply in 90 seconds.") Most clients say (Ping timeout). So, why does Quassel ping out so often and why does it have it's own ping out message?

#3 Updated by Sputnick over 10 years ago

  • Status changed from New to Resolved
  • Assignee set to Sputnick
  • Target version set to 0.5.0

Also available in: Atom PDF