forums › forums › SQLyog › Using SQLyog › Error 2013 Lost Connection To Mysql
- This topic is empty.
-
AuthorPosts
-
-
January 28, 2010 at 4:25 am #30383
West Dude
MemberSorry I didn't see the previous reply on the same problem. So yes I do have ssh forwarding enabled but still having the same issue. Strange. Any suggestion?
-
January 28, 2010 at 7:44 pm #30384
West Dude
Member'West wrote on '27:Sorry I didn't see the previous reply on the same problem. So yes I do have ssh forwarding enabled but still having the same issue. Strange. Any suggestion?
My suspicion is with the mysql version sqlyog supported. I try to connect to mysql version 5.1.37-1 for FC11 with sqlyog, no problem. But when I tried connecting to mysql version 5.1.42-2 with sqlyoq, the 2013 error show up. This regardless whether my machine in on the server somewhere connecting via internet or the server is inside our LAN. Any comment? Please help?
-
January 29, 2010 at 6:18 am #30385
peterlaursen
ParticipantNo clue. Are you perfectly sure?
The server “5.1.42-2” is probably one installed from Fedora repositories (with 'yum') I guess. I believe there is no such official MySQL version. Could you try official MySQL builds?
A FTP link: ftp://mirrors.dotsrc.org/mysql/Downloads/MySQL-5.1/
(On Fedora and SuSE I always have used the 'glibc23' RPM builds with success. But you will probably need to have support for older C runtimes installed. I am not sure If FC11 has as default (I have not been using Fedora since version 8). If not the case the command to install those are “”yum install compat-libstdc++-33″”
-
February 2, 2010 at 4:20 am #30386
West Dude
MemberPeter you are right. The version that gives me the error is installed using the yum install. Since I assumed that fedora won't add it in their yum repository unless they have already test it and approve it. I also did a test on the centos version 5.4 with the latest version offered via yum install and the version is 5.0.77 and it works just fine. Very strange. Any other thought?
-
February 2, 2010 at 4:46 am #30387
peterlaursen
ParticipantNo idea. I don't use Linux very much and when I do it is SuSE. For me the generic 'glibc23' RPM's from dev.mysql.com have always worked fine. I always have updated MySQL after installing the distro.
-
February 4, 2010 at 12:49 am #30388
West Dude
Member'peterlaursen' wrote on '01:No idea. I don't use Linux very much and when I do it is SuSE. For me the generic 'glibc23' RPM's from dev.mysql.com have always worked fine. I always have updated MySQL after installing the distro.
I tried using the latest mysql and since I can only downloaded the community version and for some reason the mysqli are not installed and configured correctly so I'm kind of stuck now.. Either way, Thanks Peter for your help.
-
February 4, 2010 at 4:54 am #30389
peterlaursen
ParticipantI do not understand your reference to 'mysqli'. If you are referring to the PHP mysqli extension SQLyog does not depend on it.
In the beginning you wrote that connecting with SSH is a problem. What about direct connection? I think we should start figure out if this is a SSH problem or MySQL problem.
-
February 6, 2010 at 4:43 am #30390
West Dude
Member'peterlaursen' wrote on '03:I do not understand your reference to 'mysqli'. If you are referring to the PHP mysqli extension SQLyog does not depend on it.
In the beginning you wrote that connecting with SSH is a problem. What about direct connection? I think we should start figure out if this is a SSH problem or MySQL problem.
What am I saying was that when I used the latest version downloaded from mysql website, I can't get my php mysqli working properly. but when I used the official mysql version downloaded and installed via yum, I couldn't access mysql with ssh via sqlyog. but my php mysqli for the yum repository installed version work just fine. I kept getting the 2013 error from sqlyog when I tried to connect to it. Thought?
-
February 25, 2010 at 5:53 pm #30391
West Dude
MemberOk. I'm going to answer my own question then so that other people who may stumble around this same issue can resolve it faster.
somehow in my.cnf I added a line bind-address = ip address of the server which somehow cause mysql to refuse and drop the packet connection to the server because the binding address is different than how I'm going to connect to the server which is localhost.
So I changed the bind-address=localhost , restart mysql and that solved the problem.
Here is the link reference on how I figured it out.
http://forums.mysql.com/read.php?52,151255,156258#msg-156258
funny how you always solve the problem yourself after you start asking people on how to do it even though you've been banging on your head for couple of days wondering what the heck is going on. 🙂
Anyway, hope this help you all..
-
-
AuthorPosts
- You must be logged in to reply to this topic.