Bad Gateway after upgrading from AEM 6.5.5 to 6.5.21 | Community
Skip to main content
M
MR_Nurfajri
Level 2
November 26, 2024

Bad Gateway after upgrading from AEM 6.5.5 to 6.5.21

  • November 26, 2024
  • 4 replies
  • 1535 views

Hi, I've recently upgraded my AEM instance on dev environment from 6.5.5 to 6.5.21 and after I've restarted the instance, it's responded with bad gateway 502 on the instance link itself and /system/console/bundles. I have tried checking if there are any invalid indexes and all of them are valid when i checked. Any suggestions on what steps should I take next to mitigate this issue?

4 replies

kaikubad
Community Advisor
kaikubadCommunity Advisor
Community Advisor
November 26, 2024

Go through this release note first. make sure you followed all the necessary steps and made changes accordingly. We did the same last month.

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/service-pack/6-5-21

    M
    MR_NurfajriAuthor
    Level 2
    November 26, 2024

    I have followed the steps from the documentation

      MukeshYadav_
      Community Advisor
      MukeshYadav_Community Advisor
      Community Advisor
      November 26, 2024

      Hi, 

      It might be some config issue, is there any error hint in log?

      https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/bad-gateway/m-p/219770

      Thanks

        M
        MR_NurfajriAuthor
        Level 2
        November 26, 2024

        Hi @mukeshyadav_  as far as I've checked on the error log, this is the first cause of error

        [OsgiInstallerImpl] updater.fake.bundle BundleEvent INSTALLED
        25.11.2024 12:47:26.781 *INFO* [OsgiInstallerImpl] org.apache.sling.audit.osgi.installer Installed bundle updater.fake.bundle [768] from resource TaskResource(url=bundle767:fake.jar, entity=bundle:updater.fake.bundle, state=INSTALL, attributes=[org.apache.sling.installer.api.tasks.ResourceTransformer=:31:17:, Bundle-SymbolicName=updater.fake.bundle, Bundle-Version=1.0], digest=0)
        25.11.2024 12:47:26.784 *INFO* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start bundle updater.fake.bundle [768]. Reason: {}. Will retry.
        org.osgi.framework.BundleException: Unable to resolve updater.fake.bundle [768](R 768.0😞 missing requirement [updater.fake.bundle [768](R 768.0)] osgi.wiring.package; (osgi.wiring.package=updater.fake.bundle) Unresolved requirements: [[updater.fake.bundle [768](R 768.0)] osgi.wiring.package; (osgi.wiring.package=updater.fake.bundle)]
          at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
          at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
          at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
          at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
          at org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(BundleStartTask.java:97) [org.apache.sling.installer.core:3.9.0]
          at org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:914) [org.apache.sling.installer.core:3.9.0]
          at org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:749) [org.apache.sling.installer.core:3.9.0]
          at org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:298) [org.apache.sling.installer.core:3.9.0]
          at java.lang.Thread.run(Thread.java:748)
        aanchal-sikka
        Community Advisor
        aanchal-sikkaCommunity Advisor
        Community Advisor
        November 26, 2024

        @mr_nurfajri 

         

        Please try updating a local AEM 6.5 with AEM 6.5.21 first.

         

         

        If you have a clone of dev instance, please try after successful upgrade of local AEM. Please assure that you restart instance after the Service Pack was Installed + All bundles Active + logs stable

         

        We had upgarded to 6.5.21 recently with no issues

        Aanchal Sikka
          M
          MR_NurfajriAuthor
          Level 2
          November 26, 2024

          @aanchal-sikka  I have tested it with my local and other dev environment, it worked and all of the bundles are active. Currently I am using the backup of the dev env and have uploaded the package and it's said "A different version seems to be installed: 6.5.5", could this be the issue? 

           

          Preetpal_Bindra
          Community Advisor
          Preetpal_BindraCommunity Advisor
          Community Advisor
          November 26, 2024

          @mr_nurfajri 

          Yes,

          1. that warning message says that the installed package is not version 21, and,

          2. The install button is enabled,

           

          Indicates that the package version is not installed. Could you please try installing it and see if you are still experiencing problems.

          Feel free to post the result or ask additional questions in this forum.

           

          Thank you.

            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            February 10, 2025

            @mr_nurfajri Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

            Kautuk Sahni
            Terms & ConditionsAccessibility statement

            Loading footer...