-
Should I keep PuTTY's connection alive by doing something like dir from time to time?
-
Ok, the popup window says:
PuTTY Fatal Error
Network error: Software caused connection abort.
I started the import at 10:58 and it timed out at 11:08, so it seems to run for 10 minutes, then quits.
-
I'll try another import, this time I've used connect_timeout=9999 before using the mysql command. Not sure if this is the proper syntax, but I didn't get a bad command warning.
-
Still no luck. Same error after 10 minutes. Any suggestions?
-
It was not the SQL error message. Putty SSH client gave the timout error message. I would recommend you to create a screen and run the command in screen. You can create a screen using the following command:
Code:
screen -S SCREEN_NAME
where SCREEN_NAME is a name of your screen
Then run the command to import your SQL file:
Code:
mysql DB_NAME < DB_NAME.sql
Close the screen with help of Ctrl+A, then Ctrl+D. When the command is run in screen it will never be killed even if you close the SSH window.
You can open a screen again with help of the following command:
Code:
screen -r SCREEN_NAME
-
Ok, I have it going again. We'll see in about 10 minutes or so.
-
Didn't work. Same message after 10 minutes again.
-
Well, I take that back - it's still going. Much slower than the first few tries, but still growing the DB. I will report in a little while.
-
It's done! But it took forever.
2.5 hours for 130MB.
Is there a reason why the performance was so slow?
-
Call your ISP and ask if they require keepalive connections for SSH.
I had issues using Adelphia cable when I subscribed to their service and I had to specifically enable keepalive in putty.
In my putty version it is located at Connection > Seconds Between Keepalives.
Basically your SSH client will send a packet to the server and back. I don't know why some ISP require this, it is a waste of time and packets, but try it out and it might be your fix.