Error while starting authoring instance | Community
Skip to main content
October 30, 2017
Solved

Error while starting authoring instance

  • October 30, 2017
  • 3 replies
  • 921 views

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?
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 kautuk_sahni

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

3 replies

edubey
Level 10
October 30, 2017

Was the instance stopped properly?

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

Thanks

October 30, 2017

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

kautuk_sahni
Community Manager
kautuk_sahniCommunity ManagerAccepted solution
Community Manager
October 30, 2017

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