Forwarded to devs Update impacting on httpd

[Dave W]

TITLE:

Update impacting on httpd​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk Onyx 17.8.11 Update #56 CentOS 7​

PROBLEM DESCRIPTION:

Experienced this on 3 different servers so far tonight, same symptoms on all 3.

httpd becomes unresponsive and starts to throw the following errors:

[Tue Jun 18 02:01:21.354153 2019] [core:error] [pid 17983:tid 139683322255488] AH00546: no record of generation 0 of exiting child 22450
[Tue Jun 18 02:01:21.354176 2019] [core:notice] [pid 17983:tid 139683322255488] AH00052: child pid 22451 exit signal Segmentation fault (11)
[Tue Jun 18 02:01:21.354187 2019] [core:error] [pid 17983:tid 139683322255488] AH00546: no record of generation 0 of exiting child 22451
[Tue Jun 18 02:01:21.354201 2019] [core:notice] [pid 17983:tid 139683322255488] AH00052: child pid 22453 exit signal Segmentation fault (11)
[Tue Jun 18 02:01:21.354211 2019] [core:error] [pid 17983:tid 139683322255488] AH00546: no record of generation 0 of exiting child 22453
[Tue Jun 18 02:01:21.354223 2019] [core:notice] [pid 17983:tid 139683322255488] AH00052: child pid 22454 exit signal Segmentation fault (11)
[Tue Jun 18 02:01:21.354233 2019] [core:error] [pid 17983:tid 139683322255488] AH00546: no record of generation 0 of exiting child 22454​

STEPS TO REPRODUCE:

Seems to be related to an update according to/var/log/plesk/install/plesk_17.8.11_installation.log. these logs are similar on all 3 servers.

e.g.

[root@server ~]# grep 'Jun 18' /var/log/plesk/install/plesk_17.8.11_installation.log
START plesk-dovecot-2.3.4.1 upgrading AT Tue Jun 18 01:14:34 BST 2019
STOP plesk-dovecot-2.3.4.1 upgrading AT Tue Jun 18 01:14:35 BST 2019
START plesk-dovecot-2.3.4.1 upgrading AT Tue Jun 18 01:14:35 BST 2019
STOP plesk-dovecot-2.3.4.1 upgrading AT Tue Jun 18 01:14:35 BST 2019
START psa-horde-5.2.17 upgrading AT Tue Jun 18 01:14:35 BST 2019
STOP psa-horde-5.2.17 upgrading AT Tue Jun 18 01:14:37 BST 2019
START psa-horde-5.2.17 upgrading AT Tue Jun 18 01:14:52 BST 2019
STOP psa-horde-5.2.17 upgrading AT Tue Jun 18 01:14:52 BST 2019
START psa-imp-6.2.21.1 upgrading AT Tue Jun 18 01:14:53 BST 2019
STOP psa-imp-6.2.21.1 upgrading AT Tue Jun 18 01:14:53 BST 2019


Although the plesk panel does not indicate that an update has taken place:

• Product: Plesk Onyx 17.8.11 Update #56 , last updated at June 16, 2019 01:15 AM

ACTUAL RESULT:

httpd is un-responsive​

EXPECTED RESULT:

no interruption to httpd service​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[DennisAm]

Same issue here. Also seeing the AH00052 segmentation errors in httpd.

A reboot of the server fixed the issue for me (not sure if this is a permanent fix, closely monitoring now).

According to the update log on my server, the following packages were updated overnight:

- MariaDB-client 10.2.25-1.el7.centos from mariadb repo (previous version: 10.2.24-1.el7.centos from mariadb repo)
- MariaDB-common 10.2.25-1.el7.centos from mariadb repo (previous version: 10.2.24-1.el7.centos from mariadb repo)
- MariaDB-compat 10.2.25-1.el7.centos from mariadb repo (previous version: 10.2.24-1.el7.centos from mariadb repo)
- MariaDB-server 10.2.25-1.el7.centos from mariadb repo (previous version: 10.2.24-1.el7.centos from mariadb repo)
- fail2ban 1:0.9.6-centos7.19061314 from PLESK_17_8_11-extras repo (previous version: 1:0.9.6-centos7.17122713 from PLESK_17_8_11-dist repo)
- mod_cloudflare 1:1.2.0.3-centos7.19061315 from PLESK_17_8_11-extras repo (previous version: 1:1.2.0.3-centos7.18021217 from PLESK_17_8_11-dist repo)
- mod_passenger 5.3.5.1-centos7.19061318 from PLESK_17_8_11-extras repo (previous version: 5.3.5-centos7.18110217 from PLESK_17_8_11-extras repo)
- passenger 5.3.5.1-centos7.19061318 from PLESK_17_8_11-extras repo (previous version: 5.3.5-centos7.18110217 from PLESK_17_8_11-extras repo)
- passenger-devel 5.3.5.1-centos7.19061318 from PLESK_17_8_11-extras repo (previous version: 5.3.5-centos7.18110217 from PLESK_17_8_11-dist repo)
- passenger-native-libs 5.3.5.1-centos7.19061318 from PLESK_17_8_11-extras repo (previous version: 5.3.5-centos7.18110217 from PLESK_17_8_11-extras repo)
- plesk-git-http 17.8.11-cos7.build1708190613.16 from PLESK_17_8_11-extras repo (previous version: 17.8.7-cos7.build1708171004.18 from PLESK_17_8_11-extras repo)
- plesk-modsecurity-crs 17.8.11-centos7.19061315 from PLESK_17_8_11-extras repo (previous version: 17.8.11-centos7.18021217 from PLESK_17_8_11-dist repo)
- psa-mod_fcgid 2.3.9.5-centos7.19061314 from PLESK_17_8_11-extras repo (previous version: 2.3.9.5-centos7.18020211 from PLESK_17_8_11-dist repo)
- psa-mod_proxy 2.4.6-centos7.19061316 from PLESK_17_8_11-extras repo (previous version: 2.4.6-centos7.17122714 from PLESK_17_8_11-dist repo)
- psa-proftpd 1.3.6-cos7.build1708190613.14 from PLESK_17_8_11-extras repo (previous version: 1.3.6-cos7.build1708180220.17 from PLESK_17_8_11-dist repo)
- psa-selinux 17.8.11-cos7.build1708190613.14 from PLESK_17_8_11-extras repo (previous version: 17.8.11-cos7.build1708190226.15 from PLESK_17_8_11-extras repo)
- sw-msmtp 1.6.2-19061314 from PLESK_17_8_11-extras repo (previous version: 1.6.2-17100418 from PLESK_17_8_11-dist repo)
- sw-nginx 1.14.2.1-centos7.19061316 from PLESK_17_8_11-extras repo (previous version: 1.14.2-centos7.19022720 from PLESK_17_8_11-extras repo)

 

[IgorG]

Thank you!
Restart the Apache webserver is effectively solve the issue. The issue PPPM-10360 is confirmed.