Return-Path: Delivered-To: apmail-httpd-bugs-archive@www.apache.org Received: (qmail 97800 invoked from network); 5 Mar 2004 20:24:38 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Mar 2004 20:24:38 -0000 Received: (qmail 76481 invoked by uid 500); 5 Mar 2004 20:24:27 -0000 Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 76365 invoked by uid 500); 5 Mar 2004 20:24:26 -0000 Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Apache HTTPD Bugs Notification List" Delivered-To: mailing list bugs@httpd.apache.org Received: (qmail 76349 invoked from network); 5 Mar 2004 20:24:26 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 5 Mar 2004 20:24:26 -0000 Received: (qmail 28140 invoked by uid 50); 5 Mar 2004 20:24:58 -0000 Date: 5 Mar 2004 20:24:58 -0000 Message-ID: <20040305202458.28139.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: bugs@httpd.apache.org Cc: Subject: DO NOT REPLY [Bug 21425] - AcceptEx failed [semaphore timeout period has expired] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21425 AcceptEx failed [semaphore timeout period has expired] ------- Additional Comments From anynamewilldo4me@yahoo.com 2004-03-05 20:24 ------- I tried the Win32DisableAcceptEx and it wouldn't work. No matter where I put it, I get an error. C:\Apache2\bin>apache -k restart Syntax error on line 110 of C:/Apache2/conf/httpd.conf: Invalid command 'Win32DisableAcceptEx', perhaps mis-spelled or defined by a modu le not included in the server configuration I really need to use mod_perl, but after going live with a W2K server with 2.0.48, this bug is driving me crazy. If it doesn't get fixed, I'll have to back off and run IIS on the machine. Right now, I'm getting error logs that are about 500KB a day and are filled with these two releated errors: [Thu Mar 04 16:05:21 2004] [warn] (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 04 16:05:21 2004] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 04 16:05:21 2004] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. [Thu Mar 04 16:05:21 2004] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. Sometimes, the server goes to 50% utilization but won't respond and others it goes to zero and is equally comatose. I'll get the OS64 error 30 times in a second and then not for again for a couple minutes, sometimes ever 10 or 15 minutes. Then it's back again. The server does about 500,000 pages a day and the number of errors is typically proportional to pages. It appears to get worse over time requiring the service to either be restarted or the server to be rebooted at least once a day. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org