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

"Upgrade to build number: 6169 - Not Ok" message appear in Confluence log while generating XML site backup.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 5.10.8, 6.0.6, 6.1.0, 6.3.2, 6.12.4, 7.5.0
    • Site - Backup / Import

      STEP TO REPLICATE

      1. Login to Confluence 6.1 with administrator account.
      2. Navigate to General Configuration > Backup and Restore
      3. Click of Backup to generate the XML site backup.

      EXPECTED BEHAVIOUR

      • The backup file was successfully created with no concerning logs.

      ACTUAL BEHAVIOUR

      • The backup file was successfully created.
      • Concerning INFO logs below appear in the logs:
        2017-03-24 02:00:01,831 INFO [Caesium-1-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6169: "Upgrade to build number: 6169" - Not Ok
        

      Notes

      This message is an INFO message and not a critical issue. If the backup is failing and this is the last message in the logs then something else likely to have happened. For example, Linux may have done an OOM kill of the process taking up too much memory or the JVM has had a java.lang.OutOfMemoryError.

            [CONFSERVER-52123] "Upgrade to build number: 6169 - Not Ok" message appear in Confluence log while generating XML site backup.

            Running into similar error. 

            INFO .......] GetExportBuilderNumber Backward compatibility for exprt: "Upgrade to build number: 6169" prevents compatibility before 6169

            ERROR [https-jsse-nio-9443-exec-2][engine.jdbc.spi.SqlExceptionHelper] LogExceptions Invalid object name 'EXTRNLNKS'

             

            Unable to create Backup on Confluence 6.14

            anshul.meena@nsc.eop.gov added a comment - Running into similar error.  INFO .......] GetExportBuilderNumber Backward compatibility for exprt: "Upgrade to build number: 6169" prevents compatibility before 6169 ERROR [https-jsse-nio-9443-exec-2] [engine.jdbc.spi.SqlExceptionHelper] LogExceptions Invalid object name 'EXTRNLNKS'   Unable to create Backup on Confluence 6.14

            +1

            6.8.0 

            Alberto Aragón added a comment - +1 6.8.0 

            +1

            6.0.4

            Hernan Montes added a comment - +1 6.0.4

            +1

            6.12.4

            Joost van Ingen added a comment - +1 6.12.4

            +1

            6.13.8

            +1

            6.15.9

            Filip Heyns added a comment - +1 6.15.9

            +1
            6.15.6

            Gonchik Tsymzhitov added a comment - +1 6.15.6

            Also happens on a fresh installation of Confluence 6.15.2.

            Manuel Bähnisch added a comment - Also happens on a fresh installation of Confluence 6.15.2.

            Jegan Ganesan added a comment - - edited

            Hi All,

            I upgraded my Confluence from 5.9 to 6.7.2, in the older version the backup was fine. After the upgradation both manual backup and schedule backup are failing.

            And am receiving the same error in the log.

            2018-03-25 22:16:29,390 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6189: "Upgrade to build number: 6189" - Ok
            2018-03-25 22:16:29,393 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6180: "Adds a multi-column index to content table that speeds up many common queries." - Ok
            2018-03-25 22:16:29,394 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6175: "Upgrade to build number: 6175" - Ok
            2018-03-25 22:16:29,394 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6169: "Upgrade to build number: 6169" - Not Ok
            2018-03-25 22:16:29,395 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: "Upgrade to build number: 6169" prevents compatibility before 6169
            2018-03-25 22:17:22,013 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
            
            

            Jegan Ganesan added a comment - - edited Hi All, I upgraded my Confluence from 5.9 to 6.7.2, in the older version the backup was fine. After the upgradation both manual backup and schedule backup are failing. And am receiving the same error in the log. 2018-03-25 22:16:29,390 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6189: "Upgrade to build number: 6189" - Ok 2018-03-25 22:16:29,393 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6180: "Adds a multi-column index to content table that speeds up many common queries." - Ok 2018-03-25 22:16:29,394 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6175: "Upgrade to build number: 6175" - Ok 2018-03-25 22:16:29,394 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6169: "Upgrade to build number: 6169" - Not Ok 2018-03-25 22:16:29,395 INFO [http-nio-9090-exec-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: "Upgrade to build number: 6169" prevents compatibility before 6169 2018-03-25 22:17:22,013 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message= 'LaaS performance logging is turned off' ]

            Mikhail Zholobov added a comment - - edited

            Hi all. I've run into the same issue on Confluence 6.1.3.

            When I try to do XML backup, I get the following messages in Confluence log:

            17-08-23 08:52:29,397 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: Checking...
            2017-08-23 08:52:29,399 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7109: "Drop and update some low performance indexes on EVENTS table for Synchrony" - Ok
            2017-08-23 08:52:29,399 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7108: "Update index sp_comp_idx when the definition is not correct" - Ok
            2017-08-23 08:52:29,400 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7106: "Drop the hibernate 2 constraints in preparation for them to be re-created in the hibernate 5 naming style" - Ok
            2017-08-23 08:52:29,401 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7105: "Drop or update some low performance indexes on CONTENT" - Ok
            2017-08-23 08:52:29,401 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7104: "Set the mime type for csv files to text/csv" - Ok
            2017-08-23 08:52:29,402 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7101: "Migrate over Documentation theme settings to Custom Page Settings in the default theme" - Ok
            2017-08-23 08:52:29,404 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6439: "Reindexes all PersonalInformation objects, creating them for any users that do not have one." - Ok
            2017-08-23 08:52:29,405 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6430: "Upgrade to build number: 6430" - Ok
            2017-08-23 08:52:29,407 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6424: "Adds missing multi-column unique constraints to the Crowd database tables" - Ok
            2017-08-23 08:52:29,409 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6423: "Cleaning data that violates constraints we want to add in the next migration task" - Ok
            2017-08-23 08:52:29,415 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6422: "Upgrade to build number: 6422" - Ok
            2017-08-23 08:52:29,417 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6412: "Delete all FileStore IDs" - Ok
            2017-08-23 08:52:29,418 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6406: "Reindex all spaces" - Ok
            2017-08-23 08:52:29,419 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6403: "Upgrade to build number: 6403" - Ok
            2017-08-23 08:52:29,420 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6193: "Rebuild the Confluence favourites index" - Ok
            2017-08-23 08:52:29,421 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6193: "Rebuild the Confluence favourites index" - Ok
            2017-08-23 08:52:29,422 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6189: "Upgrade to build number: 6189" - Ok
            2017-08-23 08:52:29,424 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6180: "Adds a multi-column index to content table that speeds up many common queries." - Ok
            2017-08-23 08:52:29,425 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6175: "Upgrade to build number: 6175" - Ok
            2017-08-23 08:52:29,426 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6169: "Upgrade to build number: 6169" - Not Ok
            2017-08-23 08:52:29,427 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: "Upgrade to build number: 6169" prevents compatibility before 6169
            

            Mikhail Zholobov added a comment - - edited Hi all. I've run into the same issue on Confluence 6.1.3. When I try to do XML backup, I get the following messages in Confluence log: 17-08-23 08:52:29,397 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: Checking... 2017-08-23 08:52:29,399 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7109: "Drop and update some low performance indexes on EVENTS table for Synchrony" - Ok 2017-08-23 08:52:29,399 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7108: "Update index sp_comp_idx when the definition is not correct" - Ok 2017-08-23 08:52:29,400 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7106: "Drop the hibernate 2 constraints in preparation for them to be re-created in the hibernate 5 naming style" - Ok 2017-08-23 08:52:29,401 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7105: "Drop or update some low performance indexes on CONTENT" - Ok 2017-08-23 08:52:29,401 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7104: "Set the mime type for csv files to text/csv" - Ok 2017-08-23 08:52:29,402 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 7101: "Migrate over Documentation theme settings to Custom Page Settings in the default theme" - Ok 2017-08-23 08:52:29,404 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6439: "Reindexes all PersonalInformation objects, creating them for any users that do not have one." - Ok 2017-08-23 08:52:29,405 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6430: "Upgrade to build number: 6430" - Ok 2017-08-23 08:52:29,407 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6424: "Adds missing multi-column unique constraints to the Crowd database tables" - Ok 2017-08-23 08:52:29,409 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6423: "Cleaning data that violates constraints we want to add in the next migration task" - Ok 2017-08-23 08:52:29,415 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6422: "Upgrade to build number: 6422" - Ok 2017-08-23 08:52:29,417 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6412: "Delete all FileStore IDs" - Ok 2017-08-23 08:52:29,418 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6406: "Reindex all spaces" - Ok 2017-08-23 08:52:29,419 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6403: "Upgrade to build number: 6403" - Ok 2017-08-23 08:52:29,420 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6193: "Rebuild the Confluence favourites index" - Ok 2017-08-23 08:52:29,421 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6193: "Rebuild the Confluence favourites index" - Ok 2017-08-23 08:52:29,422 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6189: "Upgrade to build number: 6189" - Ok 2017-08-23 08:52:29,424 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6180: "Adds a multi-column index to content table that speeds up many common queries." - Ok 2017-08-23 08:52:29,425 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6175: "Upgrade to build number: 6175" - Ok 2017-08-23 08:52:29,426 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6169: "Upgrade to build number: 6169" - Not Ok 2017-08-23 08:52:29,427 INFO [http-nio-8090-exec-17] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: "Upgrade to build number: 6169" prevents compatibility before 6169

              Unassigned Unassigned
              dazmi Dayana
              Affected customers:
              28 This affects my team
              Watchers:
              32 Start watching this issue

                Created:
                Updated: