OSGi console is blank in Production Author | Community
Skip to main content
Raja-Karuppsamy
Community Advisor
Raja-KaruppsamyCommunity Advisor
Community Advisor
December 24, 2021

OSGi console is blank in Production Author

  • December 24, 2021
  • 1 reply
  • 2254 views

Hi All,

 

We have seeing the blank page while accessing the OSGi console in Production author instance. We have tried to restart the server but still the issue persists.
Please note - we are not seeing the issue in lower environments and Production Publisher. All the bundles are in Active and we don't see anything in the error log as well. 

Anyone faced this issue ?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Vijayalakshmi_S
Vijayalakshmi_S
Level 10
December 27, 2021

Hi @raja-karuppsamy 

Are you able to access the other consoles (Say from Main/Sling). In particular, Web Console -> System Information.

If yes and if its allowed (perhaps off business hours), try to do Framework Restart from that console (Understand you already tried restarting the server itself, just a try from framework standpoint explicitly)

    Raja-Karuppsamy
    Community Advisor
    Raja-KaruppsamyCommunity AdvisorAuthor
    Community Advisor
    December 27, 2021

    @vijayalakshmi_s Thanks for your response.

    One thing I noticed today - I'm able to see the OSGi configuration if I access via IP address but NOT with Author DNS.

     

    Yes - I'm able to view/access other consoles in OSGi. Can you please let me know the impact if any ? when we run the framework restart ?  As mentioned - we are seeing this issue only in Production Author instance.

     

      Raja-Karuppsamy
      Community Advisor
      Raja-KaruppsamyCommunity AdvisorAuthor
      Community Advisor
      December 29, 2021

      Thanks for the inputs @raja-karuppsamy

      This JS is called when OSGi configuration console is accessed. Can you check the response code of this call - /system/console/res/ui/bundles.js (for Bundles console)

      Similarly, access frequently used consoles in author dispatcher and narrow down the requests that fails with 403. 

      Enable Dispatcher Debug log and trace the request from there and see if it makes to the application server. 

      Also, see if you can observe the behavior with admin login. 


      @vijayalakshmi_s We are getting 403 error response code for that js file and the error is occurring for Admin user as well. 

       

      We will check the Dispatcher log for the OSGi request and let you know.

        Terms & ConditionsAccessibility statement

        Loading footer...