Bug 1669213

Summary:	`ExtendedStatus Off` directive when using mod_systemd causes systemctl to hang
Product:	Red Hat Software Collections	Reporter:	David Mulford <dmulford>
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	Maryna Nalbandian <mnalband>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	httpd24	CC:	bnater, jorton
Target Milestone:	---
Target Release:	3.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1669221 (view as bug list)		Environment:
Last Closed:	2019-12-10 07:57:26 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 David Mulford 2019-01-24 15:55:05 UTC

Having "ExtendedStatus off" causes mod_systemd to not send a READY=1 from the systemd_monitor() function upon a reload via `systemctl reload httpd24-httpd`. This was tested with httpd24-httpd-2.4.34-7.el7.x86_64.

Upstream Apache BZ is https://bz.apache.org/bugzilla/show_bug.cgi?id=62697

Steps to Reproduce:

1. Set "ExtendedStatus off" in httpd's configuration.
2. Start httpd24 with `systemctl start httpd24-httpd`
3. Attempt to reload with `systemctl reload httpd24-httpd`

Actual results:

httpd24 reloads successfully, but systemd doesn't see this and fails with the following error when viewing `systemctl status httpd24-httpd` or `journalctl -u httpd24-httpd`.

systemd[1]: httpd24-httpd.service reload operation timed out. Stopping.

This message is repeated indefinitely and the systemctl reload command never completes.

Expected results:

The systemctl reload should complete, and httpd reports its READY=1 status like it does when ExtendedStatus is on.

Comment 11 errata-xmlrpc 2019-12-10 07:57:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:4126