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:
* traceback happens when email alerts are enabled and local mail servers are down
* SELinux denials are analyzed as expected, but email alerts are not sent
Version-Release number of selected component (if applicable):
setroubleshoot-server-3.0.47-11.el6.x86_64
setroubleshoot-plugins-3.0.40-2.el6.noarch
setroubleshoot-3.0.47-11.el6.x86_64
How reproducible:
* always
Steps to Reproduce:
0. echo "root@localhost filter_type=never" >> /var/lib/setroubleshoot/email_alert_recipients
1. stop all local mail servers
2. trigger an SELinux denial
3. look into /var/log/messages or /var/log/setroubleshoot/setroubleshootd.log
Actual results:
2016-10-25 02:54:06,364 [avc.ERROR] Exception during AVC analysis: [Errno 111] Connection refused
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 234, in run
self.analyze_avc(avc, report_receiver)
File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 214, in analyze_avc
report_receiver.report_problem(siginfo)
File "/usr/lib64/python2.6/site-packages/setroubleshoot/server.py", line 195, in report_problem
email_alert(siginfo, to_addrs)
File "/usr/lib64/python2.6/site-packages/setroubleshoot/email_alert.py", line 74, in email_alert
smtp = smtplib.SMTP(smtp_host, smtp_port)
File "/usr/lib64/python2.6/smtplib.py", line 244, in __init__
(code, msg) = self.connect(host, port)
File "/usr/lib64/python2.6/smtplib.py", line 300, in connect
self.sock = self._get_socket(host, port, self.timeout)
File "/usr/lib64/python2.6/smtplib.py", line 278, in _get_socket
return socket.create_connection((port, host), timeout)
File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
raise error, msg
error: [Errno 111] Connection refused
Expected results:
* all exceptions are handled
Description of problem: * traceback happens when email alerts are enabled and local mail servers are down * SELinux denials are analyzed as expected, but email alerts are not sent Version-Release number of selected component (if applicable): setroubleshoot-server-3.0.47-11.el6.x86_64 setroubleshoot-plugins-3.0.40-2.el6.noarch setroubleshoot-3.0.47-11.el6.x86_64 How reproducible: * always Steps to Reproduce: 0. echo "root@localhost filter_type=never" >> /var/lib/setroubleshoot/email_alert_recipients 1. stop all local mail servers 2. trigger an SELinux denial 3. look into /var/log/messages or /var/log/setroubleshoot/setroubleshootd.log Actual results: 2016-10-25 02:54:06,364 [avc.ERROR] Exception during AVC analysis: [Errno 111] Connection refused Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 234, in run self.analyze_avc(avc, report_receiver) File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 214, in analyze_avc report_receiver.report_problem(siginfo) File "/usr/lib64/python2.6/site-packages/setroubleshoot/server.py", line 195, in report_problem email_alert(siginfo, to_addrs) File "/usr/lib64/python2.6/site-packages/setroubleshoot/email_alert.py", line 74, in email_alert smtp = smtplib.SMTP(smtp_host, smtp_port) File "/usr/lib64/python2.6/smtplib.py", line 244, in __init__ (code, msg) = self.connect(host, port) File "/usr/lib64/python2.6/smtplib.py", line 300, in connect self.sock = self._get_socket(host, port, self.timeout) File "/usr/lib64/python2.6/smtplib.py", line 278, in _get_socket return socket.create_connection((port, host), timeout) File "/usr/lib64/python2.6/socket.py", line 567, in create_connection raise error, msg error: [Errno 111] Connection refused Expected results: * all exceptions are handled