• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved [mpm_prefork:notice] [pid 26344] AH00169: caught SIGTERM, shutting down

daanse

Regular Pleskian
Hi,
does anyone could give me a lead on this Problem?
This went 8 Minutes long, always shutting down until Apache startet 00:08:00 ....
Just copied the first snipped of that carusell ..

Code:
[Sat Aug 20 00:01:12.397819 2016] [auth_digest:notice] [pid 26344] AH01757: generating secret for digest authentication ...
[Sat Aug 20 00:01:12.398158 2016] [:notice] [pid 26344] mod_bw : Memory Allocated 0 bytes (each conf takes 48 bytes)
[Sat Aug 20 00:01:12.398168 2016] [:notice] [pid 26344] mod_bw : Version 0.92 - Initialized [0 Confs]
[Sat Aug 20 00:01:13.023149 2016] [ssl:warn] [pid 26344] AH01909: roundcube.webmail:443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 20 00:01:13.023721 2016] [ssl:warn] [pid 26344] AH01909: lists:443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 20 00:01:13.024755 2016] [ssl:warn] [pid 26344] AH01909: default-188_68_52_131:443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 20 00:01:13.044154 2016] [:error] [pid 26344] python_init: Python version mismatch, expected '2.7.5+', found '2.7.9'.
[Sat Aug 20 00:01:13.044254 2016] [:error] [pid 26344] python_init: Python executable found '/usr/bin/python'.
[Sat Aug 20 00:01:13.044262 2016] [:error] [pid 26344] python_init: Python path being used '/usr/lib/python2.7/:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/
lib-old:/usr/lib/python2.7/lib-dynload'.
[Sat Aug 20 00:01:13.044294 2016] [:notice] [pid 26344] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads.
[Sat Aug 20 00:01:13.044299 2016] [:notice] [pid 26344] mod_python: using mutex_directory /tmp
[Sat Aug 20 00:01:13.063284 2016] [mpm_prefork:notice] [pid 26344] AH00163: Apache/2.4.10 (Debian) OpenSSL/1.0.1t Apache mod_fcgid/2.3.9 mod_python/3.3.1 Python/2.7.9 mod_perl/2.0.9dev Perl/v5.20.2
configured -- resuming normal operations
[Sat Aug 20 00:01:13.063336 2016] [core:notice] [pid 26344] AH00094: Command line: '/usr/sbin/apache2'
[Sat Aug 20 00:01:15.382826 2016] [mpm_prefork:notice] [pid 26344] AH00169: caught SIGTERM, shutting down
[Sat Aug 20 00:01:18.025092 2016] [ssl:warn] [pid 26605] AH01909: roundcube.webmail:443:0 server certificate does NOT include an ID which matches the server name
 
Hi daanse,

depending to your apache configuration, you setup an amount of "StartServers" processes at any apache - startup, which are spawned to a defined "MaxClients" - process - amounts.
Seeing a NOTICE as "[mpm_prefork:notice] [pid 26344] AH00169: caught SIGTERM, shutting down" doesn't mean, that there is something wrong here. It is just a NOTICE, that one of your processes have been killed, mostly depending to client inactivity. Consider to change the log - level to "warn" ( possible values are: debug, info, notice, warn, error, crit, alert, emerg ) for example, if you are not able to ignore such notices by yourself.
 
Hi @UFHH01,

so this is nothing important? Cause my Apache Service went down for 8 Minutes. I got Warnings from Monitoring.
All started with this log.
 
Hi daanse,

so this is nothing important?
Well, from the provided log - entries, the answer is: NO! ( pls. re-read my above explanation, if you think, that the NOTICE might be important ).

Consider to use the "debug" - level and consider then to post the complete log - entries from "before the issue(s) start(s)" to "untill the issue(s) end(s)" if you would like help with further investigations.
In addition, it could be a good idea to post the corresponding log - entries from you PHP - log ( same time - period, pls. )
 
Back
Top