Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-3924

2.8 upgrade hangs with "Error while trying to initialise Crowd Container"

XMLWordPrintable

      I have seen this twice.

      Upon the first start-up after upgrading from 2.7.2-rc4 to 2.8.0-m1, the log stops at the following line and the Crowd server does not proceed to finish the start-up:

      2014-05-22 06:24:51,769 localhost-startStop-1 INFO [atlassian.plugin.manager.DefaultPluginManager] Plugin system started in 0:00:11.075
2014-05-22 06:24:51,789 localhost-startStop-1 INFO [ContainerBase.[Catalina].[localhost].[/crowd]] org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)

      If accessing the Crowd Console, I will see an error screen saying:

      fatal Error while trying to initialise Crowd Container. could not perform addBatch

      (See attached the screenshot and the complete log).

      I needed to restart once or twice to get the Crowd Server completely started. (For one occurrence of the issue, I only needed to restart once; for another time, I needed to restart twice.)

        1. atlassian-crowd.log
          347 kB
        2. Atlassian Crowd - System Errors - Google Chrome_999.png
          Atlassian Crowd - System Errors - Google Chrome_999.png
          52 kB

            [CWD-3924] 2.8 upgrade hangs with "Error while trying to initialise Crowd Container"

            Ishwinder Kaur added a comment -
            Atlassian Update - 9 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Crowd Data Center, please check our public roadmap.

            Kind regards,
            Crowd Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 9 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Crowd Data Center, please check our public roadmap . Kind regards, Crowd Data Center

            Peguiron Ernst, Mathias added a comment -

            I experienced the same error message (in the context of database restore) and then quickly recognized that I forgot to grant access to the database for the connecting "crowddbuser".

            Peguiron Ernst, Mathias added a comment - I experienced the same error message (in the context of database restore) and then quickly recognized that I forgot to grant access to the database for the connecting "crowddbuser".

            Pablo da Silva [ACP-JA] added a comment -

            Hi, i was experiencing the same problem upgrading to 3.1.2,  looks like the issue was a process locked on the database, so i restarted the MySql service, stopped the Crowd script and ran it  again and the upgrade process worked fine then.

             

            Pablo da Silva [ACP-JA] added a comment - Hi, i was experiencing the same problem upgrading to 3.1.2,  looks like the issue was a process locked on the database, so i restarted the MySql service, stopped the Crowd script and ran it  again and the upgrade process worked fine then.  

            Hemant added a comment -

            Any updates on this? I upgraded crowd to 2.10 and failed similarly.

            Hemant added a comment - Any updates on this? I upgraded crowd to 2.10 and failed similarly.

            Tahir Raza added a comment -

            Any updates on this? I upgraded crowd to 2.10 and failed similarly.

            Tahir Raza added a comment - Any updates on this? I upgraded crowd to 2.10 and failed similarly.

              Unassigned Unassigned
              zxu@atlassian.com Zhuang Xu (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: