Upgrading CQ5.6.1 to AEM 6.1, authentication issues

4
votes

I have been following the instructions on
https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html

I reached "Once the upgrade is finished, the AEM homepage will be shown."

However, all I get is "an HTTP 503 status for all requests except for those under http:///system/console", exactly as described at the NOTE under this step.

The problem is that I always get this error, not only during the upgrade, but also after the upgrade is finished!

The error.log states: 

11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

Any help is highly appreciated.

5
aem
@Stravos I had to reinstall CQ. Only solution i found... – Nvan
I had the same problem, and the only solution was to reinstall. But it would be interesting to know why this happend. and if this happen again, then is reinstallation not a really good solution. I've already worked since half a year with aem 6.1 and then from one second to the other I get the error 503 and the server was death. – Try it

5 Answers

2
votes

We've encountered this once: There were issues with diskspace (the disk was simply full), make sure you have an adequate amount of space available.

2
votes

There could be two possible reasons:

  1. Some of the bundles are not active.
  2. Lucene is corrupt and hence not able to start

Possible fix is:

  1. Bring your bundles back to active, if it is not active.
  2. Stop your instance. go to crx-quickstart\repository\index and delete index folder.

Restart the instance (This will regenerate Lucene indexes fully).

1
votes

Quick fix:

  1. Stop the AEM instance.

  2. Go to folder crx-quickstart\repository\ remove folder index

  3. Start the AEM.

Everything should working fine. (It's working for me)

0
votes

Check the permissions under crx-quickstart\repository\ after you deleted the index.

0
votes

For me it had nothing to do with the segmentstore or the index or any unsatisfied bundles. Instead, it was the datastore.

The permissions for the datastore directory didn’t allow the user running aem to access it. The datastore directory is configured in org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.

This error really should reveal its root cause a little bit more easily. I’m sure it was somewhere in the logs, though…