ent if a failure is detected.
>
> - Si
>
>
> From: Marcus
> Sent: Monday, February 23, 2015 10:21 AM
> To: dev@cloudstack.apache.org
> Cc: us...@cloudstack.apache.org
> Subject: Re: Agent dies every night/morning memory violation
>
> It doesn't reall
start cloudstack-agent if
a failure is detected.
- Si
From: Marcus
Sent: Monday, February 23, 2015 10:21 AM
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: Re: Agent dies every night/morning memory violation
It doesn't re
21/02/2015 06:39:38 1905 jsvc.exec error: Service did not exit cleanly
>>
>> On 20 February 2015 at 21:56, Simon Weller wrote:
>>
>>> Andrija,
>>>
>>> What is SELinux set to on this host?
>>>
>>>
>>> - SI
>>>
>>&g
'
> 21/02/2015 06:39:38 1905 jsvc.exec error: Service did not exit cleanly
>
> On 20 February 2015 at 21:56, Simon Weller wrote:
>
>> Andrija,
>>
>> What is SELinux set to on this host?
>>
>>
>> - SI
>>
>>
>> ____
__
> From: Andrija Panic
> Sent: Friday, February 20, 2015 6:06 AM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: Agent dies every night/morning memory violation
>
> Hi,
>
> I have crazy agent on one of the hosts,
Andrija,
What is SELinux set to on this host?
- SI
From: Andrija Panic
Sent: Friday, February 20, 2015 6:06 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Agent dies every night/morning memory violation
Hi,
I have crazy
Hi,
I have crazy agent on one of the hosts, that is being killed each morning
and I found this in /var/log/audit.log:
type=ANOM_ABEND msg=audit(1424321463.930:430678): auid=0 uid=0 gid=0
ses=68891 pid=10831 comm="jsvc" reason="memory violation" sig=6
I dont remember changing anything on the syst
