From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36973 Path: main.gmane.org!not-for-mail From: Henrik Enberg Newsgroups: gmane.emacs.gnus.general Subject: Re: (wrong-type-argument processp nil) Date: 20 Jul 2001 14:44:35 +0200 Message-ID: References: <87ae269y5r.fsf@cachemir.echo-net.net> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172468 11412 80.91.224.250 (21 Oct 2002 03:54:28 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:54:28 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 17828 invoked from network); 20 Jul 2001 12:44:54 -0000 Original-Received: from fep04.swip.net (HELO fep04-svc.swip.net) (130.244.199.132) by gnus.org with SMTP; 20 Jul 2001 12:44:54 -0000 Original-Received: from rocksteady.enberg.org ([212.151.169.216]) by fep04-svc.swip.net with ESMTP id <20010720124401.HCBO17855.fep04-svc.swip.net@rocksteady.enberg.org> for ; Fri, 20 Jul 2001 14:44:01 +0200 Original-Received: by rocksteady.enberg.org (Postfix, from userid 500) id 2DC2D1C255; Fri, 20 Jul 2001 14:44:35 +0200 (CEST) Original-To: ding@gnus.org X-Face: "5wt-]2B9og!o1fh;x.'C>fruC{XQY4sue`8vh}B:'9K7@188fx#CM~A^Oh{W^l#bRv6 In-Reply-To: (Rupa Schomaker's message of "Wed, 18 Jul 2001 09:45:59 -0700") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.104 Original-Lines: 20 Xref: main.gmane.org gmane.emacs.gnus.general:36973 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36973 Rupa Schomaker wrote: > Roland Mas writes: > >> I've come across this error message recently (ie. maybe for a month or >> so). It happens when I gnus-get-new-news, possibly after a while. It >> seems the socket dies (firewall might be involved in it), and Gnus >> fails to handle it correctly. Here comes the backtrace (I'm unable to >> understand what parts of it are relevant, so I paste it all). > > When I switched from an ipchains (RH 7.0) based firewall to an > iptables (debian woody 2.4.5 kernel) this problem disapeared. It was > (for me at least) definitely a interraction with my firewall. Fwiw, I seem have the exact same problem (even if I don't get any errors, it just won't connect) and I run ipchains on RH 7.1. I guess its time to move to iptables. Henrik -- I always have fun because I'm out of my mind!!!