-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
settings.export_status_failed When trying to export SQL & Json backups #5937
Comments
Same issue |
Hello. |
+1 |
Unfortunately nothing interesting :-(
UPDATE The file gets created! MariaDB [monica]> SELECT * FROM export_jobs;
+----+------+------------+---------+------+--------+----------+-------------------------------------------------------+---------------------+---------------------+---------------------+---------------------+
| id | uuid | account_id | user_id | type | status | location | filename | started_at | ended_at | created_at | updated_at |
+----+------+------------+---------+------+--------+----------+-------------------------------------------------------+---------------------+---------------------+---------------------+---------------------+
| 3 | NULL | 1 | 1 | sql | failed | public | exports/rRMr1jf4gBmkk0jxa9Ki5TftlXNIU9VbSBuPUtQQ.sql | 2022-01-29 23:19:04 | 2022-01-29 23:19:05 | 2022-01-29 23:19:04 | 2022-01-29 23:19:35 |
| 4 | NULL | 1 | 1 | sql | failed | public | exports/IAbRclkOqti78HkamPsKKOz8eu6zQVkCRTXOd1Cp.sql | 2022-01-29 23:21:24 | 2022-01-29 23:21:24 | 2022-01-29 23:21:24 | 2022-01-29 23:21:54 |
| 5 | NULL | 1 | 1 | json | failed | public | exports/E4BOInWPGvCCIKfndXDdyeOfLyROXuITVM55RyLv.json | 2022-01-29 23:24:09 | 2022-01-29 23:24:18 | 2022-01-29 23:24:09 | 2022-01-29 23:24:48 |
| 6 | NULL | 1 | 1 | json | failed | public | exports/CI8bAdX2KDjrLjF7dTBsRvQ2Y8KxmBDo5lShEOcS.json | 2022-02-06 10:35:31 | 2022-02-06 10:35:40 | 2022-02-06 10:35:31 | 2022-02-06 10:35:40 |
| 7 | NULL | 1 | 1 | json | failed | public | exports/UQ82hfd4iPcUX0izSytoE16MDYmE2XdyFHnUFedk.json | 2022-02-06 10:49:36 | 2022-02-06 10:49:44 | 2022-02-06 10:49:36 | 2022-02-06 10:49:44 |
+----+------+------------+---------+------+--------+----------+-------------------------------------------------------+---------------------+---------------------+---------------------+---------------------+
5 rows in set (0.000 sec) root@monica-6497cd64dc-x64pt:/var/www/html# ls -l /var/www/html/storage/app/public/exports/UQ82hfd4iPcUX0izSytoE16MDYmE2XdyFHnUFedk.json
-rw-r--r-- 1 www-data www-data 9029645 Feb 6 11:49 /var/www/html/storage/app/public/exports/UQ82hfd4iPcUX0izSytoE16MDYmE2XdyFHnUFedk.json |
@asbiin Thanks! |
This seems to still be an issue. For those of you wanting to still have access to your exports, follow these steps:
NOTE: this copies ALL exports to your local machine, not just the most recent ones. Also, you MUST verify that the resulting files actually contain your valid data before deleting anything in the container |
I can confirm this issue is still ongoing and @DesignsWithDavid workaround is also working for the time being |
Hi! Same issue here running 'latest' Monica 3.7.0 on an 8-raspberry-cluster-docker-swarm (actually with MariaDB, but same issue with MySQL). But opening the commandline on the app container and navigating to /var/www/html/storage/app/public/exports/ indeed shows the files being created. That's not the best user experience, but a least a way to get and backup the exports. |
The workaround @DesignsWithDavid mentioned was working up until a few days ago for me. JSON exports are now no longer being created inside the docker container after hitting export. Not sure what changed, it was working one day with the same dataset, then the next day it just randomly stopped working for me. SQL exports still work, for now. |
Describe the bug
I've recently imported a database from a v3.5.0 docker instance into a fresh 3.6.1 docker setup. After looking to make an export of the 3.6.1 database for backup purposes, I receive the following error: settings.export_status_failed (Also seen in the screenshot)
Screenshots
Which version are you using:
A self-hosted Ubuntu 20.04 full VM running the latest docker and docker-compose. I've used phpmyadmin to import the 3.5 database into the 3.6.1 database.
My docker-compose file:
The text was updated successfully, but these errors were encountered: