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 434980 - "Get new headers" task gets stuck in queue if one server is unreachable
"Get new headers" task gets stuck in queue if one server is unreachable
Status: RESOLVED OBSOLETE
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other All
: Normal normal
: ---
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2007-05-01 19:02 UTC by freggy1
Modified: 2011-12-03 18:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description freggy1 2007-05-01 19:02:59 UTC
Please describe the problem:
I have different news servers configured in Pan, one of them is GMane. When clicking o a group only present in GMane, Pan correctly downloads the headers, but the task is not removed from the queue when another server than GMane is not reachable. In a wireshark dump, I see that Pan continues to contact the unreachable news server every five seconds. While Pan is doing this, no new headers appear in the group, until I delete the task.

[problem also discussed in pan-users mailing list, subject Pan 0.120 only queuuing tasks"]

Steps to reproduce:
1. Configure two servers in Pan, for example news.gmane.org and an IP address on which no NTTP server is listening
2. Get new headers in a group from GMane, by clicking on the group in the group list


Actual results:
The status bar says: "Tasks 1/1", and headers are downloaded from GMane. The status bar changes to "Tasks 0/1". No new headers appear in the group. The task remains stuck in the queue. Wireshark shows that Pan tries to connect every five seconds to the server on which the NNTP port is closed.

Expected results:
Pan should immediately show new headers from the group, and the task should not remain in the queue. Pan could show a warning in the status bar that server XXXX did not respond.

Does this happen every time?
Yes

Other information: