Check is AEM Server is Up | Community
Skip to main content
raghavc
New Participant
August 8, 2016
Solved

Check is AEM Server is Up

  • August 8, 2016
  • 5 replies
  • 4304 views

Hi,

Is there a way to identify if the server startup is complete ?

I need to perform this as part of an env creation script, before the code can be deployed.

AEM version : 5.6.1

Thanks. 

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

Hi,

if you can parse the logs then you could look for the two messages below in either stdout.log or error.log

stdout.log  09.08.2016 08:09:53.807 *INFO * [main] Startup completed

error.log  09.08.2016 08:09:53.806 *INFO* [main] org.apache.felix.framework BundleEvent STARTED

Regards,

Opkar

5 replies

kautuk_sahni
Employee
August 9, 2016

Opkar Gill wrote...

Hi,

if you can parse the logs then you could look for the two messages below in either stdout.log or error.log

stdout.log  09.08.2016 08:09:53.807 *INFO * [main] Startup completed

error.log  09.08.2016 08:09:53.806 *INFO* [main] org.apache.felix.framework BundleEvent STARTED

Regards,

Opkar

 

 

Awesome Help Opkar. This adds information to my kitty.

~kautuk

Kautuk Sahni
raghavc
raghavcAuthor
New Participant
August 9, 2016
Thanks Opkar, will check that       
raghavc
raghavcAuthor
New Participant
August 9, 2016
Thanks Kautuk. Yes that's a good option. But is their any service available aem. As per adobe doc, status.bat file in bin folder of crx-quickstart should return the status, this did return a response when the server was started with start.bat.       
ogillAccepted solution
Employee
August 9, 2016

Hi,

if you can parse the logs then you could look for the two messages below in either stdout.log or error.log

stdout.log  09.08.2016 08:09:53.807 *INFO * [main] Startup completed

error.log  09.08.2016 08:09:53.806 *INFO* [main] org.apache.felix.framework BundleEvent STARTED

Regards,

Opkar

kautuk_sahni
Employee
August 9, 2016

Hi 

I am not sure, where i am wrong, but just check the response of "http://localhost:4502/", if it is responding you with 404 then it is not started.

Or 

Check for "http://localhost:4502/libs/granite/core/content/login.html?resource=%2F&$$login$$=%24%24login%24%24&j_reason=unknown&j_reason_code=unknown"    If 404 :- Not started

                                                                                                                                                                                                                                                   if response is there, then it is started.

~kautuk

Kautuk Sahni