Bug 2112317

Summary: systemd[1]: php-fpm.service: start operation timed out. Terminating.
Product: Red Hat Enterprise Linux 8 Reporter: redbug888 <bigpanther>
Component: php-7.4-moduleAssignee: Remi Collet <rcollet>
Status: CLOSED MIGRATED QA Contact: rhel-cs-infra-services-qe <rhel-cs-infra-services-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.5Keywords: MigratedToJIRA
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 20:25:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description redbug888 2022-07-29 10:23:52 UTC
Description of problem:

/var/log/messages:Jul 28 13:08:38 systemd[1]: php-fpm.service: start operation timed out. Terminating.
/var/log/messages:Jul 28 13:08:39 systemd[1]: php-fpm.service: Failed with result 'timeout'.

Version-Release number of selected component (if applicable):

PHP Version => 7.4.26
    with Zend OPcache v7.4.26, Copyright (c), by Zend Technologies
PHP Version => 7.4.26

How reproducible:

every time, when vm is booting, php-fpm will fail to start

(may be the high system load is one reason for)


Steps to Reproduce:
1. reboot system
2. php-fpm will fail to start (timeout) - no restart try will be done.
    apache stays unavailable - users are affected
3. restart php-fpm manually is always successful

Actual results:

restart php-fpm manually is always successful

Expected results:

The php-fpm timeout value (if exists) should overlive a system (re)start

Additional info:

Comment 1 RHEL Program Management 2023-09-21 20:16:27 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 20:25:08 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.