Mysql Download For Windows 10 64 Bit Msi Installer
Teodolinda Mattson
I asked this question on Stack Overflow as well, but decided I had to ask it here too. I have been trying for quite some time to install MySQL Server. I have read the documentation countless times, but can't even find a hint of what to do. It is really, really frustrating me.
Why can't you try installing the MySQL using its MSI installer, which is much user friendly - where you can have a installation wizard with nice on-screen instruction, where you can simply install it by following the simple 1,2,3 steps ..
The archive is a compressed version of the MySQL directory structure. When you extract this archive you'll find that it creates a directory called mysql-5.6.22-win32 inside whichever directory you told it to extract to.
If the ZIP file is downloaded to C:\Users\your_user_name\Downloads and you were to extract the archive into that directory, then a directory named mysql-5.6.22-win32 would exist inside C:\Users\your_user_name\Downloads. This folder contains all the MySQL files.
I have seen this problem recently. There appears to be a problem with this build (2.0 Beta 2) from Bitnami. Even though it asks your what port to use for mysql, it still uses the default port. So if you have something running on the default mysql port (3306), such as another Bitnami stack or your own instance of mysql, the installer fails trying to seed the database.
Has there been any response from Bitnami support on this? We may be able to contact them directly with this issue and get a faster response than you. We just need exact steps to replicate the issue, including how you installed your original MySQL and on what port, and all config and port information you input in the Bitnami installer.
sorry for the late response, well the original mysql is installed using the all in one installer from Mysql on port 3306, beside that I just run the bitnami installer and change the port in the wizard form 3306 to 3307 and I got the error that I showed you on the screenshot
I just downloaded the stack from Bitnami, bitnami-dreamfactory-2.0.1-1-windows-installer.exe and also had MySql installed, same distribution as @Jose_Manuel_Ojeda , but got slightly different error (On Windows 7, Enterprise N, Service Pack 1) See my other postings for exact message, but it was unable to execute the artisan migration.
Hi @JayDee I do have a work around for that. first uninstall mysql, the install dream factory with the bitnami installer, then re install mysql, just make sure you have different ports for each instance of mysql because dream factory will install an instance on 3306.
Here, you can choose what features to install. By default, all features areinstalled with the exception of the debug symbols. If the "Database instance"feature is selected, the installer will create a database instance, by defaultrunning as a service. In this case the installer will present additionaldialogs to control various database properties. Note that you do notnecessarily have to create an instance at this stage. For example, if youalready have MySQL or MariaDB databases running as services, you can justupgrade them during the installation. Also, you can create additional databaseinstances after the installation, with the mysql_install_db.exe utility.
NOTE: By default, if you install a database instance, the data directorywill be in the "data" folder under the installation root. To change the datadirectory location, select "Database instance" in the feature tree, and use the"Browse" button to point to another place.
This dialog is shown if you selected the "Database instance" feature. Here, youcan set the password for the "root" database user and specify whether root canaccess database from remote machines. The "Create anonymous account" settingallows for anonymous (non-authenticated) users. It is off by default and it isnot recommended to change this setting.
Installation is finished now. If you have upgradable instances ofMariaDB/MySQL, running as services, this dialog will present a "Do you want toupgrade existing instances" checkbox (if selected, it launches the UpgradeWizard post-installation).
Silent installations also support installation properties (a property wouldcorrespond for example to checked/unchecked state of a checkbox in the UI, userpassword, etc). With properties the command line to install the MSI packagewould look like this:
If you encounter a bug in the installer, the installer logs should be used fordiagnosis. Please attach verbose logs to the bug reports you create. To create a verboseinstaller log, start the installer from the command line with the /l*vswitch, like so:
Apart from testing, an example where this feature can be useful is adevelopment scenario, where users want to run a 64 bit server and develop both32 and 64 bit client components. In this case the full 64 bit package can beinstalled, including a database instance plus development-related features(headers and libraries) from the 32 bit package.
I can't seem to find clear instructions anywhere for doing an in place upgrade from MySQL 5.6 to 5.7. The community installer shows no upgrade from 5.6.35 to 5.7.x. Do I need to remove and install, or install in parallel, and then import the database from a backup? Am I missing some obvious steps somewhere?
@isradame, so you updated to 9.98 and cannot do backups? Jamf support still said 5.7 is NOT supported even though the documentation specifically states MySQL 5.7 compatibility and is recommended? Are you backing up with the Backup Utility?
@ryanstayloradobe , yes. I upgraded to 9.98 and MySql 5.7. I could not do manual and also using the JSS Database backup utility.
I told Jamf support that their document states MySql 5.7 is recommended.
(From page 14 of the JSS Installation and Configuration Guide for Mac 9.98PDF document. "The JSS Database Utility requires a server with MySQL 5.6.x or 5.7.x (MySQL 5.7.x is recommended) installed.").
@isradame I could make and restore backups just fine with MySQL 5.7 on Windows. I had to comment out line 62 in MySQL's my.ini configuration file, as well as change line 287 as follows (depending on your config, they may be on different line numbers:
This may be a Mac side issue with macOS Sierra 10.12.4, MySql 5.7 and JAMF Pro 9.98.
I had to remove MySql 5.7 and re-install the 5.6 version.
I also have a specific username and password for the 'jamfsoftware" database. Not using the default.
@isradame have you tried making the changes suggested above to your my.cnf file? As far as I know the settings are stored in the same way irrespective of platform. If it doesn't exist in /etc/my.cnf then @bentoms describes how to create it here: -database-utility-change-mysql-settings-greyed-out/
Do you get a specific error message when you try to create a backup? The other thing I had to do was make the JSS Database Utility aware of the MySQL 5.7 binaries location - it prompted the first time it was launched after migrating.
@neil.martin83 yes I did.
Not only the issue with not able to do backups, but the MySql service was restarting automatically.
Here is the error I would get when I tried to perform a backup, thru the JAMF Utility or manually.
"Encountered an error during applications repair: mysql: [Warning] Using a password on the command line interface can be insecure.Error 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error:0"
Sometimes installing a newer version of MySQL is more of a second installation vs what we normally think of as an upgrade so you have the possibility of files (normally the my.ini/my.cnf) from previous versions of mysql remaining and being respected but some of their settings might be out of date or the new files might not have the settings you have previously configured.
"No-beep" was removed prior to version 5 of mysql I believe so that would likely cause issues if it was still there. You may have to check all instances of the my.cnf/my.ini on the system as they could be installed and respected in multiple locations depending on versions and installation methods. This KB on using Option Files can help you locate them.
Sometimes you need to increase your max_allowed_packet if you have a packet in your database that is larger than the default 16mb, but typically this is not the case. Normally the main thing to increase this for is when uploading printer ppds, and you will see an error in logs if this is the case. DO NOT just go increase this value unless you are having issues uploading files or are getting errors with your mysql dump because of a previously uploaded packet. If you are getting errors with the dump, look at the logs and see what size it says its failing for and increase to that value and not an arbitrary value. It is set at this default value for a reason and could cause problems if increased for no reason. I have seen rouge clients with built up logs due to proxies peg tomcat servers sending massive file submissions and since mysql was set to allow it, it took that large amount of data and in turn brought the server down. Also adjusting max_allowed_packet is not for scale or performance, it is literally the cap on the largest data packet that can be put in the database.
@isradame the issue you are mentioning with MySQL starting/stopping in System Preferences will cause errors while connecting via command line or doing backups when its stopped, and is generally seen on a Mac and has been seen with previous versions of MySQL as well. We have had some success with modifying the table_open_cache values in the my.cnf but I would reach out to support to have them work with you on that.
@kirkmshaffer After a clean reload of the OS 10.12.4, a clean install of JAMF "9.98", latest Java "1.8" and the latest MySql "5.7". I still had the same problem.
Could not do manual or use the JSS Database utility for backups.
Also the mysql service was crashing.
Here is what I did to fix it. I do not deserve the credit. @zachary.fisher provided me with the instructions.