Hi Jason,
> This means SELinux is ON in a kind of testing mode. It is only reporting
> what would be blocked and not "enforcing" anything. So the messages are
> basically informing you that you WILL have problems IF you enable enforcing
> mode.
> Checking AppDynamic PHP agent it does not support
> On 12 May 2015, at 03:39, Tim Dunphy wrote:
>* Plugin catchall_labels (83.8
> confidence) suggests ***...
> May 11 22:31:38 web1 python[14832]: SELinux is preventing
> /usr/lib/appdynamics-php5/proxy/jre/bin/java from block_suspend acce
Well, I was having a heck of a time with the rpm install in terms of
customizing the install directory.
So I thought the easy way out might be to go for a source install. Which I
tried and this was the output from the install:
[root@web1:/opt/AppDynamics/appdynamics-php-agent] #./install.sh
appd.
Tim Dunphy wrote:
>>
>> If rpm is configured for _that_ location of log files, I would remove
>> the
>> repository this rpm comes from from configuration and will remember to
>> never-never ever use that repository for anything.
>>
>> Just my $0.02
>
> Yeah I completely get where you're coming from
On Mon, May 11, 2015 10:38 am, Tim Dunphy wrote:
>>
>> If rpm is configured for _that_ location of log files, I would remove
>> the
>> repository this rpm comes from from configuration and will remember to
>> never-never ever use that repository for anything.
>>
>> Just my $0.02
>>
>
> Yeah I comp
Am 11.05.2015 um 16:47 schrieb Tim Dunphy :
>> That's a rather odd (personally, I think bad) place for a log (or
>> even logfile lock) and I'm not at all surprised that selinux is
>> keeping your application from writing there. I would check to see if
>> there is a setup/configuration option for yo
>
> If rpm is configured for _that_ location of log files, I would remove the
> repository this rpm comes from from configuration and will remember to
> never-never ever use that repository for anything.
>
> Just my $0.02
>
Yeah I completely get where you're coming from there. However it's not an
On Mon, May 11, 2015 9:47 am, Tim Dunphy wrote:
>>
>> That's a rather odd (personally, I think bad) place for a log (or
>> even logfile lock) and I'm not at all surprised that selinux is
>> keeping your application from writing there. I would check to see if
>> there is a setup/configuration optio
>
> That's a rather odd (personally, I think bad) place for a log (or
> even logfile lock) and I'm not at all surprised that selinux is
> keeping your application from writing there. I would check to see if
> there is a setup/configuration option for your application to put
> the log files and rela
Original Message
> Date: Sunday, May 10, 2015 09:02:11 PM -0400
> From: Tim Dunphy
>
> Hey guys,
>
> I've got another C7 problem I was hoping to solve. I
> installed appdynamics-php-agent-4.0.5.0-1.x86_64 on a C7.1 host.
>
> It's failing to communicate with it's contr
Hey guys,
I've got another C7 problem I was hoping to solve. I
installed appdynamics-php-agent-4.0.5.0-1.x86_64 on a C7.1 host.
It's failing to communicate with it's controller on another host. And this
is the interesting part. Whether or not I have SELinux enabled, I have
apache reporting SELinu
11 matches
Mail list logo
