Troubleshooting for failed OSGi installer configurations

This article explains how to troubleshoot issues where OSGi configurations or bundles fail to install when placed under the crx-quickstart/install folder of an AEM installation.

If you have placed a configuration or bundle under the crx-quickstart/install folder of your AEM installation and it fails to install, then follow the steps below to debug the issue.

Go to http://host:port/system/console/osgi-installer and log in as admin.

On this user interface, it shows which bundles and configurations were applied and when. This includes files applied via crx-quickstart/install folder and ones in JCR (Oak) repository install folders.

In addition to the osgi-installer tool, you can enable debug logging on the installer modules. Go to http://host:port/system/console/slinglog

Click Add New Logger.

Set Log Level to Debug.

Set Log File to logs/installer.log

Add these Loggers: org.apache.felix.fileinstall, org.apache.sling.installer

Save.

Now when you make changes to the install folder files, you see corresponding log messages in the installer.log

Some things that could cause the OSGi installer to fail are:

A syntax error in the .config or .cfg file that was applied. A syntax reference for the .cfg and .config files can be found here:
- http://felix.apache.org/documentation/subprojects/apache-felix-file-install.html
- https://sling.apache.org/documentation/bundles/configuration-installer-factory.html#configuration-files-config
Failure of the system to unpause the JCR install module. Follow this article.
Malfunctioning of the installer module - if you suspect this, then contact AEM Customer Care.

De voorwaarden van Creative Commons zijn niet van toepassing op Twitter™- en Facebook-berichten.

Juridische kennisgevingen | Online privacybeleid

Troubleshooting for failed OSGi installer configurations

Vraag het de community

Contact met ons opnemen