Thanks nseagoon! But that didn't help. I already did that. And I'm still
trying to understand the audit log.
Does any one have any other suggestion(s) for me? Cheers!!
On Monday, May 28, 2012 3:48:03 AM UTC+1, nseagoon wrote:
If you're running puppet as a daemon with selinux in enforcing
On Tue, May 29, 2012 at 1:39 PM, Sans r.santanu@gmail.com wrote:
Thanks nseagoon! But that didn't help. I already did that. And I'm still
trying to understand the audit log.
Does any one have any other suggestion(s) for me? Cheers!!
It may be useful for you to install the 'setroubleshoot'
Thanks Brian!
I'm still trying to find out how to make it work, with no such joy so far.
Anyone from PuppetLab care to comment?
Cheers!!
On Monday, May 14, 2012 1:08:38 PM UTC+1, Brian Gupta wrote:
I've run into permission errors like this if apparmor is enabled, and not
configured for the
If you're running puppet as a daemon with selinux in enforcing mode, I
think you may need to run:
setsebool puppetmaster_use_db on
In the current state and presuming that the audit daemon is running,
/var/log/audit/audit.log should be reporting which aspect of selinux is
preventing the access
I've run into permission errors like this if apparmor is enabled, and not
configured for the app I am trying to run.
http://en.wikipedia.org/wiki/AppArmor
I'm guessing you need to tell selinux that /usr/share/puppet-dashboard/* is
a valid path. (Never used selinux, but my understanding is that
Dear all,
Can anyone please tell me why Ruby on Rails application is not starting,
when SELinux is on. This is the errors reporting on the browser:
The application has exited during startup (i.e. during the evaluation of
config/environment.rb). The error message can be found below. To solve
