Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-31055

fatal error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Support Request
    • Icon: Low Low
    • None
    • 5.2, 5.2.5, 5.3
    • None

      We are getting an fatal error after an update from 5.1.5 to 5.3

      Type:
      startup

      Description:
      This installation of Confluence has failed one or more bootstrap configuration checks. Please check the logs for details.

      Your server id is: BAJU-NUEW-6FLB-0FZ5

      Exception:
      Detected tables with non-default collation. See https://confluence.atlassian.com/x/TABrFw

      Level:
      fatal

      Time:
      2013-10-04 08:54:57

      We've also tryed to fix this Problem with this solution but without any success.

      https://confluence.atlassian.com/display/CONFKB/Change+MySQL+Database+Character+Encoding+to+UTF8+During+Server+Migration

          Form Name

            [CONFSERVER-31055] fatal error

            Mike Krejci added a comment -

            Thank you, I actually solved my problem already. It was that some of the tables still did not have the collation set utf8_bin. They were missed because they were previously utf8_general and not LATIN1. Doing a SHOW TABLE STATUS listed all the tables and showed me which ones I had missed, then it was a simple matter to just alter those tables individually.

            Mike Krejci added a comment - Thank you, I actually solved my problem already. It was that some of the tables still did not have the collation set utf8_bin. They were missed because they were previously utf8_general and not LATIN1. Doing a SHOW TABLE STATUS listed all the tables and showed me which ones I had missed, then it was a simple matter to just alter those tables individually.

            Steve Haffenden (Inactive) added a comment -

            Hi mk7

            Thanks for getting in touch. I think the best course of action would be for you to create a support ticket. Once the support team have your details they'll be in touch to work with you in resolving this issue.

            You can create a support ticket on http://support.atlassian.com

            Regards

            Steve Haffenden (Inactive) added a comment - Hi mk7 Thanks for getting in touch. I think the best course of action would be for you to create a support ticket. Once the support team have your details they'll be in touch to work with you in resolving this issue. You can create a support ticket on http://support.atlassian.com Regards

            Mike Krejci added a comment -

            I have this same issue. I upgraded to 5.3 and get the same error message and have applied all the suggested fixes and I still get the error.

            Mike Krejci added a comment - I have this same issue. I upgraded to 5.3 and get the same error message and have applied all the suggested fixes and I still get the error.

            Steve Haffenden (Inactive) added a comment -

            Hi software24

            Thanks for raising this issue. This sounds like something that our support team should be able to help you with. I've created the following support request: https://support.atlassian.com/browse/CSP-110938 and someone from the team will be in touch shortly to help resolve your problems.

            Regards

            Steve Haffenden (Inactive) added a comment - Hi software24 Thanks for raising this issue. This sounds like something that our support team should be able to help you with. I've created the following support request: https://support.atlassian.com/browse/CSP-110938 and someone from the team will be in touch shortly to help resolve your problems. Regards

              shaffenden Steve Haffenden (Inactive)
              9cf65cb647e7 Kian Toyouri Gould
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: