AEM 6.1 unexpectedly shutting down | Community
Skip to main content
beths25520175
beths25520175
July 20, 2016

AEM 6.1 unexpectedly shutting down

  • July 20, 2016
  • 4 replies
  • 2061 views

Has anyone experienced AEM 6.1 unexpectedly shutting down? It's not a process crash - the logs indicate a full shutdown of felix and everything stopping nicely - no errors. We can't see what is triggering this - it's at odd times of day - it happened yesterday and today on the same publish instance - has anyone experienced this? Any idea what could cause unexpected AEM 6.1 shutdown? 

Thanks,

Beth

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

smacdonald2008
smacdonald2008
Level 10
July 20, 2016

I have asked our support team to look at this. I am not aware of any community KBs that addressed this situation. 

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
July 21, 2016

is it happening on every instance of AEM version or only a particular instance of AEM ? 

Did it started recently or from the instance instantiation ? 

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
July 21, 2016

Hi 

Is this behavior started recently? if so, please try to revert the code changes to the change list till it was working fine.

And if you try it on vanilla instance, is it still happening ?

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
beths25520175
beths25520175Author
July 21, 2016

Hi all,

1. It's happened on one particular instance - we have 4 production publish instances, and this is just one of them.

2. Not related to a code update.

3. It started recently - not since the instance was created.

I guess it has to be some rogue monitoring script or tool that is doing it, but I thought perhaps that there was some security setting or feature in AEM that would cause it to shut down?

smacdonald2008
smacdonald2008
Level 10
July 21, 2016

Support response on this:

I have never seen such an issue before.  It sounds like something outside of AEM is sending a SIGTERM (kill) signal to the AEM java process.  I would suggest they look for patterns to see if it always happens at the same time of day, whether there are any suspicious cron jobs.  Also enable audit logging in linux to see if somebody or something is shutting it down

Terms & ConditionsAccessibility statement

Loading footer...