By Jason Dean on

Hi

I'm hosting my Drupal site on a VPS with Cpanel. It's a new site and traffic is low, but I experience "the connection with the server was reset" messages when navigating around the site. When I click refresh, the page loads fine. This can happen when I'm the only user logged into the site.

Sometimes I can work on the site for a day and not get it, sometimes 6 times in a session. A user has reported it too.

I run a small Wordpress site on the same VPS and never had a problem. The hosting provider had me check DNS settings, but everything seems to point to an Apache problem.

The host has now suggested opening up httpd.conf in /usr/local/apache/conf/httpd.conf and increasing the maximum number of active connections from 500 to 1000.

Would Drupal really be running out of http requests with only 1 user logged in?

My site is http://www.womensmarketingforum.com

Thanks!

⋅ Categories: Drupal 5.x

Comments

Jason Dean’s picture

Jason Dean commented

After a bit of research, I've made a few tweaks in httpd.conf:

MaxClients 25 (was 150)
MaxRequestsPerChild 5000 (was 100)

I'll see if this makes a difference. Still a bit alarmed that I'm tweaking server settings before the site's really being used by anyone. Hope I'm barking up the right tree!

switch13’s picture

switch13 commented

I have many instances of MaxClients and MaxRequestsPerChild in my httpd.conf file. Do you remember if you changed all of them?

dpatte’s picture

dpatte commented

I'm also seeing this, though none of my users have reported it yet. Im using the latest version of drupal and started noticing it about the same time as I upgraded.

I have similiar symptoms.

I'll check my settings and see what I find.

Cubic8’s picture

Cubic8 commented

I was getting this too; this was on my local development version of Drupal which is Apache 2.2.13 on Windows7. Certain pages (normally under Admin menu) would start to come up with 'connection reset' (I use FireFox). Then I would have to restart Apache, and clear the Drupal cache to get things working again.

After a lot of frustration, I noticed that some of my paths in httpd.conf had backslashes ('\'). The comments at the top of httpd.conf explicitly say these must be forward slashes ('/'). So I corrected the slashes, and now after several days running I haven't had any further problems!

noah’s picture

noah commented

In case it's of any use to anyone: I was able to make this problem go away (on a D5 site on Apache on Windows) by disabling "Aggregate and compress CSS files".