So essentially we created a new "root like" MySQL user and used that for the dual purposes of connecting via Adminer (the DB web UI we replaced PHPMyAdmin with at some point - perhaps v14.0?) and for remote connections. As is noted in that thread, we ended up going with option 2. You may also find this post (again by me - from while we were developing v15.0) of interest and value. Regardless, if you have a look at this StackExchange answer (by me! :) you should hopefully be able to do some investigation and work out what is going on. However, TBH I'm not really sure how that works when you upgrade? Debian generally allows you to carry forth previous config when doing a dist-upgrade, so you may well have ended up with a combo of your old config and the new.
#QUERIOUS 2 KEYGEN PASSWORD#
By default, that means that you should no longer need a password to connect to your MySQL root user (so long as you are logged in as the root Linux user). In a clean install, instead of a normal network connection, it uses a unix socket. From here on in, I'll continue to use "MySQL" as a generic term, meaning MariaDB specifically, when I refer However, by default the (at least on Debian) MariaDB uses a different connection and authentication mechanism for the root account (apparently MySQL 5.7 have also adopted this new authentication mechanism too). So whilst internally they don't work exactly the same, MariaDB is a "drop in replacement" for MySQL and you should not note any major differences. Port 3306 is open in Amazon's security settings, FWTW.Īny idead on what to do here to fix things?įirst up, it's well worth noting that In Debian 9/Stretch (the basis of v15.x), Debian switched from MySQL to MariaDB. PhpMyAdmin works, as well as SSH'ing in and entering mysql from there.
Which makes me think the server won't accept connections from the outside world. Nov 25 16:20:00 lamp sshd: pam_unix(sshd:session): session closed for user (snip) Nov 25 16:20:00 lamp sshd: Disconnected from (snip) port 54311 Nov 25 16:20:00 lamp sshd: Received disconnect from (snip) port 54311:11: disconnected by user Nov 25 16:20:00 lamp sshd: pam_unix(sshd:session): session opened for user (snip) by (uid=0) Nov 25 16:20:00 lamp sshd: Accepted publickey for (snip) from (snip) port 54311 ssh2: RSA SHA256:(snip) I did a lot of googling and tried all sorts of things, like commenting out #bind-address = 127.0.0.1 in the config file and restarting mysql, all to no avail. MySQL said: Lost connection to MySQL server at 'reading initial communication packet', system error: 0 Unable to connect to host (snip).com, or the request timed out.īe sure that the address is correct and that you have the necessary privileges, or try increasing the connection timeout (currently 10 seconds).
#QUERIOUS 2 KEYGEN PRO#
The error message that Sequel Pro kicks off is this: I looked through all my old notes and can't locate what, if anything, I did to make it accessible in 14.
#QUERIOUS 2 KEYGEN MAC#
All went fine except for one minor issue, I can't connect to the database server using local GUI tools (Sequel Pro on the Mac for example) as I could when I was using version 14. Now that v16 is on the horizon I finally got off my butt and migrated my v14 LAMP machine to v15.
0 kommentar(er)
