It stopped again. This time with 3G of memory. I piped the console logs to a file and here is the output1.11.2017 21:15:56.632 *INFO * [main] Setting sling.home=sling (default)01.11.2017 21:15:56.633 *INFO * [main] Starting Apache Sling in /home/ubuntu/aem-install/author/sling01.11.2017 21:15:56.636...

How much memory is recommended ? I can try that straight away and get back to you.Ok I am trying with 3G for Author and Publisher. I will post here if I see the same issue again.

I checked the error log, it does not have any max heap errors. I can share it with you. I uploaded my error.log here. https://s3.console.aws.amazon.com/s3/object/symphony-aem/error.log?region=us-east-1&tab=overviewI know this is cumbersome, but maybe you can look towards the end of the file and migh...

yes, the app comes up. I am even able to play around a bit, but then after few mins ~11 mins in some cases or ~1 hour when I give more memory, sling shuts down by itself.

I have a quickstart jar. After running it for a while, I see in the logs that Java VM is shutting down and sling is stopping. Any idea what is going on ?My java version is 1.8 SEI am giving Xmx 1024m while starting the jar.