Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Error while starting authoring instance

Avatar

Level 1

I am getting below error on restarting an authoring instance. This is on a Unix box.

HTTP ERROR: 503

Problem accessing /. Reason:

AuthenticationSupport service missing. Cannot authenticate request.

What could be the reason and the solution?
1 Accepted Solution

Avatar

Correct answer by
Administrator

You get that error when the authentication bundles haven't started yet. In some cases this is just a matter of time - the startup may still progress. If it isn't just time then there are any number of reasons why the authentication bundles might not have started. There are two steps you need to take to troubleshoot the issues:

    Look at your error.log during startup and look for exceptions and error messages. These exceptions and error messages will clue you into what the problem is.

    If you don't see error messages log into Felix and see if you have any bundles that aren't starting and try to manually start them and watch the error logs while you are manually starting them.

~kautuk



Kautuk Sahni

View solution in original post

3 Replies

Avatar

Level 10

Was the instance stopped properly?

Try to delete \crx-quickstart\repository\index folder and restart author.

Thanks

Avatar

Level 1

Yes the instance was stopped properly. We had an offline compaction. After we started the instance again, nothing came up. Hence tried restarting again.

Avatar

Correct answer by
Administrator

You get that error when the authentication bundles haven't started yet. In some cases this is just a matter of time - the startup may still progress. If it isn't just time then there are any number of reasons why the authentication bundles might not have started. There are two steps you need to take to troubleshoot the issues:

    Look at your error.log during startup and look for exceptions and error messages. These exceptions and error messages will clue you into what the problem is.

    If you don't see error messages log into Felix and see if you have any bundles that aren't starting and try to manually start them and watch the error logs while you are manually starting them.

~kautuk



Kautuk Sahni