[Page 1, 2 Next]

Topic: Apache 2.4 randomly stop responding [Solved]

[1]

Topic: Apache 2.4 randomly stop responding [Solved]

[bagu]

Hello,

I use apache 2.4.1 and mod_fcgid (same config form apache 2.2.22+mod_fcgid 2.3.6) and without any error message, apache stop responding randomly.

There is no problem with apache 2.2.22+mod_fcgid 2.3.6 and with apache 2.4.1 + php5_module i have

[admin]

Runs fine here, not seen a single crash.

Asume that you are not running SSL ?

Other errors/warnings in the logs ?
Some in the Windows Event Viewer?

Do you use the default settings ?

<IfModule mpm_winnt_module>
ThreadsPerChild 150
MaxConnectionsPerChild 0
</IfModule>

Win32 or Win64, XP or Win7 ?

Steffen

Btw.
Download mod_fcgid 2.3.6 is still there.

[admin]

Just get some notes from James about craches with PHP/Modules.


Try, maybe it helps for fcgid and/or PHP handler:

<IfModule mpm_winnt_module>
ThreadStackSize 8242880
</IfModule>

Currently the stack size is 256k, multiply that by the 64 threads in Windows and you have 19 megs, which is right about what you see in the process list when you first start up 2.2. That's not all in use, but reserved.

From the docu:

"On platforms with a relatively small default thread stack size (e.g., HP-UX), Apache httpd may crash when using some third-party modules which use a relatively large amount of auto data storage. Those same modules may have worked fine on other platforms where the default thread stack size is larger. This type of crash is resolved by setting ThreadStackSize to a value higher than the operating system default. This type of adjustment is necessary only if the provider of the third-party module specifies that it is required, or if diagnosis of an Apache httpd crash indicates that the thread stack size was too small."


Steffen

[bagu]

I'm under win XP 32bit as i said
I only use built-in modules because antiloris don't work for the moment.
I don't use SSL.

There is no error in error log neither in windows event log. Apache just stop responding.

I use MPM so i will try to test "ThreadStackSize 8242880"

Thanks for your patience

[bagu]

After many tests, the problem is still here.

But...

The difference is that apache is still alive because after 1-3 minutes of not responding at all, it re-work.

Here are my conf :
Httpd.conf : http://pastebin.com/Zu1MBMeL
Fcgid.conf : http://pastebin.com/saADTvKT
PHP.ini : http://pastebin.com/KkQasKSd

I can't locate the problem because there is no error (note : even if i change "LogLevel notice fcgid_module:error" to "LogLevel notice"...i put "LogLevel notice fcgid_module:error" to avoid the gracefull kill spamming my logs - 1 to 6 line/day)

EDIT : even if you see WAMP, i don't use wampserver, it's just a habit of naming that I took.

[glsmith]

Hmmmm, I wonder if this isn't part of my problem with APR 1.4.6 on XP SP3. 2.4.1 built on APR 1.4.6 on my XP box runs dog slow. Half of the requests outright fail.

For instance, I have a page with 600 thumbnails on it, only about 50 will show up, and eventually the browser will timeout. Even a simple static page with a couple of images really lags before it finally shows up.

This I do not notice on the Vista laptop I built on, or the 2008 R2 box I build the 64 bit build on. Apache 2.4.1 built on APR 1.4.5 does not have a problem on my XP SP3 server.

If you care to give it a try, the Apache Haus builds were purposely built with APR 1.4.5 because of my experience. See if everything works fine then. If so, we have a pretty good idea that APR 1.4.6 is a problem on XP, which would mean most likely Server 2003 as well. If not, you have a real head scratcher there.

[DigitalDJ]

Don't suppose there's an update on this?

I'm also getting this with Apache 2.4.1 and either fcgid 2.3.6 and 2.3.7

Apache 2.2.22 worked perfectly fine.

After about an hour of requests to the server, just about everything becomes unresponsive. Both httpd.exe processes are still alive, in fact, I have a separate VirtualHost that uses mod_proxy...and that still works when other things are timing out.

Can't seem to find anything in the logs

[admin]

Can you guys try with APR 1.4.5 ?

Download Removed

To be sure, you do not see issues with 2.2.22 with apr 1.4.6 ?


Steffen

[DigitalDJ]

I'll try APR 1.4.5 and report back in a hours (when it breaks again) :p

I'm not sure when APR was updated to 1.4.6, I updated to the Apache 2.2.22 build on ApacheLounge when it was first published.

I'll also note that my configuration is mostly all 2.4 defaults, except for a couple of added VirtualHosts and mod_fcgid:

[bagu]

There is no issue with 2.2.22 with apr 1.4.6

For the moment, no issues with 2.4.1 with apr 1.4.5
I will continue stress tests.

[DigitalDJ]

Still occurs on APR 1.4.5, Apache 2.4.1. At least for my server

[bagu]

It just crash here too

[DigitalDJ]

I've switched back to mod_php for now, see if that solves it.

[bagu]

OK, with apr 1.4.5 apache stop responding after +/- 1 hour. But, when problem appear, it waork again after 5 minutes, so it crash again in a loop.

[admin]

Recap:

All fine with 2.2.22 with APR 1.4.5 and 1.4.6

2.4.1 on XP crashes with APR 1.4.5 and APR 1.4.6, most likely also Win2003. On Vista, Win7 and Win2008 no issues reported.


Steffen

[DigitalDJ]

My setup is with Win2008 R2, so not just XP having the issue. I have a strong feeling the issue is fcgid.

[admin]

With mod_fcid 2.3.7 and 2.3.6 ?

Bagu has the crashes also with the PHP module.

Steffen

@DigitalDJ: get a unknown user at @dod.. when a reply is posted.

[DigitalDJ]

I tried both fcgid 2.3.7 and 2.3.6 and a combination of APR 1.4.5/1.4.6, both produce hangs. I'm using mod_php at the moment and things still seem OK, but it's only been an hour or so.

[DigitalDJ]

Actually I have noticed a couple of errors in my error.log, although I have no idea if they're related. It doesn't seem to because I think the error shows even when the server is still responsive.

[bagu]

The error