There are many posts here and all over the web about getting the message:
Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)
when trying to connect a a MySQL database. In my case, it's coming from MySQLWorkbench version 6.3 newly installed on a almost as newly install Ubuntu 15.10 system.
The advice is always to update the password on the database to use the new authentication.
However, that is not my problem, and that's not what the message says. It says that the OLD authentication is being used when the database wants the NEW authentication.
This version of MySQLWorkbench has a checkbox that tells it to use the OLD authentication, which is unchecked, but, from the message, it appears to be using the OLD authentication all the time.
I can connect to the database easily from version 5.2 of MySQLWorkbench running on Mac OS X.
I tried installing an older version of MySQLWorkbench on my Ubuntu system, but there were numerous errors with the package, which is intended for an earlier version of Ubuntu.
Any ideas about how I can force MySQLWorkbench to use the NEW authentication? I tried setting:
useLegacyAuth=0
but that did nothing.
OK, got the answer. The hosting outfit (Siteground) sets up MySQL passwords to work with EITHER the legacy or the new protocol. I don't know if this is homegrown, some sort of plugin that's generally available, or a standard MySQL feature. With this option, MySQLWorkbench fails to connect and erroneously reports the problem as the server not supporting the old protocol. Probably it's just confused by the error response which its programmers didn't anticipate.
Siteground very quickly set my password to use the new authentication ONLY upon my request, and then MySQLWorkbench connected with no problem.
Related
Good day. I just finished upgrading my AWS RDS database engine from 9.6.22 to 10.17. I used these steps to make the upgrade using the AWS Console:
Create snapshot of target database to upgrade
Restore snapshot
Upgrade the restored snapshot's (which is now a new instance) DB Engine version.
After I did all of this, everything seems fine but when I access the database, this warning message appears
WARNING: psql major version 9.6, server major version 10.
Some psql features might not work.
I did not continue on my testing because I want to know what is the meaning of this first. Because I am fairly new in AWS as a whole. Thanks!
The meaning is that just because you are connecting to an upgraded database on some machine run by Amazon, the PostgreSQL installation on your local machine was not magically updated. psql from version 9.6 doesn't know what metadata tables were changed in v10, what features were removed and so on.
It would be a good idea to install a more recent version of PostgreSQL on your machine. By the way, upgrading to v10 was not the smartest move, as that version will go out of support in less than a year. You should upgrade to the latest version that your service provider offers.
The client program psql you are using to connect to the database is from an older version than the database it is connecting to. Some of the introspection features might not work. For example, psql from 9.6 won't know how to do tab completion for commands that were added to the server after 9.6.
This is generally not a major problem for psql (unless the server wants to use SCRAM authentication), but for optimal experience it would be good to install a newer client. Other tools like pg_dimp might not with at all against a server newer than they are.
How do I connect a postgresql to a web2py application? The web2py documetation says that I can connect it using the command db = DAL("postgres://myuser:mypassword#localhost:5432/mydb") but upon doing it, it produces an error saying RuntimeError: No driver of supported ones ('psycopg2',) is available.
I already installed psycopg2 but I don't know how to use it in the web2py app. There are not a lot of resources out there about this so I'm having a lot of trouble.
Your DAL code is correct. I think psycopg2 is not installed correctly.
Maybe you want to install psycopg2-binary.
This question may sound absurd as I am totally new to XMPP & Openfire. I have a setup of Openfire 4.2.3 in Ubuntu 18.0.4 LTS that being used in my android chat app. During testing I received a Timeout error. While investigating the issue I found the solution rely on the XMPP updated version, check this link for more info.
Well I tried my best to find out my XMPP version and how to update it. Unfortunately I didn't find anything on it. So, I have two obvious questions here:
How to check XMPP version my Openfire is running on?
How to update XMPP version on my existing Openfire setup?
Since you are able to use the web-interface, just log in. On the start page look for the server properties. Theres the version.
For upgrading follow these steps:
To stop openfire on ubuntu: /etc/init.d/openfire stop;
Backup copy of the openfire installation directory: /usr/share/openfire;
Backup Openfire Base in Postgres: If you use the pgAdmin application, right-click on openfire base and click “Backup”. To run backup, it can be with own postgres as user. I recommend tar format, and encoding “SQL_ASCII”.
To install the new version: you can actually use the “dpkg -i” command, you will be asked if you want to keep your current version (choose this one), but you will still upgrade (option N or O - keep your currently -installed version).
On the java, has a statement informing that from version 4.3 will be necessary Java 8 installed.
Source: https://discourse.igniterealtime.org/t/update-openfire-4-1-6-to-4-2-1-in-ubuntu-server/80336
And if you really meant the "XMPP-Version". There is not really such a thing. XMPP is implemented to a different extend on different server-providers. Some have more extensions, some less.
To see which ones you have, refer to the wikipedia site:
https://en.wikipedia.org/wiki/Comparison_of_XMPP_server_software
Recently I installed PostgreSQL 10.4, but it was losing connection all the time. I uninstalled it, removed the data folder and installed version 9.6, which didn't help, so I uninstalled it as well and removed the data folder. I installed 10.4 again hoping that it will work well this time.
When I opened pgAdmin it showed as if version 9.6 was still installed apart form the 10.4 (which should be there). I tried creating a user in it (to see if it really works) and it created it successfully, but after further investigation I realized that it created the same user in the 10.4 installation. It must have been the same installation, but pgAdmin saw it as two separate ones. I deleted both installations form pgAdmin and reinstalled version 10.4.
Everything works fine now, but I still wanted to ask what might have caused this issue? Can it cause problems for my existing db in the future?
It's not "PostgreSQL" that remembered the installation. It's pgAdmin where you simply didn't delete the configured connection. Connection information is something specific to the SQL client, not the database server.
The existing connection definition uses the same hostname, port and apparently password that was valid for a running 9.6 server or the new Postgres 10 server. The name of that "server" is something that is specified in pgAdmin and has nothing to do with the actual Postgres installation. You could have named the "9.6 Server" connection "Connect to some nice DBMS" instead.
That information is not stored together with the PostgreSQL installation, but in your user profile.
I'm trying to reach a Postgresql base via ssl from the builtin database browser in IntelliJ IDEA Ultimate.
In datasource properties I have added the same key and cert pem-files that work fine with psql and pgadmin, but on "Test Connection" I just get
[08006] SSL error: No X509TrustManager implementation available
Updated in response to Andrey's comment:
If I add the local root certificate (which neither psql or pgadmin needed) in the CA file setting, the error changes to
[08006] SSL error: No trusting managers found for ECDHE_RSA
What am I missing?
Can anyone confirm a working db-connection using:
IntelliJ IDEA Ultimate Edition 2019.2 or later
Ssl
PostgreSQL 12.x or later
I had the same problem. I updated my intelliJ to latest version (IntelliJ IDEA 2021.3.3 - ultimate). Then it started working.