Unfortunately, the both foreman-selinux commands and the autorelabel did not help. Also, our policy would prevent me from using foreman-debug -u. I count over 10000 lines of data I'd have to clean information out of in order to do the upload. If I take the manual data collection approach, is there a way I can send it privately to the foreman core developers? I will have to scrub data information from the manual collection as well, but there is less information there.
Thanks! On Wednesday, July 20, 2016 at 3:47:30 AM UTC-4, Lukas Zapletal wrote: > > > After restarting the httpd service (Enforcing) and visiting foreman in > the > > browser we get a nice big ruby on rails dump with a permission denied > > making a directory. In the audit log there are about 14 AVC denials > > related to foreman/passenger (I can provide if desired, but didn't want > to > > put garbage on the list). Switching to Permissive, and reloading the > page > > from the browser works fine (with or without restarting httpd), so I > > conclude there no actual file permission issue. Any ideas? I'd really > > like to get back to running enforcing mode. > > Hi, > > > http://projects.theforeman.org/projects/foreman/wiki/Troubleshooting#SELinux-denials > > > -- > Later, > Lukas #lzap Zapletal > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
