Bug 901495
| Summary: | no reasonable troubleshooting help for httpd_can_network_connect_db | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | udo.rader | ||||||
| Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 18 | CC: | dwalsh, mgrepl | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-04-24 19:36:51 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: | |||||||||
| Attachments: |
|
||||||||
Strange can you send me the AVC messages and I will try to duplicate. Created attachment 682467 [details]
audit log excerpt containing the AVC message
Those AVC's worked fine for me. If you just cat them into /usr/bin/sedispatch I get three options. |
Created attachment 682295 [details] sealert screenshot showing the problem after upgrading fom f17 to f18, I got SE alerts about httpd (apache) trying to make a "name_connect", see the attached screenshot. The issue behind the alert is that apache tries to establish a php-mssql database connection that is prevented by the selinux configuration. What I expect is to get "real" troubleshooting by sealert and no generic "file a bug if you want to allow httpd making name_connect in tcp ports". If I open the details of the issue, all required troubleshooting information is there, see the "SETroubleshoot Details Window" in the screenshot again.