Unable to start AEM - equestLogin=1 10.05.2017 10:43:46.521 *ERROR* [pool-6-thread-1] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery avail | Community
Skip to main content
A
aembytes
New Participant
May 10, 2017
Solved

Unable to start AEM - equestLogin=1 10.05.2017 10:43:46.521 *ERROR* [pool-6-thread-1] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery avail

  • May 10, 2017
  • 6 replies
  • 4643 views

Unable to start AEM with errors like mentioned in the subject and repository service unregistering

 org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@395786be with name Registered Service.351 and config SINGLE.
10.05.2017 10:45:26.521 *ERROR* [pool-6-thread-3] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@395786be with name Registered Service.351 and config SINGLE.
10.05.2017 10:45:31.521 *ERROR* [pool-6-thread-5] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@395786be with name Registered Service.351 and config SINGLE.
10.05.2017 10:45:36.520 *ERROR* [pool-6-thread-3] org.apache.sling.commons.scheduler.impl.QuartzScheduler No discovery available, therefore not executing job org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@395786be with name Registered Service.351 and config SINGLE.

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 MC_Stuff

Hi Ronny,

https://gist.githubusercontent.com/stillalex/43c49af065e3dd1fd5bf/raw/9e726a59f75b46e7b474f7ac763b0888d5a3f0c3/rmNode.groovy

java -Xmx4096m -jar oak-run-1.1.8.jar console crx-quickstart/repository/segmentstore


In the console tool shell, run these commands:

:load rmNode.groovy
rmNode(session, "/:async")
rmNode(session, "/oak:index/damAssetLucene/:data")
#....Add all async index :data ......
:exit

 

Thanks,

6 replies

Nagesh_Mohan
Nagesh_Mohan
New Participant
December 18, 2018

Hi,

Do we need run only below commands or do we need to run the command which mentioned in url(https://gist.githubusercontent.com/stillalex/43c49af065e3dd1fd… )

:load rmNode.groovy

rmNode(session, "/:async")

rmNode(session, "/oak:index/damAssetLucene/:data")

#....Add all async index :data ......

:exit

MC_Stuff
MC_StuffAccepted solution
New Participant
May 13, 2017

Hi Ronny,

https://gist.githubusercontent.com/stillalex/43c49af065e3dd1fd5bf/raw/9e726a59f75b46e7b474f7ac763b0888d5a3f0c3/rmNode.groovy

java -Xmx4096m -jar oak-run-1.1.8.jar console crx-quickstart/repository/segmentstore


In the console tool shell, run these commands:

:load rmNode.groovy
rmNode(session, "/:async")
rmNode(session, "/oak:index/damAssetLucene/:data")
#....Add all async index :data ......
:exit

 

Thanks,

ronnyfm
ronnyfm
New Participant
May 12, 2017
        ¿Do you mean running a command via oak-run-*.jar? Do you have a sample command for that? Thanks.
MC_Stuff
MC_Stuff
New Participant
May 11, 2017

Hi Ronny,

  Symptoms indicates reindex issue.  If you are familiar with oak console then remove :data on index def and start the instance otherwise Get official support help.

Thanks,

ronnyfm
ronnyfm
New Participant
May 10, 2017
        Any sucess? Facing same error since a couple of days ago. Not sure what happened. I already tried by deleting /repository/index. No luck, same result. The instance, eventually starts up, but after some time it is unresponsive.
smacdonald2008
smacdonald2008
New Participant
May 10, 2017

Has someone removed bunldes from AEM? Looks like something was removed from the AEM service container. Did this just start happening? 

Terms & ConditionsAccessibility statement

Loading footer...