| Author |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
 Posted: Fri 12 Nov '10 11:26 Post subject: Asynchronous AcceptEx failed only sometimes |
 |
|
I'm using apache 2.3.8 32 bit on XP Pro with fcgid 2.3.5b PHP 5.3.3
Once in a month or less I get
| Code: |
[Fri Nov 12 08:28:29.539949 2010] [warn] [pid 780:tid 2480] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
|
but that 5 times a second and than it disappears until 5 or 6 weeks.
Using Win32DisableAcceptEx is not an option cause uit doesn't exist in 2.3
Any idea why the network name disappears? |
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Sat 13 Nov '10 8:58 Post subject: |
|
|
I have this ... few times a days ... server still answers.
I'd suspect for the same reason it does it on 2.2, but no, no Win32DisableAcceptEx so I just suffer with it.
Since there is nothing I can do about it ... been thinking about just disabling the error ... one less piece of log pollution. |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
| Posted: Sat 13 Nov '10 16:17 Post subject: |
|
|
| if I have to guess than they fixed something so there is no more need for Disable AccepEx. Well mod_fcgid creates more log pollution.... |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
| Posted: Tue 30 Nov '10 19:03 Post subject: |
|
|
I stil wonder about the OS 64 error. For testing I unplugged the networkwire and tada: No error 
I'll set the LogLevel to debug. Maybe there are more information :-/ |
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Wed 01 Dec '10 5:44 Post subject: |
|
|
That's nice, no error, but no requests from the outside.
As far as fcgid polluting, yes this new one does that for sure.
Funny thing is they have not upgraded the module to the new logging API ... but it's obvious anyway when it states fcgid in the log.
[:warn] [pid 5208:tid 524] mod_fcgid: process 2280 graceful kill fail, sending SIGKILL
^ should say fcgid before the : |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
| Posted: Thu 02 Dec '10 12:31 Post subject: |
|
|
Yesterday I had the OS64 error again while stitting on the screen of the server and using the browser os the connection couldn't fail more than a second else I would have noticed it. I gonna ignore that error message in the log. It's kinda "spam" or so.
Setting the LogLevel to debug produced only a huge log file, but no further information. That's true debugging... Also nothing in the windows event log at that time. |
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Thu 02 Dec '10 13:48 Post subject: |
|
|
Here's a new one for you,
[Mon Nov 29 13:07:17.009750 2010] [warn] [pid 3784:tid 1048] (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed. |
|
| Back to top |
|
