System Bundle is in Starting mode | Community
Skip to main content
S
santhoshm687661
January 24, 2022
Solved

System Bundle is in Starting mode

  • January 24, 2022
  • 3 replies
  • 1455 views

Hi All,

 

We are using AEM 6.5.8 and 6.5.11 when we restart the server then we are noticeing the system bundle is in starting status until we stop the server and delete the index file.

 

Could you please let me know if any inputs?

 

Thanks,

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 Anny0505

@santhoshm687661 ,

 

Could you check your custom servlet which is implemented for QR code generation. I see there is some issue with servlet implementation QRCodeImagegenerator and Workflow process for deactivate.

 Please make sure to check your error log.

 

1. Try to open we-retail site and if the pages looks good on we-retail system wise configs and bundles looks good.

2. Next check is your custom code and verify error log and project spefipic log files. if any unresolved dependencies please install external jar files or add them in the maven pom.xml.

 

Hope this help you in identifying the issue.

 

Thanks!!

 

3 replies

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
January 24, 2022

which index files do you delete? under /crx-quickstart/repository? This shouldn't be the case unless there is some corruption in the repository or aem is not started with the correct permissions. 

 

I would suggest to review the error logs at the time of startup to understand if you see any repository specific exceptions which can be linked back to a problem with the repo or the file permissions.

 

    Anny0505
    Community Advisor
    Anny0505Community AdvisorAccepted solution
    Community Advisor
    January 24, 2022

    @santhoshm687661 ,

     

    Could you check your custom servlet which is implemented for QR code generation. I see there is some issue with servlet implementation QRCodeImagegenerator and Workflow process for deactivate.

     Please make sure to check your error log.

     

    1. Try to open we-retail site and if the pages looks good on we-retail system wise configs and bundles looks good.

    2. Next check is your custom code and verify error log and project spefipic log files. if any unresolved dependencies please install external jar files or add them in the maven pom.xml.

     

    Hope this help you in identifying the issue.

     

    Thanks!!

     

      joerghoh
      Adobe Employee
      joerghohAdobe Employee
      Adobe Employee
      January 25, 2022

      The log messages in the screenshot indicate that this is not the only problem, I see also errors in the PackageRegistry. Can you start from the top and share the first errors which appear there after the start?

        Terms & ConditionsAccessibility statement

        Loading footer...