I am trying to connect to a local mysql server (5.6.37) running on linux (gentoo) using mysql workbench (6.3.9). I get an "Unsupported operation provided to mysql_options()" error message and cannot connect. I am aware of the very similar question posted here, the bug report about the issue and the supposed fix.
However, none of the suggested solutions seem to apply in my case. The system variable old_passwords is not enabled (ie is set to 0) and all users are using the mysql_native_password plugin explicitly, as described in the fix. I am at a loss on what to try next. Can someone help me figure out what I've missed?
Thanks
Related
i'm getting some issues connecting to Cloud SQL from Container engine...
I followed https://cloud.google.com/sql/docs/container-engine-connect tutorial and it all seems to work, though I had to tweak a few things with the password/user stuff being sent.
However after several failed attempts of the container trying connect using Cloud SQL Proxy I am now seeing this error ER_HOST_IS_BLOCKED: Host '104.197.135.204' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
FLUSH HOSTS; doesn't seem to fix it.
and I'm unable to change the max_connect_errors value since root doesn't have the super privilege & it's not part of the MySQL flags customizable https://cloud.google.com/sql/docs/mysql-flags
any thoughts?
Got some answers through Google Cloud SQL Slack channel. It was actually related to a different database
However, I did learn that the ER_HOST_IS_BLOCKED is reset whenever a successful connection is made so this should never be an issue
I am trying to connect to MySQL database using Delphi Xe5 and fire monkey mobile application.
I am using an TSQLConnection to connect to the database but i get an error DBX Error: Driver could not be properly initialized. Client library may be missing, not installed properly, of the wrong version, or the driver may be missing from the system path.
I have read the below articles of which none had a solution that worked.
Articles:
DBX Error: Driver could not be properly initialised
http://wiltonsoftware.com/posts/view/getting-embarcadero-dbexpress-mysql-working-dbx-error-driver-not-initialized
None of their solutions seem to work, i use delphi xe5 on Windows 64x.
I have tried downloading the zip file libmysql.dll and coppied into the following paths mentioned but to no avail.
C:\Users\Public\Documents\RAD Studio\12.0\Bpl
C:\Program Files (x86)\Embarcadero\RAD Studio\12.0\bin
Can anybody please assist me in understanding why i am not able to connect to my MySQL database?
Your error message
DBX Error: Driver could not be properly initialized. Client library may be missing,
not installed properly, of the wrong version, or the driver may be missing from the
system path.
is the standard generic one from DBX and just seems to mean "something went wrong somewhere". Error-reporting doesn't seem to be DBX's strong point; a couple of times recently I've had that error when the problem turned out to be quite different than it might lead you to expect. What's annoying about it is that I only found out because I happened to have "Break on exception" turned on in the IDE and could see that the initial exception came with quite different and more revealing info, but the DBX driver seems to re-raise with that text entirely replaced by its generic, info-free version, at least in the circumstances I ran into.
AS you've subsequently found out, a FireDAC connection may succeed in connecting where a DBX one fails, and even where it fails, its error messages are more specific than DBX's. It's a shame because I find FD more fidly to set up (like I always forget its SqlWait component and it doesn't tell me that I have until r/time). So, I'm not suggesting anyone should switch to FireDAC if they've already got DBX working on a given database, just that FD can be a useful diagnostic tool.
I got problem (#2006 Mysql server gone away) with mysql while connecting and performing some operations through web browser.
Operation Listed below:
When Executing big procedure
Importing database dump
When Access some particular tables It immediately throws "Server gone away".
Refer this question for Scenarios: Record Not Inserted - #2006 Mysql server gone away
Note : The above operations are works fine when I perform through terminal.
I tried some configuration as googing stated. That is set wait_timeout, max_allowed_packet. I checked for the bin_log but it is not available.
But the issues will not rectified.
What is the problem & How can I figure out & fix the issue?
what is the different between access phpmyadmin mysql server from web browser and terminal?
Where I can find the mysql server log file?
Note: If you know about any one of the above questions. Please post here. It would be helpful to trace.
Please help me to figure this out..
Thanks in advance...
Basically nothing except phpMyAdmin is limited by PHP's timeout and resource limits (limits to keep a runaway script from bogging down your entire machine for all eternity; see the docs for details of those values. In some cases, you might be authenticating through a different user account (for instance, root#localhost and root#127.0.0.1 aren't the same user), but as long as you're using a user with the same permissions the differences are minimal.
You can read more about logs in the MySQL manual, note that "By default, no logs are enabled (except the error log on Windows)".
Below are answer for question
From my research the problem is that browser have some limit to disconnect the connection i.e timeout connection. So that the above problem raised.
To resolve this problem
Go to /opt/lampp/phpmyadmin and open config.inc.php
add the command $cfg['ExecTimeLimit'] = 0;
Restart the xamp server. Now you can perform any operations.
`
2. Web client is differ from terminal because Terminal client will not getting timeout. Terminal client maintain the connection till the progress completed. I recommenced to use command prompt to import/export/run process by safe way.
Basically phpmyadmin will not have any log file. If you wanna see warnings and error you should configure the log file.
Configuration steps:
Go to /opt/lampp/etc/my.cnf
Add log_bin = /opt/lampp/var/mysql/filename.log
Restart the xamp server. You can get the log information.
The yii requirements page says PDO extension + the mysql driver works, phpinfo() says that PDO and the MySQL driver is installed, I have configured the 'db' component in the main config file for my project generated with yiic webapp, checked and double checked that the settings are correct (and yes, I am using mysql).
I have made a new migration script in /[mywebapp]/protected/migrations and now I'm trying to run the ./protected/yiic migrate command, but i just get an exception:
exception 'CDbException' with message 'CDbConnection failed to open the DB connection: could not find driver'
I have no idea what is wrong. I have been googling for 2 hours now and i find a lot of other users experiencing the same problems, but usually they are missing the drivers or something obvious. Is there anything i'm completely overlooking?
Despite the real answer being in the comments for this question, I am answering it here so that it appears as an answer. Yiic.php migrate uses the configuration stored in console.php. You need to set your database connection in there to use yiic.
I have MySQL database hosted on server. I want to create WCF web service of that database. Actually I want to comsume WCF service in Windows Store App. I am following these articles.
Using an Entity Framework Entity as a Windows Forms Data Source
Making a Connection
But I am getting error Authentication with old password no longer supported, use 4.1 style passwords. Then searched Stack Overflow and got this solution, but it is also not working for me.
Please guide me to solve this issue.
PS : Please don't down vote this question, I have googled and searched in Stack Overflow but didn't get solution :(
UPDATE 1
I have applied command via phpMyAdmin in SQL query textbox. I also followed this Mysql password hashing method old vs new, but getting same error that "you have no SUPER privilege."
I have not managed to solve the problem as the others who have responded, although I tried out everything that has been proposed. In the end it turned out that the server on which stood my DB is not updated phpMyAdmin since version 3.5.5, and is currently being used everywhere version 4.1.14 and it is a problem. The solution is to update your host phpMyAdmin or your own mySQL back to an earlier version in order to continue working on remote DB. You may need this knowledge in order to solve some doubts that have arisen. :)