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

Data archive fails to export #12424

Open
MirceaKitsune opened this issue Nov 18, 2019 · 4 comments
Open

Data archive fails to export #12424

MirceaKitsune opened this issue Nov 18, 2019 · 4 comments
Labels
bug Something isn't working

Comments

@MirceaKitsune
Copy link

The process of exporting your account data to an archive sometimes fails without explanation. When I go to https://instance.social/settings/export and click the "request your archive" button, the page tells me that it's compiling my archive for roughly 10 minutes, after which I'm only shown the old archive and the button to request a new one becomes available again. I've been trying this procedure for an entire day on the instance I'm presently using, and it never manages to generate it, despite the rest of the instance working perfectly fine.

I don't know whether this might be related to the version: When I exported my last archive a week ago, I believe it was running Mastodon 2.9.7. It was upgraded to 3.0.1 this week, and now I'm getting this problem whenever I try to export. It's not a big account either, with less than 12.000 toots and no media uploaded.

@quimgil
Copy link

quimgil commented Apr 22, 2021

Several users in our instance are having the same problem, including myself -- https://red.confederac.io v3.3.0. There are a few more reports out there that are unanswered.

As an admin, I don't know where to look for more information. The /settings/export page keeps the message "Compiling your archive..." after days, even when it is clear that such thing isn't happening. Testing is more difficult because users need to wait 7 days until they can try again. I don't know where to find related logs, or a manual restart. Creating an archive from the command line seems to not be possible.

As a result, users that are migrating to other instances leave unhappy because they need to leave behind their content. We have announced the closure of our server by the end of June, and this problem with the archives is causing a lot of bittersweet feelings.

I wonder whether anyone has any advice about where to look, what to do.

@ClearlyClaire
Copy link
Contributor

You should look for errors in the sidekiq logs (journalctl -u mastodon-sidekiq)

@Thorwegian
Copy link

I am having the same issue. It only seems to affect big accounts such as mine. I have no trouble exporting less active accounts with fewer posts. I think I must have gigabytes of media attachments and it doesn't like that.

@vmstan vmstan added the bug Something isn't working label Nov 17, 2023
@CurrentBias
Copy link

I am having the same issue. It only seems to affect big accounts such as mine. I have no trouble exporting less active accounts with fewer posts. I think I must have gigabytes of media attachments and it doesn't like that.

Same here -- I have about 9k posts and am stuck at "compiling your archive"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants