Getting `error dumping table` error while dumping database using pscale cli
harshitsaini opened this issue · 5 comments
I'm trying to create a database dump of dev branch but getting error saying error dumping table
Shell Command
pscale database dump [database_name] dev --output mysql_dumps/dev/$(date +"%Y-%m-%d_%H-%M-%S") --service-token [redacted] --service-token-id [redacted] --org [redacted] --debugDebug log
⠹ Dumping tables ...2023-09-10T18:39:25+05:30 error error dumping table {"error": "EOF"}
2023-09-10T18:39:25+05:30 info dumping table database schema... {"database": "redacted", "table": "redacted"}
2023-09-10T18:39:25+05:30 info dumping table ... {"database": "redacted", "table": "redacted", "thread_conn_id": 6}
⠴ Dumping tables ...2023-09-10T18:39:26+05:30 error error dumping table {"error": "EOF"}
2023-09-10T18:39:26+05:30 info dumping all done {"elapsed_time": "25.971499491s", "allrows": 0, "allbytes": 0, "rate_mb_seconds": 0}
Dumping is finished! (elapsed time: 45.007105241s)Table schemas and metadata are downloaded successfully but table data download is failing.
I'm having the same problem
⠹ Dumping tables ...2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
⠸ Dumping tables ...2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
⠼ Dumping tables ...2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
⠴ Dumping tables ...2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
⠦ Dumping tables ...2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "write tcp 127.0.0.1:52420->127.0.0.1:52384: use of closed network connection"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "EOF"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "write tcp 127.0.0.1:52422->127.0.0.1:52384: use of closed network connection"}
⠧ Dumping tables ...2023-09-14T10:20:06+02:00 error error dumping table {"error": "write tcp 127.0.0.1:52424->127.0.0.1:52384: use of closed network connection"}
2023-09-14T10:20:06+02:00 error error dumping table {"error": "write tcp 127.0.0.1:52426->127.0.0.1:52384: use of closed network connection"}
Dumping is finished! (elapsed time: 4.805909542s)
I'm having the exact same problem. I'm using pscale database dump and the command was working fine yesterday. No big changes to the database. The database is 146MB.
Hello @harshitsaini, @DaliborPan, and @pjfancher,
We're still investigating the underlying cause that is currently affecting the pscale database dump command for new Hobby plan databases, which I believe is the case for all 3 of you currently.
We do have a temporary workaround that can be utilized if needed for the time being, assuming that your tables all have less than 100K rows and you already have the MySQL Client utilities installed.
You would first use the pscale connect command to connect to your branch, which should provide accessibility over your localhost / 127.0.0.1 address, typically on port 3306 if you do not have anything else using that port.
You may then run the command below, and if needed adjust the port value and backup filename, and you should be able to generate a quick backup for a small PlanetScale database:
> mysqldump -A --host=127.0.0.1 -P 3306 > planetscale_backup.sql
Once we have more information on the underlying cause/fix we'll continue to keep this issue updated so we appreciate your patience in the meanwhile!
Hello @harshitsaini, @DaliborPan, and @pjfancher,
An underlying fix on our end outside of the CLI code base has gone out that should resolve the issue with using pscale database dump so you should be able to use it again now!
If you experience any further issues though please let us know!