Im trying to install mysql on SUSE 15 Sp2 :
Followed steps from official documentation :
https://dev.mysql.com/doc/mysql-sles-repo-quick-guide/en/
But when i tried to install the mysql getting following error :
Problem: nothing provides 'libc.so.6(GLIBC_2.28)(64bit)' needed by the
to be installed mysql-community-server-8.0.29-1.sl15.x86_64
Solution
1: do not install mysql-community-server-8.0.29-1.sl15.x86_64
Solution 2: break mysql-community-server-8.0.29-1.sl15.x86_64 by
ignoring some of its dependencies
According to the list of platforms that are supported by this version of MySQL, version 15.3 of openSUSE is required. That's probably what's going wrong here: The version of glibc which is provided by the repositories of your openSUSE 15.2 is too old for this MySQL version. If possible, I would recommend you backup your system and then upgrade to 15.3 and then to 15.4, see these instructions. Especially when you intend to do development, it's really wise to first upgrade your OS to the latest version, because only then will you have the latest versions of the technologies you're learning – otherwise, some things you learn will be outdated from day one.
Related
I have a Wordpress site that was developed on a server running the latest version of MYSQL, however, I've just found out the host server (BT) is running 5.1.1. and they have no plans to upgrade anytime soon.
Does anyone know if there is a way of converting the database so it runs on 5.1.1 with no issues caused re the site being built in the latest version of Wordpress?
If this is a massive issue, then I do have some alternative hosting options, but I'm hoping for a way forward re conversion - any geniuses out there?
Many thanks
I doubt that BT is running MySQL 5.1.1. That version was never released. It was an internal development milestone in 2005.
The first GA release of the 5.1 branch was 5.1.30 in 2008. The last 5.1 release was 5.1.73 in 2013. But after 2013, 5.1 has been in "sustaining support" which means they will not make any new versions or fixes.
You shouldn't deploy to a hosting site that still runs any 5.1.x version. A site that is so far behind is probably behind on other software too, and I would not be surprised if they have known security vulnerabilities.
Wordpress officially requires MySQL 5.6 or later, according to https://wordpress.org/about/requirements/.
You could try to test that by testing on MySQL 5.1 (assuming you can find an installation package of MySQL 5.1). Use mysqldump to export data from your 5.6 database server and then import that to MySQL 5.1. The output of mysqldump wraps newer syntax in special comments that will be ignored by older versions of MySQL Server.
Regardless, my recommendation is:
Find another hosting service running MySQL 5.6 or 5.7.
Develop and test your site with the same versions of all software (MySQL, PHP, Apache, etc.) that you will eventually deploy to.
Hi I believe there have been some similar topics regarding connector/ net not supporting server versions prior to 5.0.
I have been trying add in a connection to a database in visual studio 2013 and I am not able to connect due to the server version being 4.1.2 I am unable to upgrade this databases server as its out of my hands.
What I have done is follow the suggested answers which is downgrade the connector/ net prior to 5.0 and downgrade the mysql server to 4.1.
I have added in the reference and its still giving me the same error.
Can anyone suggest anything else I could try or may be missing?
Cheers guys I'm pretty desperate now!!
See MySQL Connector/Net Developer Guide - Connector/Net Versions. This document contains table that shows the .NET Framework version required, and the MySQL Server version supported by Connector/Net.
For MySQL Server 4.1 you may need to install Connector/NET v. 6.2 and .NET Framework 2.x
what you must do is, install a lower NuGet that supports the version you have of maria db, in my case, I install the MySql.Data.EntityFramework 8.0.11 and it will work without problem.
I'm trying to istall mysql server on a windows 7 machine - that has python 3.4.3 installed. However, when trying to install the python connectors for 3.4, the installer fails to recognize the python installation, saying python 3.4 is not installed.
Has anyone solved this issue before? I'ts driving me nuts...
Just to add to the murkiness, I had the same error with current version of MySql install when attempting with python 3.5 installed (which is the latest python download). Long story short, I uninstalled python 3.5, installed python 3.4.4 (which interestingly didn't update PATH so I updated it manually) and reran installer and it found the python installation.
So my conclusion is the MySql installer is tied to certain versions of the add-on products which in this case meant specifically python 3.4
just in case anyone else has this issue in future. Look at what bit version you have for Python 3.4. When I installed 64 bit version of Python 3.4, this issue went away.
I ran into a similar issue with Python 3.7.2.
In my case, the problem was that I tried to install the 64 bit MySQL connector, but had the 32 bit version of Python installed on my machine.
I got a similar error message:
Python v3.7 not found. We only support Python installed using the Microsoft Windows Installer (MSI) [...]
The problem just went away by installing the 32 bit MySQL connector instead.
From my experience if you have both Py2.7 and Py3.4 installed when installing the mysql connector for py3.4 you will run into this issue. Not sure of the WHY but for some reason if you have py2.7 installed, the py3.4 mysql connector recognizes that version first and just assumes that you have py2.7 installed and does not recognize that py3.4 is installed.
The only way I have found around this is to uninstall py2.7 and then install the py3.4 mysql connector. You can always install py2.7 again after the fact.
I had 3.6.X version and it could not see it; I uninstalled it and installed 3.4.0 version and it passed the requirement.
https://www.python.org/downloads/release/python-340/
Had the same problem and have fixed it. Using a Windows 7 PC and I already had multiple versions of Python installed.
Uninstalled all versions of Python from my PC
Uninstalled the failed MySQL install
Restarted PC
Re-installed Python 3.7 64-bit (the currently required version for MySQL)
Installed the Python 3.7 MySQL Connector separately through the link below
https://dev.mysql.com/downloads/connector/python/
Once that was installed, restarted the MySQL install
The MySQL Installer window will open and already show the Python 3.7 MySQL Connector in the list of products
Click "Add" at the top-right and select all of the products you want and then install them
You should then be able to complete the MySQL setup
I was looking for an similar answer. The correct answer is that there is a bug in the mysqlconnector MSI. When python installs, it creates a registry entry under HKLM Software\Python\PythonCore\3.6-32\InstallPath however, the MSI for mysqlconnector is looking for installation path in the registry Software\Python\PythonCore\3.6\InstallPath as part of the RegLocator/registrypath variable.
Use ORCA to edit the MSI, change the RegLocator so that -32 is in the path. It will install now without error or changes to the system.
I had same problem with python 3.4, all I did was installed python 3.4 version for all users. and added system variable as per this page. it worked for me!
Hope that helps.
Make sure you have the 64bit version of whichever version of Python you are running. It can be downloaded from here:
https://www.python.org/downloads/windows/
Just had the same problem and this solved it for me. I also uninstalled all previous versions of Python before running the mysql setup
I had this problem until I discovered I had installed python based in another architecture (32b). MySQL required 64 bit.
Had the same problem with Python 3.7 when trying to install MySQL in Windows 10. It was fixed by installing the 64-bits version of Python, not selected by default when going to https://www.python.org/downloads/.
I found it in https://www.python.org/ftp/python/3.7.3/python-3.7.3-amd64.exe
Here is a much simpler work around:
pip install mysql-connector-python
Is the same package that MySQL is having trouble installing. Just use pip to install it.
Next, go back to the installation style and select "Manual" instead of "Developer". They are identical, but "Manual" allows you to remove packages. Just remove the "Connector/Python" package from the list to be installed.
Carry on with the install, you're done.
I am trying to start a new application Ruby on Rails 3.1 on Debian Squeeze with MySQL Server 5.1 (the latest supported by Debian stable version).
I have problem with the mysql2 gem. When I use mysql2 gem version 0.2.6 rake migrations fail with error undefined method rows for nil class. I gooogled and everybody says that this error is resolved when one upgrades mysql2 gem to 0.3.X. However, when I do this upgrade I get another error about gem having been compiled for 5.5 mysql client and not 5.1.
Any help would much appreciated. Maybe the answer is "NO. YOU CANNOT DO IT". Even then, I want to know that.
Thanks in advance
Panayotis
Well, this is a tricky question. My current rails package latest version is 2.3.5-1.2+squeeze2 and the current mysql-server package is 5.1.49-3, both from the stable debian repositories.
However, you're trying to install RoR 3.1. That means you're not on stable or you are not trying to install it from any of the official debian repository at all (it is not wheeze nor sid).
If you can install the stable version of rails, go ahead and I bet you won't have any trouble. Otherwise, if you want the most current release I'm pretty sure you'll have to go for the dirty way. It might probably involve download a 5.5 MySQL (not from the repositories, because it isn't there) and messing with the libraries.
Remember if you require newer packages (such as newer libraries) and you don't want to use the testing repositories, you can always give debian backports a try.
MySQL 6.0 is for production. Can I use it for database storage of a large project?
MySQL 5.1 is the latest stable version, I'd recommend sticking with that. 6.0 will be quite unstable at this point.
EDIT as of 2011-05-26 MySQL 5.5.12 is the latest stable version. See this link for the lastest stable version: http://dev.mysql.com/downloads/
MySQL 6.0 in this moment is a alpha version, so I suggest you to use the current stable release -> MySQL 5.1
Here you can find some info about the table size limit depending on operating System. MySQL has not internal limit.
Only if there are critical enhancements that your site requires. And even then I'd hold back and use workarounds until it at least gets to beta.
We tried to use the latest PHP and MySQL 5.1 with failure on an IIS7 machine. I am sure if you download the source of PHP and compile it, it would have support for 5.1, but out of the box it seems to support 5.0. So, we replaced 5.1 with 5.0 and everything worked flawlessly.
Short story is use what works well. I would try it in development and avoid it in production until everything works well.