["Resuelto"]Configurar apache2.conf y my.conf para muchas conex

[Piradoxlanieve]

holas decidi cambiar mi servidor dedicado un celeron 1.2ghz con 1gb de ram de ovh por un un quad core 6600 de 4gb de ram en prevision de montar algo serio pero tengo un problema... las web en el celeron se mostraban rapido pero en el quad core... se agota el tiempo de espera aveces tardan mas en cargar y nose que puede ser el ekipo lo supera pero va peor creadno mas procesos del apache? eso lo solia hacer en xammp pero aqui nose si funciona, saludos y gracias.

[Piradoxlanieve]

:rolleyes:he modificado el apache2.conf y el my.conf con unos valores superiores a los que bien por defecto y nada no hay manera me he dado cuenta que solo se me cae una web de 3 Service Unavailable! error 503 el equipo para nada esta sobre cargado un load average de 0.23-0.40 las demas web van pero el tracker nada de nada tarda mucho en cargar no carga puede ser algo del php.ini??? del dominio??? ayudarme plis cuando vaya a casa pego el log del apache.

[Piradoxlanieve]

[Mon Sep 28 18:29:14 2009] [error] [client 190.231.224.143] request failed: error reading the headers
[Mon Sep 28 18:31:04 2009] [error] [client 89.130.144.33] request failed: error reading the headers
[Mon Sep 28 18:31:27 2009] [error] [client 64.120.9.170] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind
[Mon Sep 28 18:32:07 2009] [error] [client 83.42.212.176] request failed: error reading the headers
[Mon Sep 28 18:32:09 2009] [error] [client 85.137.90.108] request failed: error reading the headers
[Mon Sep 28 18:32:19 2009] [error] [client 90.162.14.196] request failed: error reading the headers
[Mon Sep 28 18:32:49 2009] [error] [client 93.136.145.191] request failed: error reading the headers
[Mon Sep 28 18:33:10 2009] [error] [client 79.157.226.122] request failed: error reading the headers
[Mon Sep 28 18:34:36 2009] [error] [client 190.231.224.143] request failed: error reading the headers
[Mon Sep 28 18:34:42 2009] [error] [client 83.59.189.43] request failed: error reading the headers

---

valores de apache2.conf
-----------------------------------------------------------
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers 78
MinSpareServers 100
MaxSpareServers 250
MaxClients 4992
MaxRequestsPerChild 10000
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
ServerLimit 100
StartServers 78
MaxClients 4992
MinSpareThreads 100
MaxSpareThreads 250
ThreadsPerChild 64
MaxRequestsPerChild 1000
</IfModule>
-----------------------------------
Valores my.conf
---------------------------------------------
# * Fine Tuning
#
key_buffer = 512M
max_allowed_packet = 512M
thread_stack = 128M
thread_cache_size = 128
max_connections = 10000
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 20M
query_cache_size = 64M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name

[Piradoxlanieve]

Pues bueno como tenia el mosqueo encima tenia instalado ispcp 1.0.3 y me daba tantos problemas decidi instalar 1.0.0 y parece que funciona perfecto con la config por defecto asi que sera algun fix , la verda que la 1.0.3 trae la novedad de elegir si quieres backup de cada hosting la cosa que esta bien pero si me da ese problema me quedare con la 1.0.0