Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The ocf:heartbeat:Squid resource agent is unable to start in RHEL-8, apparently due to process forking behavior changes in Squid. The are_pids_sane() function in resource agent requires that the Squid process whose PID is stored in the PID file is also the one which binds the listening TCP port, which is not true on RHEL-8 (the port is bound by a child of the main process).
Version-Release number of selected component (if applicable):
resource-agents-4.1.1-17.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. first, a small debug print patch for the RA to see the non-matching PIDs (first PID is the main process, second is the one which binds the proxy TCP port):
> [root@virt-014 ~]# diff Squid-orig /usr/lib/ocf/resource.d/heartbeat/Squid
> 218a219
> > echo "${SQUID_PIDS[1]} != ${SQUID_PIDS[2]}"
2. pcs resource create squid-proxy ocf:heartbeat:Squid squid_conf=/etc/squid/squid.conf squid_exe=/usr/sbin/squid squid_port=3128 squid_pidfile=/var/run/squid.pid op monitor interval=30s
Actual results:
> [root@virt-014 ~]# pcs resource debug-start squid-proxy
> Operation start for squid-proxy (ocf:heartbeat:Squid) returned: 'ok' (0)
> > stdout: 12454 != 12457
> > stderr: ocf-exit-reason:squid:Pid unmatch
> [root@virt-014 ~]# pcs status
> [...]
> squid-proxy (ocf::heartbeat:Squid): Stopped
>
> Failed Resource Actions:
> * squid-proxy_start_0 on virt-014 'unknown error' (1): call=29, status=Timed Out, exitreason='squid:Pid unmatch',
> last-rc-change='Thu Mar 14 18:35:34 2019', queued=0ms, exec=60005ms
> * squid-proxy_start_0 on virt-025 'unknown error' (1): call=29, status=Timed Out, exitreason='squid:Pid unmatch',
> last-rc-change='Thu Mar 14 18:36:47 2019', queued=0ms, exec=60014ms
> [root@virt-014 ~]# ps faux
> [...]
> root 12454 0.0 0.4 111680 8468 ? Ss 11:47 0:00 /usr/sbin/squid -f /etc/squid/squid.conf
> squid 12457 0.0 1.1 116836 21080 ? S 11:47 0:00 \_ (squid-1) --kid squid-1 -f /etc/squid/squid.conf
> squid 12470 0.0 0.1 24308 2024 ? S 11:47 0:00 \_ (logfile-daemon) /var/log/squid/access.log
Expected results:
resource starts
Additional info:
Comment 1Oyvind Albrigtsen
2019-03-18 15:07:27 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/RHBA-2019:3307