After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 364357 - Repeated server error messages
Repeated server error messages
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other Linux
: Normal major
: 1.0
Assigned To: Charles Kerr
Pan QA Team
: 358057 361998 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-23 06:45 UTC by J.D.
Modified: 2006-11-02 17:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
first draft patch (4.84 KB, patch)
2006-10-30 15:47 UTC, Charles Kerr
none Details | Review
prettier revision (6.02 KB, patch)
2006-10-30 23:09 UTC, Charles Kerr
committed Details | Review

Description J.D. 2006-10-23 06:45:21 UTC
When a server error is encountered the error message window keeps popping up every 3-4 seconds.  Further, if you don't keep up with clicking the ok button to dismiss it, multiple copies of the error window stack up.  Very annoying.

I first noticed this several versions ago.  It is still a problem in .117.

In case it matters, I'm running Ubuntu 6.06 (gnome).
Comment 1 Duncan 2006-10-23 11:37:11 UTC
Thanks for filing this. =8^)

Charles, I asked him to file it after he mentioned it in the Cox groups, as I haven't been getting the errors for whatever reason.  A bit more info from there:  Cox is beta testing some new news servers (outsourced from highwinds-media).  These are officially limited to four connections shared between two servers, so the most logical split would be two connections to each.  The problem seems to be that these connections are extremely touchy, and many (not just on pan) are experiencing 502 (IIRC) errors -- too many connections, even when they have the proper number of connections configured.  (As I said, for whatever reason, config, better physical connection, whatever, I've not seen these.  <shrug>)

One of the recent pan changes was of course making these errors a bit more visible, with a popup instead of just logging them.  Great, except that there needs to be some limit to the popups.  Perhaps once every 2 minutes or 5 minutes?  Also, checking to see if there's already an error popup and canceling the next one if the last one still exists (while continuing to log, but even there, maybe limit it to one every thirty seconds if the last error was identical) is probably wise.

I'd suggest that this needs to make it for 1.0, or if that's not possible, at least for 1.0.1 or whatever the first stable fix series release version is.  I've found rather more pan users on Cox than I thought existed =8^), and the new multi-server features seem popular, but several have found pan unworkable with these constant popups.  If the fix doesn't make it for 1.0, I could see this being the biggest complaint. =8^(

Duncan
Comment 2 Charles Kerr 2006-10-30 15:47:10 UTC
Created attachment 75668 [details] [review]
first draft patch

This patch is more a band-aid than a true fix, but I'm uploading it to leave breadcrumbs for myself and to aid anyone who's hitting this wall right now. This patch does the following: (1) only pop up one offline error message, rather than a flood of them, and (2) don't go offline in the first place as the result of a `too many connections' error.  Rather, throttle back new connections for the next two minutes.
Comment 3 Charles Kerr 2006-10-30 15:48:27 UTC
*** Bug 361998 has been marked as a duplicate of this bug. ***
Comment 4 Charles Kerr 2006-10-30 23:09:10 UTC
Created attachment 75700 [details] [review]
prettier revision
Comment 5 Charles Kerr 2006-10-31 01:37:42 UTC
*** Bug 358057 has been marked as a duplicate of this bug. ***