День добрый .
У меня стоит апач на ред хат 4 . Он работает в связке с Php и СУБД Informix . Так вот
какое то время он работает нормально , а потом начинаются проблемы с соединением с базой данных . Спасает перезапуск апача !

При прорсмотре листинга процесов можно увидеть что работают только несколько потоков , а остальные просто висят в памяти ! Из за чего это может быть ?

Вот листинг


автор[root@PcWeb acquaring]# ps -ef | grep httpd
root 26312 1 0 02:00 ? 00:00:00 /usr/local/apache/bin/httpd
nobody 26315 26312 0 02:00 ? 00:00:17 /usr/local/apache/bin/httpd
nobody 26316 26312 0 02:00 ? 00:00:08 /usr/local/apache/bin/httpd
nobody 26317 26312 0 02:00 ? 00:00:11 /usr/local/apache/bin/httpd
nobody 26318 26312 0 02:00 ? 00:00:09 /usr/local/apache/bin/httpd
nobody 26319 26312 0 02:00 ? 00:00:30 /usr/local/apache/bin/httpd
nobody 26320 26312 0 02:00 ? 00:00:08 /usr/local/apache/bin/httpd
nobody 26321 26312 0 02:00 ? 00:00:08 /usr/local/apache/bin/httpd
nobody 26322 26312 0 02:00 ? 00:00:10 /usr/local/apache/bin/httpd
nobody 26323 26312 0 02:00 ? 00:00:14 /usr/local/apache/bin/httpd
nobody 26324 26312 0 02:00 ? 00:00:13 /usr/local/apache/bin/httpd
nobody 26325 26312 0 02:00 ? 00:00:09 /usr/local/apache/bin/httpd
nobody 26326 26312 0 02:00 ? 00:00:07 /usr/local/apache/bin/httpd
nobody 26327 26312 0 02:00 ? 00:00:13 /usr/local/apache/bin/httpd
nobody 26328 26312 0 02:00 ? 00:00:10 /usr/local/apache/bin/httpd
nobody 26329 26312 0 02:00 ? 00:00:18 /usr/local/apache/bin/httpd
nobody 26330 26312 0 02:00 ? 00:00:07 /usr/local/apache/bin/httpd
nobody 26331 26312 0 02:00 ? 00:00:07 /usr/local/apache/bin/httpd
nobody 26332 26312 0 02:00 ? 00:00:09 /usr/local/apache/bin/httpd
nobody 26333 26312 0 02:00 ? 00:00:13 /usr/local/apache/bin/httpd
nobody 26334 26312 0 02:00 ? 00:00:09 /usr/local/apache/bin/httpd
nobody 26340 26312 0 02:00 ? 00:00:13 /usr/local/apache/bin/httpd
nobody 26341 26312 0 02:00 ? 00:00:07 /usr/local/apache/bin/httpd
nobody 26342 26312 0 02:00 ? 00:00:10 /usr/local/apache/bin/httpd
nobody 26343 26312 0 02:00 ? 00:00:21 /usr/local/apache/bin/httpd
nobody 26344 26312 0 02:00 ? 00:00:09 /usr/local/apache/bin/httpd
nobody 26345 26312 0 02:00 ? 00:00:16 /usr/local/apache/bin/httpd
nobody 26346 26312 0 02:00 ? 00:00:11 /usr/local/apache/bin/httpd
nobody 26347 26312 0 02:00 ? 00:00:13 /usr/local/apache/bin/httpd
nobody 26348 26312 0 02:00 ? 00:00:07 /usr/local/apache/bin/httpd
nobody 26349 26312 0 02:00 ? 00:00:07 /usr/local/apache/bin/httpd
nobody 26350 26312 0 02:00 ? 00:00:09 /usr/local/apache/bin/httpd
nobody 26351 26312 0 02:00 ? 00:00:20 /usr/local/apache/bin/httpd
nobody 26352 26312 0 02:00 ? 00:00:08 /usr/local/apache/bin/httpd
nobody 7943 26312 0 12:14 ? 00:00:01 /usr/local/apache/bin/httpd
nobody 7986 26312 0 12:16 ? 00:00:00 /usr/local/apache/bin/httpd
root 9500 5548 0 13:07 pts/2 00:00:00 grep httpd


Вот конфиг апача

[quot автор]
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
#
ServerRoot "/usr/local/apache"

#
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename.
#
#LockFile /usr/local/apache/logs/httpd.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile /usr/local/apache/logs/httpd.pid

#
# ScoreBoardFile: File used to store internal server process information.
ScoreBoardFile /usr/local/apache/logs/httpd.scoreboard

#
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order. The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults. You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive on

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 60

#
# Server-pool size regulation. Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
:
[MinSpareServers 32
MaxSpareServers 10

#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 20

#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 256

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
#
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
#
MaxRequestsPerChild 10000

#Count Threads
ThreadsPerChild 256
#
SendBufferSize 32768

ListenBacklog 1023

Ну и дальше все стандартно !
/quot]

может кто тоже сталкивался с такой проблемой ?

ALex_hha автор/usr/local/apache/bin/httpd
зачем ставили из исходников???

А как еще в таком случае сделать связку apache\php\informix ?

Ну в любом случае не все ли равно !! Из сырцов или с рпм -а я его ставил !!!
Проблема не в том как установить , а как исправить проблему !!!

То есть вы предлогаете собрать свой рпм . И переинсталить сервер ?

авторЯ вам предлагаю - удалить все, что ставили из исходников. Скачать с сайта RedHat src.rpm необходимых пакетов, в вашем случаю я думаю это только php, и пересобрать его с необходимыми опциями (--with-informix=/usr/.......).

Что самое интересное то я так и делал ! Сначала ставил из src.rpm апач после чего пхп конфигурил такой строкой


после того как поставил пхп снова переконфигурил апач





Kachalov ограничьте количество соединений с БД в php.ini

А не посдкажите какой именно параметр там править ?