Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Progress Endpoint Never Provides Filename #16

Open
genio opened this issue Dec 12, 2017 · 5 comments
Open

Progress Endpoint Never Provides Filename #16

genio opened this issue Dec 12, 2017 · 5 comments

Comments

@genio
Copy link

genio commented Dec 12, 2017

{
    "status": "Success",
    "progress": 100,
    "description": "Compressing data & attachments",
    "result": "{\"mediaFileId\":null}",
    "startTime": 1513004884339
}

So, the actual backup file can never be found.

@dzschille
Copy link
Collaborator

@genio i am using this script for weekly updates of Jira and Confluence, it is working fine here.
Do you can share some more details? Are you using Atlassian cloud or self hosting?

@cchappel
Copy link

Probably Atlassian cloud. We are having the same issue.

{"status":"Success","progress":100,"description":"Compressing data & attachments","result":"{\"mediaFileId\":null}","startTime":1516647659660}

@dzschille
Copy link
Collaborator

Since mid of December my backups are also failing. But only for Jira, the Confluence backup is still working. There seems to be working scripts over here: https://jira.atlassian.com/browse/JRACLOUD-67169
We will check that and fix this script.

@mattock
Copy link
Owner

mattock commented Jan 23, 2018

@dzschille it seems I have the same symptoms. I will test your fix when it is ready.

@cchappel
Copy link

This is the reply we got from Atlassian support.

It did show that in our case, a single line in our backup script was off, but we made adjustments late last year for the runbackup URL as well, so please pay attention to the changes indicated in this ticket. No idea if we're fixed yet, (need to wait until tomorrow to try again) but this seems to be the right answer.

It seems you are affected by an existing bug which you can track here: JRACLOUD-67169: JIRA backup script returns 404 in the new infrastructure.

I've also included a link to this bug ticket so that they are aware of the support ticket. Please do find the workaround instruction in the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants