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:
During SMB authentication the main cronie process terminates so no other jobs are executed after a single auth fault.
Before 1.4.7 and patch
https://github.com/cronie-crond/cronie/commit/ee4cbe7659ede3f61db18cc922ee0e27268a8579?diff=unified
cronie was known to be overly sensitive to SIGPIPE.
Version-Release number of selected component (if applicable):
cronie-1.4.4-16.el6_8.2
How reproducible:
Often in customer's environment
Steps to Reproduce:
1. setup crontab for user in SMB domain
2. observe SMB auth failure
Actual results:
main cronie process terminates on SIGPIPE, no record in logs
Expected results:
cronie logs the auth failure and recovers, continues serving subsequent jobs
Additional info:
messages events preceding the cronie crash:
[2018/07/29 19:39:09.683477, 0] auth/pampass.c:589(smb_pam_account)
smb_pam_account: PAM: UNKNOWN PAM ERROR (4) during Account Management for User: netadmin
[2018/07/29 19:39:09.683612, 0] auth/pampass.c:797(smb_pam_accountcheck)
smb_pam_accountcheck: PAM: Account Validation Failed - Rejecting User netadmin!
[2018/07/29 19:39:09.684137, 0] rpc_server/srv_pipe.c:835(pipe_gssapi_verify_final)
rpc_server/srv_pipe.c:835: failed to obtain the server info for authenticated user: NT_STATUS_ACCESS_DENIED
[2018/07/29 19:39:09.684270, 0] rpc_server/srv_pipe.c:1608(api_pipe_alter_context)
Jul 29 19:39:01 server CROND[26999]: (smbuser) CMD (some cmd)
Jul 29 19:52:28 server crond[3308]: (CRON) STARTUP (1.4.4) (manual)
in cronie strace:
...
connect(7, {sa_family=AF_LOCAL, sun_path="/var/lib/samba/winbindd_privileged/pipe"}, 110) = 0 <0.000132>
...
write(7, "0\10 ...0\0\0smbuser\0\0\...
--- SIGPIPE
Could you please provide a reproducer more specific than the one described above?
I'm a Cronie maintainer but I have no experience with Samba tools, so a specific reproducer would really help me debug this issue.
Created attachment 1490880[details]
Backport of upstream patch
I have managed to reproduce this using:
# killall -SIGPIPE crond
I've tried and backported the upstream patch.
After the backport, I have not been able to reproduce the crash.
I'm attaching the patch.