271890 - constant timeouts when backing up MySQL DB

Status: RESOLVED EXPIRED

(Toolkit :: Downloads API, defect)

Description

[ACIDSTEALTH]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Whenever I attempt to backup the MySQL databse of my website (abhnation.com), I
get constant timeouts. I select all tables to be backed up and it loads for
about 2 minutes then just does one of 2 things:

1. usually it just times out and does nothing

2. after loading for about 2 minutes it will open a dialuge box to save the
sql.gz file to my computer, so I select a location and save it, but the file is
0KB in size, and the actual DB is about 80-90mb.

Solutions I tried:

1. I upgraded from Firefox .8 to 1.0, that didn't accomplish anything.

2. I tried rebooting Firefox, then my system, and I also rebooted my router and
DSL modem. That accomplished nothing.
3. I had a friend upload the DB to another location and attempted to retrieve it
from the other location, that also failed.
4. I tried backing up the DB using alternative methods.
-A) I tried using the MySQL Backup tool built into IPB 2.0
-B) I tried backing up the DB using Mambo CMS (mamboserver.com)
-C) I tried backing up the DB using PHPmyAdmin
-D) I tried backing up the DB using a 3rd party script (invisionize.com) which I
modified
-E) I tried using a Python script (.py) to back up the database

All of the above failed, so I resorted to using Internet Explorer (6.0) to try
and back up the script, all of the above methods failed in IE as well as Mozilla
1.6.

I also have problems when trying to qeuery the DB using all of the above
methods, I get the same timeout problems in all 3 browsers, althoughthe problem
is most common in Firefox. I was able to successfully qeuery the DB in IE6, but
not in Firefox 1.0.

This is a criticalerror for me because I need to be able to backup the DB every
24 hours and I can't do that now.

Reproducible: Always
Steps to Reproduce:
1. Open a tool that can handle MySQL backups (phpmyadmin, MySQL Backup tool in
IPB 2, MamboServer, cpanel, etc)
2. select the proper compression settings and tables to back up
3. submit your qeuery to the server

Actual Results:  
qeuery fails, resulting in a timeout or a 0KB file download.

Expected Results:  
opened a dialouge box to save the target as, than saved the backup of the MySQL
DB to the designated location on the computer.

I am not using any special themes or 3rd Party plugins other than Javascript.

Comment 1

[Paul van Schayck]

Doing this kind of queries on a server causes a very high server load and can
make connections time out. 
This problem has probably to do with the server and bad luck/timing.

Can you try to increase the network.http.keep-alive.timeout option in
about:config. And retry at lower server load times (night, very early morning).

Comment 2

[ACIDSTEALTH]

It can't be the server because Aside from the mysql timeouts and the other bug
report I filed, there is no problems, and the server is lighting fast. Although
I usually do back up the DB late at night when no one is online, and the server
doesn't have a high load since there isn't alot of other stuff on the server.

It either is an error with Firefox or a local problem, because my friend and
co-admin of the site can backup the DB just fine even during prime time traffic
time for the server (6-9pm). :\

Comment 3

[Paul van Schayck]

Have you tried changing this option:
network.http.keep-alive.timeout

And you can say: 10/10 times failes with Firefox. 5/10 times failes with IE.

Comment 4

[ACIDSTEALTH]

(In reply to comment #3)
> Have you tried changing this option:
> network.http.keep-alive.timeout
> 
> And you can say: 10/10 times failes with Firefox. 5/10 times failes with IE.

I'll have to configure that option and see if anything happens.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.