From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/83798 Path: news.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: Freeze up on general news scan (g) Date: Sun, 06 Oct 2013 13:54:29 -0400 Organization: Still searching... Message-ID: <871u3y1e0a.fsf@newsguy.com> References: <87mxda84nc.fsf@newsguy.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1381082112 12081 80.91.229.3 (6 Oct 2013 17:55:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Oct 2013 17:55:12 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M32054@lists.math.uh.edu Sun Oct 06 19:55:16 2013 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VSsXz-0005Wi-O9 for ding-account@gmane.org; Sun, 06 Oct 2013 19:55:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1VSsXd-0002WV-4e; Sun, 06 Oct 2013 12:54:53 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1VSsXZ-0002Vx-Mr for ding@lists.math.uh.edu; Sun, 06 Oct 2013 12:54:49 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1VSsXU-0005Li-F3 for ding@lists.math.uh.edu; Sun, 06 Oct 2013 12:54:49 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1VSsXS-0007YI-Gl for ding@gnus.org; Sun, 06 Oct 2013 19:54:42 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VSsXS-0005Nk-8g for ding@gnus.org; Sun, 06 Oct 2013 19:54:42 +0200 Original-Received: from z65-50-57-227.ips.direcpath.com ([65.50.57.227]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Oct 2013 19:54:42 +0200 Original-Received: from reader by z65-50-57-227.ips.direcpath.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Oct 2013 19:54:42 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: z65-50-57-227.ips.direcpath.com User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.0.92 (gnu/linux) Cancel-Lock: sha1:iRUzPjAzOesQbPL8S0EubQqEQNw= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:83798 Archived-At: Lars Magne Ingebrigtsen writes: > Harry Putnam writes: > >> For some time now I've been having a problem where when I do a general >> news scan (g) It doesn't ever finish. It doesn't always happen and >> has been a bit of problem getting a backtrace but finally got one >> posted below. > > I've now added further sanity checking to the async nntp retrieval > stuff. Does this fix this problem for you? I realize this is an old old thread... but I'm still having the problem and have had all this time. I've gotten so used to working around it that I kind of quit fussing with it... until, lately when I posted about it again and got some help from Katsumi, that seemed at first to fix things: It was some old code I had kicking around that was from way back with this post I'm responding to, was current. See the thread if interested: http://thread.gmane.org/gmane.emacs.gnus.general/83778 Or from gnus: Message-ID: <871u4cwiwu.fsf@newsguy.com> I've ditched that old code of mine, and after a few refreshes I'm back to having huge (never ending) waits when pressing 'g'. All nnml: nnimap: etc gets refreshed , the last being nnfolder... but when it hits the part where it nntp refresh...happens, it just never finishes. I doubt it is a server problem since any single newsgroup or any nntp server refreshes in a normal amount of time... I run in topics so if I hit M-g on all gmane groups, good refresh time. Ditto for newsguy.com and apn (forte-agent news service) It only the over all 'g' refresh that goes into infinity. If you do get a chance to respond to this message, I wonder how you would track down what is happening during that infinite wait. Watching the nntp-log buffer... doesn't show much... It seems to stop at newsguy, but like I said I can refresh all newsguy groups with M-g in a normal time frame. How to make gnus show me what it is doing, or where to look for that?