Unable to Manage MySQL (connection has timed out)

I

intelliot

Verified User
Joined
Jul 29, 2004
Messages
41
After clicking MySQL Management, I see:

Your connection has timed out

Details

Either your request was invalid or the program hasn't completed your request.
Please notify the server admin
Click to expand...

Any ideas?
 
Are you the administrator of the server? If not, contact your hosting provided.
Otherwise, is MySQL responding to requests from other websites or from the command line in a timely matter?
Have you tried restarting MySQL?
When did this stop working and what (if any) were the last actions that were made to the server before it stopped working?

What Operating System and version of MySQL are you using?
 
I've got the same problem... Most often I get this error, but sometimes I do get past to manage databases. I have no problems accessing the databases in applications and speed is good.

One of my 7 DB's has grown to ~300Mb, the rest is below 1Mb each.

No actions has been taken before this occured, it's a rather new box running on FreeBSD 4.11 with MySQL 4.1.14 and I do have admin access

Edit: Load Averages 0.05 0.10 0.04
 
Last edited:
I've had a ticket with my support (Servstra) who just informed me:

We had a detailed investigation on your issue. Unfortunately we were unable to trace out the root cause since mysql is running fine in server and the timeout occurs only when accessed through DA. We then contacted Direct Admin support in this regard. They updated us that this is actually a bug in the version of DA installed. A fix would be released for this soon.
Click to expand...
 
They updated us that this is actually a bug in the version of DA installed. A fix would be released for this soon.
Click to expand...
I don't recall finding/fixing anything with mysql. I'm not sure if they're making that up, or misinterpreted my findings (unless I'm missing something). I do remember looking at one box, but was not able to solve the problem.

What I found was that when you restart mysql, the second it shuts down, the request made through DA worked fine, and the databases show up. Also, once you're viewing the db though DA, it works fine.

This would imply that only the
Code: 
mysql_list_dbs(&connection, "[b]username[/b]\_%");
function is failing. Exactly why that is, I cannot say. I believe that the function just gets a list of DB's from doing checking the mysql data directory (essentially an "ls" through mysql), but why exactly it's not returning until mysql is shutting down, I don't know, doesn't really make much sense.

John
 
Will ask support about this. Otherwise I'll have to wait for a long time for bugfix I guess...

The problem is really strange...
 
News from Servstra again, hopefully this time it's for real...

We contacted the direct admin team and they have reported that they will install the new patch in the new version of DA that will come out.
Click to expand...

Not sure if they mean 1.275 or ver 2.0... ;)
 
Edit your /usr/local/directadmin/conf/directadmin.conf

add:

show_db_usage=500

save/exit.
Restart directadmin:

/sbin/service directadmin restart

John
 
You must log in or register to reply here.
Back
Top