Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Apache2 stopped working once in 24 hours |
|
| Author |
|
zohaib09
Joined: 08 Oct 2022
Posts: 1
Location: Pakistan, Hyderabad
|
 Posted: Sat 08 Oct '22 19:24 Post subject: Apache2 stopped working once in 24 hours |
 |
|
Hi
We are using apache2 Apache/2.4.54 (Debian) on debian 11 with php8.0, php-fpm is not installed. It has been working fine since long. Now apache2 stops working once in 24 hours
Syslog:
apache2.service: Killing process 383505 (/usr/sbin/apach) with signal SIGKILL.
apache error logs:
[Sat Oct 08 09:06:13.220482 2022] [mpm_prefork:notice] [pid 293859] AH00171: Graceful restart requested, doing restart
AH00557: apache2: apr_sockaddr_info_get() failed for servername
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1. Set the ‘ServerName’ directive globally to suppress this mess>
[Sat Oct 08 09:06:13.276095 2022] [http2:warn] [pid 293859] AH10034: The mpm module (prefork.c) is not supported by mod_http2. The mpm determines how things are proces>
Sat Oct 8 09:06:13 2022 (293859): Fatal Error Unable to create lock file: Bad file descriptor (9)
[Sat Oct 08 09:06:17.717821 2022] [http2:warn] [pid 386911] AH10034: The mpm module (prefork.c) is not supported by mod_http2. The mpm determines how things are proces>
[Sat Oct 08 09:06:17.741732 2022] [core:warn] [pid 386911] AH00098: pid file /var/run/apache2/apache2.pid overwritten – Unclean shutdown of previous Apache run?
[Sat Oct 08 09:06:17.746772 2022] [mpm_prefork:notice] [pid 386911] AH00163: Apache/2.4.54 (Debian) SVN/1.14.1 OpenSSL/1.1.1n mod_perl/2.0.11 Perl/v5.32.1 configured →
[Sat Oct 08 09:06:17.746806 2022] [core:notice] [pid 386911] AH00094: Command line: ‘/usr/sbin/apache2’
[Sat Oct 08 09:06:17.911089 2022] [mpm_prefork:notice] [pid 386911] AH00169: caught SIGTERM, shutting down
mpm_prefork.conf
<IfModule mpm_prefork_module>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxRequestWorkers 150
MaxConnectionsPerChild 500
</IfModule>
Please advice.
Thanks! |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7294
Location: Germany, Next to Hamburg
|
| Posted: Thu 13 Oct '22 8:53 Post subject: |
|
|
For the warning, you have to set a server name
e.g.
| Code: |
ServerName example.com
|
HTTP/2 is supported in all multi-processing modules that come with httpd. However, there will be severe restrictions if you use the prefork mpm.
In prefork, mod_http2 will only process one request at a time per connection. But clients, such as browsers, will send many requests simultaneously. If one of these takes long to process (or is a long polling one), the other requests will stall.
mod_http2 will not work around this limit by default. The reason is that prefork is today only chosen, if you run processing engines that are not prepared for multi-threading, e.g. will crash with more than one request.
If your setup can handle it, configuring event mpm is nowadays the best one (if supported on your platform).
If you are really stuck with prefork and want multiple requests, you can tweak the H2MinWorkers to make that possible. If it breaks, however, you own both parts. |
|
| Back to top |
|
|
|
|
|
|
