Displaying 4 results from an estimated 4 matches for "passenger_exec_t".
2012 Nov 28
2
apache, passenger, and selinux
I seem to have quieted some, but I'm still getting noise from selinux.
Here's one that really puzzles me: my users have a ruby app with passenger
running. However, one of the sealerts gives me:
sealert -l 5a02b0a1-8512-4f71-b1c8-70a40b090a9d
SELinux is preventing /bin/chmod from using the fowner capability.
***** Plugin catchall_boolean (89.3 confidence) suggests
*******************
2015 Jun 21
2
puppet files denied by SELinux
...t context using the line you suggested I get an error:
#semanage fcontext -a -t passenger_t "/etc/puppet/environments(/.*)?"
ValueError: Type passenger_t is invalid, must be a file or device type
So I googled around and found what seems to be the correct syntax:
semanage fcontext -a -t passenger_exec_t "/etc/puppet/environments(/.*)?"
Because when I applied that line, I didn't get any errors or complaints.
However the problem still existed on the monitor2 host which had the key
pair copied from the NFS share.
So in summary it appears that there is some interaction between SELinux...
2015 Jun 29
1
puppet files denied by SELinux
...gt;
>> #semanage fcontext -a -t passenger_t "/etc/puppet/environments(/.*)?"
>> ValueError: Type passenger_t is invalid, must be a file or device type
>>
>> So I googled around and found what seems to be the correct syntax:
>>
>> semanage fcontext -a -t passenger_exec_t "/etc/puppet/environments(/.*)?"
>>
>> Because when I applied that line, I didn't get any errors or complaints.
>> However the problem still existed on the monitor2 host which had the key
>> pair copied from the NFS share.
>>
>> So in summary it app...
2015 Jun 21
0
puppet files denied by SELinux
...d I get an
> error:
>
> #semanage fcontext -a -t passenger_t "/etc/puppet/environments(/.*)?"
> ValueError: Type passenger_t is invalid, must be a file or device type
>
> So I googled around and found what seems to be the correct syntax:
>
> semanage fcontext -a -t passenger_exec_t "/etc/puppet/environments(/.*)?"
>
> Because when I applied that line, I didn't get any errors or complaints.
> However the problem still existed on the monitor2 host which had the key
> pair copied from the NFS share.
>
> So in summary it appears that there is some...