Cannot dump database

[DaliborPan]

Hi, I'm trying to dump my database using CLI pscale database dump [name] [branch]. I was able to do that on 5th September. Now I'm getting errors

⠸ Dumping tables ...2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
⠼ Dumping tables ...2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
⠴ Dumping tables ...2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
⠦ Dumping tables ...2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:15+02:00	error	error dumping table	{"error": "EOF"}
⠧ Dumping tables ...2023-09-14T10:41:16+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:16+02:00	error	error dumping table	{"error": "write tcp 127.0.0.1:53455->127.0.0.1:53418: use of closed network connection"}
2023-09-14T10:41:16+02:00	error	error dumping table	{"error": "EOF"}
2023-09-14T10:41:16+02:00	error	error dumping table	{"error": "write tcp 127.0.0.1:53457->127.0.0.1:53418: use of closed network connection"}
2023-09-14T10:41:16+02:00	error	error dumping table	{"error": "write tcp 127.0.0.1:53459->127.0.0.1:53418: use of closed network connection"}
⠇ Dumping tables ...2023-09-14T10:41:16+02:00	error	error dumping table	{"error": "write tcp 127.0.0.1:53461->127.0.0.1:53418: use of closed network connection"}
Dumping is finished! (elapsed time: 4.884509083s)

Anyone experiencing the same?

[orware]

Hello @DaliborPan,

You may try passing in the --threads optional parameter here and dropping the number down in order to help avoid the EOF error here if this is still occurring for you.

By default that parameter is defaulting to 16 threads when using the pscale database dump command so you can try dropping it to 4 or 8 and see how the behavior is in those cases.

Are you on one of our Hobby plans by any chance or have added a significant amount of data in to your database? Those may be factors as to why it may have been working previously on September 5th but is now running into an issue compared to that earlier attempt.

[DaliborPan]

Hello @orware,

thank you for your reply! Lowering number of threads doesn't work for me.

I'm on hobby plan, latest version of planetscale cli. For testing purpose, I've created fresh new database, added only one table with a single column, and it still doesn't work..

I also found an issue created few days ago, so I thought that more people might be experiencing the same.

[orware]

Hello @DaliborPan and @pjfancher,

We'll likely follow-up in the official issue you linked to above but we are currently investigating this further on our end so that's the quick update I can share!

I was able to recreate the issue in a new Hobby plan database so that helps us to get an idea for where the issue might be so our team will be reviewing those details to identify any fixes that may be required on our end.

[pjfancher]

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. The --threads parameter does not work.

[mscoutermarsh]

Update: this has been fixed!

[Qavi-Nizamani]

It is not fixed yet

⠸ Dumping tables ...2023-10-12T13:44:26+05:00 error error dumping table {"error": "EOF"} Dumping is finished! (elapsed time: 15m41.672388558s)

[orware]

Hello @Qavi-Nizamani,

Based on it taking close to 16 minutes before the EOF error was triggered, the issue in your case is likely a little different and may be based on your current data size and a few other factors.

You can try dropping the number of threads down from the default of 16 using the optional --threads parameter as an initial test but if you continue to have difficulty please send in a quick ticket over at https://support.planetscale.com/ and we can take a closer look at the details for your database and figure out a solution.