Remote access fails
I have two instances of mysql running, one on my local machine and one on my freenas server. Heidi connects to the local instance just fine but connecting to freenas returns the following:
SQL Error (2013):Lost connection to MySQL server at 'reading initial communication packet', system error: 0
I can connect to the freenas instance via ssh with several clients such as kitty or putty and even running plink in a command window with the following parameters:
plink -P 22 -l <freenas user> -pw <freenas user password> <freenas ip>
Once the freenas prompt appears I can connect to mysql just fine with no restrictions.
My Heidi connection parameters are as follows:
In the Settings tab:
Network type: SSH tunnel
Hostname/IP: <freenas ip>
User: <mysql user>
Password: <mysql user password>
Compressed client/server protocol is left unchecked
In the SSH tunnel tab:
plik location is correct
SSH host + port: <freenas IP address> / 22
Username: <freenas username>
Password: <freenas username password>
Private key file is left empty
Local port: 3306
I've tried putting the mysql user name and password in the SSH tab and the freenas user name and password in the Settings tab but then I get the following error:
SQL Error (1045): Access denied for user '<mysql user>'@'localhost'(using password: YES)
And yet all parameters are correct, at least it would appear so since I can connect to mysql with those same parameters outside Heidi.
My Heidi version is 126.96.36.19931. Any ideas?
I have the feeling there's some initial config value that's interfering since logging on to freenas via ssh allows me to access mysql. I'll be researching the location of this elusive config file but in the meantime any other ideas will be very welcome.
Cheers and keep up the good work.
Re my.cnf: I created one out the my-large.cnf I found in the installation directory and specified port 3307. I also changed the port in the Heidi connection parameters to 3307. The mysql.sock file is where it's supposed to be. Unfortunately error 2013 is still the result.
Further, if you have your local MySQL now running on port 3307, try reverting that and only use 3307 as the local port in Heidi's SSH settings. But I guess you already tried this combination.
Ok, if you after all are sure your SSH settings are right, you should now get again
Lost connection to MySQL server at 'reading initial communication packet'
No real new ideas here currently, just some URLs for you:
Ah, and I read somewhere about error 2013 that this can be due to being low on disk size - MySQL needs some space for its key buffer and other things, can even be some gigabytes, so make sure your harddrive has a minimum of let's say 10gb.
Still working on this and have some new info. I'm now using an Ubuntu 10.10 server instead of the old FreeNas server. I can now access the server database with Heidi but only if I open an SSH session from the client computer and then start Heidi. Otherwise I get the same error as before. Go figure. Any ideas?
create user '<username>'@'%' identified by '<password>';
grant all on *.* to '<username>'@'%' identified by '<password>';
Then in Heidi's session manager my server session is as follows:
Network type: TCP/IP
Hostname/IP:<server IP address>
And that's it. Now when I start Heidi both server instances are started and I can jump between them seamlessly. Fantastic!
Please login to leave a reply, or register at first.