Webdigity Webmaster Forums - Please help me keep this server alive

Nikolas

Sat 11 February 2006, 12:18 pm GMT +0200

I have a very strange problem.

The server crashes by Apache(as you've allready noticed).
Even ssh is unreachable when those crashes are done.

Here is the configuration :

Debian stable
Apache/2.0.55
mod_ssl/2.0.55
OpenSSL/0.9.7g
PHP/4.4.1

The error log has these lines :

Quote

[Fri Feb 10 23:16:37 2006] [error] server reached MaxClients setting, consider raising the MaxClients setting
[Sat Feb 11 00:29:52 2006] [notice] child pid 9957 exit signal Segmentation fault (11)
[Sat Feb 11 00:38:23 2006] [notice] child pid 9372 exit signal Segmentation fault (11)
[Sat Feb 11 00:40:38 2006] [notice] child pid 10198 exit signal Bus error (7)
[Sat Feb 11 02:28:08 2006] [notice] child pid 10170 exit signal Segmentation fault (11)
[Sat Feb 11 03:18:37 2006] [notice] child pid 10225 exit signal Segmentation fault (11)
[Sat Feb 11 07:26:33 2006] [notice] child pid 10390 exit signal Segmentation fault (11)
[Sat Feb 11 11:31:43 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Sat Feb 11 11:31:44 2006] [warn] pid file /usr/local/apache2/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Sat Feb 11 11:31:44 2006] [notice] Apache/2.0.55 (Unix) mod_ssl/2.0.55 OpenSSL/0.9.7g PHP/4.4.1 configured -- resuming normal operations

I understand the two lines in the end(are after I started again the server), but what about the segmentation fault?

Does anyone knows what can cause this?

The only resource I found is that php 4.x crashes the apache (2.x) when is used in ErrorDocument (.htaccess)(using php error pages) For this I am upgrading the sites to php 5, but I believe that this is not the reason for the problem.

Thanks in advance :)

wineo

Sat 11 February 2006, 05:59 pm GMT +0200

What have you got the MaxClients set at?

Nikolas

Sun 12 February 2006, 03:05 am GMT +0200

MaxClients is set to 150

Meth0d

Sun 12 February 2006, 06:53 am GMT +0200

you should have max clients set to 0, and alsu use htacess files to handle error documents, instead of editing the config file

Nikolas

Sun 12 February 2006, 01:07 pm GMT +0200

Having maxClients to 0 will crash the server for sure, because if this machine will not be able to handle those requests. I will try to raise it to 200 or something.

The error documents are handled by htaccess.

Meth0d

Mon 13 February 2006, 01:13 am GMT +0200

ok you put 0 and it doesnt set it to unlimited? i cant even remeber of the top of my head, but you should have a way to use unlimited users (if the machine can handle it) if machine can only handle 200 at a time that is not that many

wineo

Mon 13 February 2006, 04:28 am GMT +0200

Hey Nick, what are the specs of the server? Have you got enough ram for apache to handle more than 150?

Nikolas

Mon 13 February 2006, 09:41 am GMT +0200

Quote from: wineo on Feb 13, 2006, 04:28:21 AM

Hey Nick, what are the specs of the server? Have you got enough ram for apache to handle more than 150?

No I don't think that it can handle more than 150 as it is an amd64 3Ghz with 1gb ram and it is used for all the services (dns, qmail, apache, mysql)

I found some bugs related to eaccelerator, and change them. Hope it will help

wineo

Mon 13 February 2006, 10:25 am GMT +0200

Keep us posted!

Nikolas

Mon 13 February 2006, 10:36 am GMT +0200

I just read the eaccelerator

forums, and it seems that eaccelerator produces some fault signals.

So I turned some sites to php5 (with eaccelerator not enabled), and for the rest I turned the eaccelerator caching on. By the way with the caching on, the server seems to load much faster.

soulwatcher

Tue 14 February 2006, 08:39 am GMT +0200

Well I dont have a answer to your problem. But you could try www.webhostingtalk.com

and post in their teck forum. People seem to know alot in that forum. They should be able to help.

Nikolas

Tue 14 February 2006, 09:15 am GMT +0200

Quote from: soulwatcher on Feb 14, 2006, 08:39:30 AM

Well I dont have a answer to your problem. But you could try www.webhostingtalk.com

and post in their teck forum. People seem to know alot in that forum. They should be able to help.

I will try them too. But it seems that the problem solved (at least I hope)

Thanks for the info