Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 71859 invoked by uid 500); 30 Aug 2002 01:21:51 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 71846 invoked from network); 30 Aug 2002 01:21:50 -0000 X-Authentication-Warning: localhost.localdomain: trawick set sender to trawick@attglobal.net using -f Sender: trawick@localhost.localdomain To: dev@httpd.apache.org Subject: Re: 2.0.40 (UNIX), mysterious SSL connections to self References: From: Jeff Trawick Date: 29 Aug 2002 21:21:27 -0400 In-Reply-To: Message-ID: Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "jb2002@pc9.org" writes: > Looking into the matter, I discovered that this error is logged whenever a > connection from localhost to localhost:443 is made. The errors ALWAYS occur > after apachectl startssl; they never occur with apachectl start. I'd bet that this is idle server maintenance (taking down a child process which isn't necessary). The non-SSL path doesn't log an error for a dummy connect but evidently the SSL path does. The connect to itself isn't a bug, though it would be nice to avoid the SSL complaints. Try swapping the order of your listen statements to see if that gets rid of the complaints (i.e., if the dummy connect to wake up a child is then done to the non-SSL socket). -- Jeff Trawick | trawick@attglobal.net Born in Roswell... married an alien...