Bamboo Export / Import failing with invalid null char

[Alex Hall]

I'm trying to preform an export but didn't realize the export had failed until I tried to import into a fresh install same version (but linux server not windows, same Bamboo version)

I think I narrowed the issue to the export failing at:

E:\Atlassian\bamboo5\exports\export_atlassianbamboo_5920_20180908.zip\db-export\loginInfos.xml
2018-09-08 19:14:22,687 INFO [http-nio-443-exec-17] [XmlMigrator] Exporting with: com.atlassian.bamboo.migration.stream.LoginInformationMapper
2018-09-08 19:14:23,594 INFO [http-nio-443-exec-17] [XmlMigrator] Ensuring the the file has been unmounted
2018-09-08 19:14:23,594 INFO [http-nio-443-exec-17] [XmlMigrator] Unmounted E:\Atlassian\bamboo5\exports\export_atlassianbamboo_5920_20180908.zip
2018-09-08 19:14:23,641 ERROR [http-nio-443-exec-17] [Export] com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output

.....

Any ideas, I'd be happy to provide more info if needed.

[Daniel Santos · Accepted solution]

Hey Alex,

It took me a while to realise that the class com.atlassian.bamboo.migration.stream.LoginInformationMapper does not exist in bamboo versions after 5.9, this happens to be the same for the loginInfos.xml file (at least for Bamboo 6.6.2).

Your export seems to have failed to write values to the loginInfos.xml file due to a special char saved in your bamboo db. The information who populates this file is stored in the AUTH_ATTEMPT_INFO table. It just registers details about failed user login attempts and can be cleaned.

Suggested steps to overcome this issue:

1. Create a database backup of your Bamboo DB (using your external tool)
2. Check the values in AUTH_ATTEMPT_INFO (either fix them or remove the rows)
3. Create another export and check it succeeds without errors

I hope it helps.

Regards,
Daniel P Santos | Atlassian Support

[Alex Hall]

Thanks Daniel!

This looks to be the answer! I briefly looked at the data in AUTH_ATTEMPT_INFO, and sure enough the data looks a bit wacky. Its possible the data is from an attack or vulnerability scan.

I haven't yet had the opportunity to remove the rows from that table or preform another export. I'm confident this is solution will work!

- Alex

[Daniel Santos]

Hey Alex,

Good to know you found something there.
I hope that is the only issue with the export =]

Take care!