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:
When rebooted, sendmail service fails to startup. Starting the service manually after boot works fine.
When it fails at boot, these errors show up in logs:
sendmail.service: Can't open PID file /run/sendmail.pid (yet?) after start: Operation not permitted
sm-client.service: Failed to parse PID from file /run/sm-client.pid: Invalid argument
Version-Release number of selected component (if applicable):
sendmail-8.16.1-10.el9.x86_64
Steps to Reproduce:
1. Remove postfix
2. Install sendmail (we actually do this with "-postfix" and "sendmail" in kickstart)
3. Enable sendmail and sm-client services (systemctl --enable sendmail.service sm-client.service)
4. Reboot
Actual results:
Sendmail fails to start. Sometimes with 2 start attempts (I think NetworkManager dispatch). Always with the above errors about pid files.
Expected results:
Sendmail
Additional info:
I'm able to work around this with the following in a /etc/systemd/system/sendmail.service.d/override.conf file:
[Unit]
After=network-online.target
[Service]
Restart=on-failure
RestartSec=5s
ExecStartPost=/bin/sleep 1
(ExecStartPost to sleep a second seems to be the key item, but I included the others to make sure it's after the NetworkManager stuff and restarts on failures)
My bug report https://bugzilla.redhat.com/show_bug.cgi?id=1931693
refers only the error in FC35 it does not seem to affect the
starting of sendmail there.
It seems to be the second line in the /run/sm-client.pid file that
triggers that error.
sendmail now does fail totally on FC38 but the problem appears to be selinux context problems...
type=AVC msg=audit(28/06/23 03:12:33.355:11025) : avc: denied { create } for pid=1154445 comm=sendmail name=sendmail.pid scontext=system_u:system_r:sendmail_t:s0 tcontext=system_u:object_r:sendmail_var_run_t:s0 tclass=file permissive=0
type=AVC msg=audit(29/06/23 03:24:25.076:11481) : avc: denied { create } for pid=1386699 comm=sendmail name=sendmail.pid scontext=system_u:system_r:sendmail_t:s0 tcontext=system_u:object_r:sendmail_var_run_t:s0 tclass=file permissive=0
type=AVC msg=audit(29/06/23 07:59:15.562:11553) : avc: denied { create } for pid=1459730 comm=sendmail name=sendmail.pid scontext=system_u:system_r:sendmail_t:s0 tcontext=system_u:object_r:sendmail_var_run_t:s0 tclass=file permissive=0
Comment 3RHEL Program Management
2023-09-21 22:06:51 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 4RHEL Program Management
2023-09-21 22:07:34 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.