Having trouble with the testlink installation. At the beginning of the installation it's giving me a warning saying:
"Failed! MySQL Database cannot be used." and after I try to install it shows me this "Checking PHP DB extensions Warning!: Your PHP installation don't have the mysql extension mysql- without it is IMPOSSIBLE to use Testlink.Failed!".
I installed Xampp before this, so I should have MySql, right? If it matters, I had to switch the Apache port numbers to 8080.
Image 1:
Image 2:
]
I faced similar issue, tried all given answers on different forums, but nothing worked for me unless I downgraded the version of Xampp to 32 bit installer version 5.6.36. Link which simply solved the problem.
As per my understanding issue is testlink [mysql] is not compatible with the latest version of PHP.
I followed this article to install but here also people faced similar issue as you can see comment section and there is no response from author on same. Rest of the article was very helpful.
I solved this issue configuring the extensions for SQL in file xampp's php.ini
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_pdo_mysql.dll
DLLs should be in the path of the xampp installation, in my case C:\xampp\php\ext\**
Click config then click PHP (php.ini) and add then following three lines
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
https://forum.testlink.org/viewtopic.php?t=2935
htis help me to fix it
Some versions of PHP are not compatible with MySQL. Try reinstalling PHP using version 5.6
Related
It seems that an SSL connection is required to use MySQL Workbench, and I don't think this is the case with previous versions.
I remember SSL connections used to be optional. After I updated it, all options are locked to require SSL.
How do I bypass this? I'm just a student and setting up SSL is out of my reach.
Screenshot:
Here is the correct solution for version +8.0.x.
When the program starts, the edited configuration files are changed again.
Therefore, you need to add useSSL=1 in advanced.
I solved this by editing the connections.xml configuration file.
Under ~/.mysql/workbench/connections.xml, I searched for the connection name and changed
<value type="int" key="useSSL">2</value>
to
<value type="int" key="useSSL">1</value>
MySQL Workbench has released 8.0.28
It solves this bug. Wow. I am happy.
In Mac OS X there is this issue.
My version is mysql-workbench-community-8.0.27-macos-x86_64.dmg.
I have downgraded to mysql-workbench-community-8.0.26-macos-x86_64.dmg, and it has solved it.
This issue has been reported to the MySQL team. See Test Connection in Workbench fails since SSL required (Bug #105327).
In the bug report, the development team replies that this issue will be fixed in 8.0.28.
Someone may be waiting for the fix, but check for the newest version on the download page.
I found this solution on Stack Exchange and worked for me just fine on Windows 10. This is the original post: MySQL Workbench: "ssl is required but the server doesn't support it".
Look for the fehrlich's answer. I will describe it here as in the original post:
You can bring back the old SSL options in 8.0.27:
Close MySQL Workbench
Go to you MySQL Workbench install folder (p.e. C:\Program Files\MySQL\MySQL Workbench 8.0 CE)
open the file modules/data/mysql_rdbms_info.xml
replace all occurrences of
">2|Require,3|Require and Verify CA,4|Require and Verify Identity"
with ">0|No,1|If available,2|Require,3|Require and Verify CA,4|Require
and Verify Identity"
Now you have the old options back.
Original image
I don't know if it may be the right approach for you, but I downgraded my version of MySQL Workbench to 6.3 and uninstalled the previous version. It will then give you the "if available" option for SSL. As you are right, it is not the case for previous versions, however you do lose a few more modern features in the process.
MySQL Product Archives
Another solution as well is to connect to connect to the database in 6.3 and since the configuration saves are in the same location, upgrade to 8.0 where it will still have the old configuration file and won't use SSL due to backwards compatibility.
I am using MySQL server 5.6. Uninstall and install MySQL Workbench 8. It's working.
I encountered this error when I was trying to export or import database from AWS RDS. I had Mysql Workbench on my system and also had Mysql installed locally.
As none of the solution mentioned here worked for me, I went further to investigate the error. I found out that the Workbench Default Target Mysql is 8.0.15 and my natively installed version of Mysql was 5.7.24, meaning the Mysqldump tool I was using didn't support the SSL protocol.
I bumped the natively installed Mysql to 8.0.18, and pointed the dump tool to it and it worked as expected.
Hope this helps someone too.
I'm installing Jira locally with the latest version (7.13 x64 version).
When doing the custom install and trying to switch to using MySQL as the database,
I get the error:
You have specified a database that is not empty, please specify an empty database.
The database is brand new, I literally just created it and if I query it I can see it has no tables created.
I created the database (and several others) using either the standard CREATE DATABASE ... or be specifying UTF-8 as well, which is how the Atlassisn docs suggest it is done.
But, no matter what I do, the same error keeps appearing. Topics on the Atlassian site mentioning this error haven't been any help and all seem to do with version conflicts which aren't relevant here.
I have installed the Java/MySQL connector version 8.0.13. Is it something to do with that?
Thanks in advance.
It was the JDBC connector that was the problem. I downloaded and installed the latest (version 8.0.13) but it was causing the error.
Installing version 5.1.47 works just fine, even though it isn't recommended for use with MySQL 5.6, which I'm using.
But, using that connector, I have a database installed and Jira is functioning as it should.
I know is so late for answer but say answer to other searcher this question
I found this error in the logs which lead me to https://jira.atlassian.com/browse/JRASERVER-67274
Loading class com.mysql.jdbc.Driver'. This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
The long and short of it is you need an older mysql-connector-java-5.1.x.jar driver instead of the latest mysql-connector-java-8.0.x.jar that the documentation would lead you to install.
Reverting my driver to mysql-connector-java-5.1.49.jar fixed the issue for me.
I have two installs of MySQL: one is a custom installation of MariaDB, and the other came prepackaged with XAMPP. Ideally I'd like to keep both and run either at separate times (I have no reason to run them together - thus port conflicting shouldn't be an issue).
When I run my MariaDB install, it runs fine. When I try running XAMPP install, it warns me "MySQL Service detected with wrong path," and doesn't get past "Attempting to start MySQL service..." when I try to run MySQL.
It also says "Found Path:" detecting the path to my MariaDB install, and "Expected Path:" indicating the location of the install prepackaged with XAMPP. What I don't understand is how it's even finding my MariaDB install.
I'm guessing it's something simple - any help is appreciated!
Details:
Windows 10
MariaDB 10.2.11
XAMPP v3.2.2
EDIT:
A similar question is answered here. However, my issue is not that the ports are conflicting, since my MariaDB install is not running. Notwithstanding, I've tried the solutions provided there, and still to no avail.
I downloaded mysql for my Mac from official website 'mysql.com', then launched it on my server using preferences pane and as well as from command line using
sudo /usr/local/etc/mysql/support-files/mysql.server start
Its working good, but during my development process i want to change the sql_mode,because i am getting below error
sql_mode=only_full_group_by
Many of them said to change sql mode config in /usr/mysql/my.cnf, but unfortunately i don't see that directory on my mac, So i installed Homebrew version mysql ,this also not working.
My Problem is where I can find my.cnf file on my mac? now i am not using homebrew version of mysql, I'm using official mysql downloaded from mysql.com/downloads.
Run mysql --help it will show you the config file that is being loaded.
Finally i got solution, i created new file inside /etc called my.cnf and set this as
[mysqld]
# Default : STRICT_TRANS_TABLES,ONLY_FULL_GROUP_BY,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
sql_mode = ""
Now its working great :) Thanks for your responses!
I tried to use MAMP Pro to replace previous XAMPP on my Mac due to its easy Virtual Hosts management. However after I installed it. The MAMP, basic version works, but the Pro version keeps given me this error message:
The MySQL configuration file my.cnf couldn't be written.
I googled for a while and there are some different solutions, like create my.cnf on /etc/, but none of these works. Also the error log is empty.
Has someone encountered this before? Or does anyone have a clue how could I solve this problem? Thank you!
I just purchased MAMP PRO and I'm having this error as well. Here's what "fixed" it:
Open Terminal and type in sudo killall -9 mysqld. You might see "No matching processes belonging to you were found," which is fine, it means that MySQL was not running.
Now, in Applications, look for the regular MAMP folder. Open MAMP here and click Start Servers
Now open MAMP PRO and the servers should be started
This is just a work-around, it definitely should not require these. At the very least, this should get you up and running.
Contacting support!
File -> Reset to Factory Settings
Possibly a permissions issue, but I wasn't able to resolve it. The above fixed it for me.
uninstall mamp.
remove all files about mamp.
reinstall mamp.
I removed 'my.cnf' from '/etc' directory. Restarted MAMP pro. Started server successfully.....
Your configuration may be wrong.
exp.
sql_mode = STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION # success
or
sql_mode = 'STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' # error