Abrupt shut down of system-AEM authorinstance will not work | Community
Skip to main content
praveenk9004043
Level 4
May 22, 2016
Solved

Abrupt shut down of system-AEM authorinstance will not work

  • May 22, 2016
  • 11 replies
  • 6348 views

Hi Friends,

I came across a scenario in AEM6.1 author instance

There was a MCaffe patch update pushed to my system and there was an abrupt shout down of my system after which when I start running my AEM author instance I am getting the below error

~HTTP ERROR: 503

Problem accessing /. Reason:

    AuthenticationSupport service missing. Cannot authenticate request.

when I checked the logs I am able to see the below issues in error.log file

22.05.2016 10:27:59.412 *ERROR* [qtp1102906766-65] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
22.05.2016 10:27:59.412 *ERROR* [qtp1102906766-65] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
22.05.2016 10:27:59.494 *ERROR* [pool-7-thread-2] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.
22.05.2016 10:27:59.584 *ERROR* [qtp1102906766-64] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
22.05.2016 10:27:59.585 *ERROR* [qtp1102906766-64] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
22.05.2016 10:28:04.501 *ERROR* [pool-7-thread-5] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.
22.05.2016 10:28:09.504 *ERROR* [pool-7-thread-1] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.
22.05.2016 10:28:14.500 *ERROR* [pool-7-thread-4] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.
22.05.2016 10:28:19.505 *ERROR* [pool-7-thread-1] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.
22.05.2016 10:28:24.505 *ERROR* [pool-7-thread-5] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.
22.05.2016 10:28:29.499 *ERROR* [pool-7-thread-2] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.
22.05.2016 10:28:34.499 *ERROR* [pool-7-thread-2] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@3ab9cfdf with name Registered Service.375 and config SINGLE.

can someone help me why is this issue cause and let me know how to resolve this issue.

Regards

Pr@veen
 

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 praveenk9004043

This issue was resolved long back

I deleted all the index from the below folder path and i was able to start by author instance.

crx-quickstart\repository\index

11 replies

March 23, 2017

Thanks Praveen. This solution worked for me.