Bamboo fails to import with EOF exception

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問


プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。

問題

Bamboo import fails with EOF exception when importing from an older instance to a new Bamboo Server.

  • Export from old Bamboo Server
  • Import to new Bamboo Server


The following error log appears during the import process on the new server.

Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677)
at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2119)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2025)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1117)
at org.codehaus.staxmate.in.SMHierarchicCursor.getNext(SMHierarchicCursor.java:72)
at org.codehaus.staxmate.in.SMInputCursor.advance(SMInputCursor.java:1631)
at com.atlassian.bamboo.migration.XmlMigrator.importFromFile(XmlMigrator.java:375)
at com.atlassian.bamboo.migration.XmlMigrator.importXmlData(XmlMigrator.java:339)
at com.atlassian.bamboo.migration.XmlMigrator.loadXmlData(XmlMigrator.java:326)
at com.atlassian.bamboo.migration.XmlMigrator.access$100(XmlMigrator.java:76)
at com.atlassian.bamboo.migration.XmlMigrator$2.doInHibernate(XmlMigrator.java:190)
... 194 more
2018-03-15 23:31:21,192 ERROR [http-nio-8085-exec-1] [SetupImportDataAction] Failed to import
java.lang.Exception: Import has failed. Errors encountered while importing. This Bamboo instance may be corrupt.

診断

環境

  • Bamboo Server

診断ステップ

  • Create an export from an older Bamboo Server
    • Follow the logs under <bamboo_home>/logs/atlassian-bamboo.log and monitor the export
  • Attempt to import on a new Bamboo Server 

原因

The exception is caused due to a problem with the export file from your original source instance. The export file may not have completed properly and have missing data which is expected to finish in the database setup. 

回避策

  • Create a new export from the original server
  • Ensure the server has enough memory to complete the export 
    • This can be viewed under the application.logs on the source machine


ソリューション

  • Check your memory usage on the original bamboo server. Make increases in small increments such as an additional 256mb or 512mb to the JVM settings in your setenv.sh script. Details found here.
  • Perform a fresh export and monitor the application logs under <bamboo_home>/logs/atlassian-bamboo.log looking for a successful export job message such as;

    2018-03-18 23:09:05,006 INFO [http-nio-8085-exec-11] [XmlMigrator] Finished updating zip
    2018-03-18 23:09:05,006 INFO [http-nio-8085-exec-11] [XmlMigrator] Ensuring the the file has been unmounted
    2018-03-18 23:09:05,008 INFO [http-nio-8085-exec-11] [XmlMigrator] Unmounted /var/atlassian/application-data/bamboo/exports/<export_file_from_ui>.zip
    2018-03-18 23:09:05,008 INFO [http-nio-8085-exec-11] [XmlMigrator] Export completed. 1.293 s
  • Ensure sufficient resources are available by checking the System Information page including;
    • JVM Memory
    • Disk Capacity


最終更新日 2018 年 11 月 2 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.