Alex: Apache 2: caught SIGTERM, shutting down

Beitrag lesen

Hallo,

ich nutze Apache 2 unter Debian Linux mit folgender Konfig:
Apache/2.0.54 (Debian GNU/Linux) FrontPage/5.0.2.2635 mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e mod_perl/1.999.21 Perl/v5.8.4

In unbestimmten Zeitabständen finde ich diese Fehlermeldung und einen Apache Restart im Log:

[Sat Sep 30 22:14:29 2006] [notice] Apache/2.0.54 (Debian GNU/Linux) FrontPage/5.0.2.2635 mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e mod_perl/1.999.21 Perl/v5.8.4 configured -- resuming normal operations
[Sat Sep 30 23:02:18 2006] [error] server reached MaxClients setting, consider raising the MaxClients setting
[Sun Oct 01 10:45:56 2006] [notice] caught SIGTERM, shutting down
[Sun Oct 01 10:45:58 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Sun Oct 01 10:45:58 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec2)
[Sun Oct 01 10:45:58 2006] [notice] mod_python: Creating 10 session mutexes based on 10 max processes and 0 max threads.
[Sun Oct 01 10:45:59 2006] [notice] Apache/2.0.54 (Debian GNU/Linux) FrontPage/5.0.2.2635 mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e mod_perl/1.999.21 Perl/v5.8.4 configured -- resuming normal operations
[Sun Oct 01 10:46:13 2006] [error] server reached MaxClients setting, consider raising the MaxClients setting

An was kann dies denn liegen? Der Apache startet sich einfach neu.