Error after applying hotfix 7310 (Oak Upgrade 1.0.19) after premature restart | Community
Skip to main content
Level 3
November 10, 2015
Solved

Error after applying hotfix 7310 (Oak Upgrade 1.0.19) after premature restart

  • November 10, 2015
  • 4 replies
  • 1863 views

We are trying to apply hotfix 7310 to an AEM 6.0 SP2 environment for Jackrabbit Oak 1.0.19. We have successfully installed on other similar environments.

We believe the instance may have been prematurely restarted manually before installation had finished and we are now getting the following:

10.11.2015 17:46:19.577 *ERROR* [qtp814541868-33] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
10.11.2015 17:46:19.577 *ERROR* [qtp814541868-33] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

We are unable to login to any consoles and the instance does not fully start up.

How can we resolve this?

Thanks,

Alex

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 Sham_HC

The quickest approach would be Restore the instance before hotfix installation. Then install the hotfix.

4 replies

Sham_HC
Sham_HCAccepted solution
Level 10
November 10, 2015

The quickest approach would be Restore the instance before hotfix installation. Then install the hotfix.

a_lex_Author
Level 3
November 10, 2015

Are there any other approaches to solve this?

 

Alex

Adobe Employee
November 10, 2015

The above message is a symptom of an earlier issue during startup that caused the repository not to start. Please check and see if it resolvable.

Regards,

Opkar

a_lex_Author
Level 3
November 13, 2015

Hello,

We were able to restore the first instance (mentioned previously) and successfully install Oak 1.0.19

When we attempted to install on our second publisher, the instance restarted and now hangs again - this time with a different issue:

 

13.11.2015 00:21:35.350 *INFO* [main] org.apache.felix.framework BundleEvent STARTED 13.11.2015 00:21:35.382 *INFO* [FelixDispatchQueue] com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener StartupListener.startupFinished called 13.11.2015 00:21:35.382 *INFO* [FelixDispatchQueue] com.adobe.granite.installer.factory.packages.impl.PackageTransformer Running in RESTART mode 13.11.2015 00:21:35.382 *INFO* [FelixDispatchQueue] org.apache.felix.framework FrameworkEvent STARTED 13.11.2015 00:21:35.413 *INFO* [Adobe Granite Maintenance Scheduler Update Task] org.apache.sling.hc.core Service [2165] ServiceEvent REGISTERED 13.11.2015 00:21:35.413 *INFO* [Adobe Granite Maintenance Scheduler Update Task] com.adobe.granite.maintenance.core Service [2164] ServiceEvent REGISTERED 13.11.2015 00:21:35.429 *INFO* [Adobe Granite Maintenance Scheduler Update Task] org.apache.sling.hc.core Service [2167] ServiceEvent REGISTERED 13.11.2015 00:21:35.429 *INFO* [Adobe Granite Maintenance Scheduler Update Task] com.adobe.granite.maintenance.core Service [2166] ServiceEvent REGISTERED 13.11.2015 00:21:35.772 *INFO* [Workflow Starter Thread] com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener Startup finished, workflow queue processing starting

 

The instance will not go past the last line of the attached log...

The two instances are identical so I am unsure why we would have the issue on one but not the other. Anyone have any ideas?