Jump to content

Cannot connect to server


blobby

Recommended Posts

Hi there,

 

 

I am very new to this kind of stuff so i appologise in advance for being a numpty!

 

There are a couple of threads similar to this one but none really solve my issue.

 

I installed WAMP5 and all was well untill i uploaded my site to my host using dreamweavers built in ftp client.

 

After that I could not view any pages on localhost, it tried to open a page for ages (using all of the cpu usage) but just returned nothing (including phpadmin).

 

I re installed WAMP5 and all was well again.

 

However, i have just uploaded my site again using my hosts ftp client,  and the same thing has happened!!

 

I have tried to view my error log but it's too large to open!! it's 801,814kb.

 

Sometimes i get the usual 'page cannot be displayed' message.  Mostly tho the page just stays blank (white) untill it times out or i get fed up of waiting!

 

I have moved the original error file and it put a new one there all by itself.  It has the following errors logged:-

 

[sun Jan 28 18:59:02 2007] [notice] ModSecurity for Apache 2.0.4 configured

[sun Jan 28 18:59:05 2007] [notice] Apache/2.2.3 (Win32) mod_ssl/2.2.3 OpenSSL/0.9.8d PHP/5.2.0 mod_perl/2.0.3-dev Perl/v5.8.8 configured -- resuming normal operations

[sun Jan 28 18:59:05 2007] [notice] Server built: Nov 15 2006 21:34:51

[sun Jan 28 18:59:05 2007] [notice] Parent: Created child process 3092

[sun Jan 28 18:59:08 2007] [notice] ModSecurity for Apache 2.0.4 configured

[sun Jan 28 18:59:10 2007] [notice] Child 3092: Child process is running

[sun Jan 28 18:59:10 2007] [notice] Child 3092: Acquired the start mutex.

[sun Jan 28 18:59:10 2007] [notice] Child 3092: Starting 250 worker threads.

[sun Jan 28 18:59:10 2007] [notice] Child 3092: Starting thread to listen on port 443.

[sun Jan 28 18:59:10 2007] [notice] Child 3092: Starting thread to listen on port 80.

[sun Jan 28 18:59:10 2007] [error] (OS 10038)An operation was attempted on something that is not a socket.  : Child 3092: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive.

 

 

that is at the start of the log, but then this line appears thousands of times :-

 

[sun Jan 28 18:59:10 2007] [error] (OS 10038)An operation was attempted on something that is not a socket.  : Child 3092: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive.

 

Then this lot:-

 

[sun Jan 28 18:59:29 2007] [notice] Parent: child process exited with status 1 -- Restarting.

[sun Jan 28 18:59:32 2007] [notice] Apache/2.2.3 (Win32) mod_ssl/2.2.3 OpenSSL/0.9.8d PHP/5.2.0 mod_perl/2.0.3-dev Perl/v5.8.8 configured -- resuming normal operations

[sun Jan 28 18:59:32 2007] [notice] Server built: Nov 15 2006 21:34:51

[sun Jan 28 18:59:32 2007] [notice] Parent: Created child process 1704

[sun Jan 28 18:59:34 2007] [notice] ModSecurity for Apache 2.0.4 configured

[sun Jan 28 18:59:36 2007] [notice] Child 1704: Child process is running

[sun Jan 28 18:59:36 2007] [crit] (OS 109)The pipe has been ended.  : setup_inherited_listeners: Unable to read socket data from parent

[Mon Jan 29 17:32:50 2007] [notice] ModSecurity for Apache 2.0.4 configured

[Mon Jan 29 17:32:53 2007] [notice] Apache/2.2.3 (Win32) mod_ssl/2.2.3 OpenSSL/0.9.8d PHP/5.2.0 mod_perl/2.0.3-dev Perl/v5.8.8 configured -- resuming normal operations

[Mon Jan 29 17:32:53 2007] [notice] Server built: Nov 15 2006 21:34:51

[Mon Jan 29 17:32:53 2007] [notice] Parent: Created child process 2192

[Mon Jan 29 17:32:56 2007] [notice] ModSecurity for Apache 2.0.4 configured

[Mon Jan 29 17:32:59 2007] [notice] Child 2192: Child process is running

[Mon Jan 29 17:32:59 2007] [notice] Child 2192: Acquired the start mutex.

[Mon Jan 29 17:32:59 2007] [notice] Child 2192: Starting 250 worker threads.

[Mon Jan 29 17:32:59 2007] [notice] Child 2192: Starting thread to listen on port 443.

[Mon Jan 29 17:32:59 2007] [notice] Child 2192: Starting thread to listen on port 80.

 

then this line thousands on times:-

 

[Mon Jan 29 17:32:59 2007] [error] (OS 10038)An operation was attempted on something that is not a socket.  : Child 2192: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive.

 

the 2 lines that have been repeated lots of times make up alomost all of the the 801,814kb file.

 

  I think that the new log is being continously written to.

 

hope this helps a bit.

 

 

Can anyone help me please?

 

Thanks in advance

Link to comment
Share on other sites

Look at the first result I got from google:

http://www.google.ie/search?hl=en&q=apache+Encountered+too+many+errors+accepting+client+connections.&meta=

 

It suggests something about xp and lookback and firewall etc.

 

Also - the second result from the above search ( http://www.issociate.de/board/post/257555/New_Apache_2.0_54_install_on_Windows_2K3_Server.html ) shows a way of how to fix your problem via a edit of httpd.conf

 

Its all about your search string. You need to pick out a common search thread. I used:

apache Encountered too many errors accepting client connections

in google.

 

-steve

 

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.