Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MySQL 8.0 service not started in the latest Visual Studio 2022 image #3894

Open
BAndysc opened this issue Oct 31, 2023 · 2 comments
Open

MySQL 8.0 service not started in the latest Visual Studio 2022 image #3894

BAndysc opened this issue Oct 31, 2023 · 2 comments

Comments

@BAndysc
Copy link

BAndysc commented Oct 31, 2023 •
edited
Loading

The latest VS 2022 image includes MySQL 8.0 instead of 5.7, however it looks like the service is not working despite having mysql service enabled in the yml as per docs (or the credentials to the database were changed?) At least this command:

"C:\Program Files\MySQL\MySQL Server 5.7\bin\mysql" -u root -p'Password12!' -e 'DROP DATABASE IF EXISTS temp_CI'

used to work before and now

"C:\Program Files\MySQL\MySQL Server 8.0\bin\mysql" -u root -p'Password12!' -e 'DROP DATABASE IF EXISTS temp_CI'

yields

ERROR 2003 (HY000): Can't connect to MySQL server on 'localhost:3306' (10061)
@BAndysc BAndysc changed the title MySQL 8.0 credentials in the latest Visual Studio 2022 image MySQL 8.0 service not started in the latest Visual Studio 2022 image Oct 31, 2023
@OwenMcDonnell
Copy link

Can you try after adding the following to your appveyor.yml config file.

init:
  - ps: Start-Service MySQL80

@BAndysc
Copy link
Author

BAndysc commented Oct 31, 2023

Thanks for the answer, yup, this worked whereas service: - mysql didn't. Not sure if that's a bug or not.

@keitherskine keitherskine mentioned this issue Nov 1, 2023
Merged
@dveeden dveeden mentioned this issue Nov 1, 2023
Open
@LadySolveig LadySolveig mentioned this issue Nov 1, 2023
Merged
4 tasks
NickCraver added a commit to DapperLib/Dapper that referenced this issue Nov 13, 2023
@NickCraver
AppVeyor: Restore MySQL
26744b7 
Looks like the image was borked with MySQL 8 went in (because it's still trying to start 5.7), see appveyor/ci#3894.
@NickCraver NickCraver mentioned this issue Nov 13, 2023
Merged
NickCraver added a commit to DapperLib/Dapper that referenced this issue Nov 13, 2023
@NickCraver
AppVeyor: Restore MySQL (#1998)
cea07ab 
Looks like the image was borked with MySQL 8 went in (because it's still trying to start 5.7), see appveyor/ci#3894.
huysentruitw added a commit to gantner-nv/Rebus.MySql that referenced this issue Nov 14, 2023
@huysentruitw
AppVeyor: try to switch to MySQL 8.0 (see appveyor/ci#3894)
66e78ab
@dveeden dveeden mentioned this issue Nov 20, 2023
Merged
bgrainger added a commit to mysql-net/MySqlConnector that referenced this issue Dec 5, 2023
@bgrainger
Update Appveyor build to MySQL 8.0.
83403d3 
This mirrors changes other projects have made in response to this issue: appveyor/ci#3894
vadz added a commit to vadz/soci that referenced this issue Dec 7, 2023
@vadz
Fix using MySQL in recent AppVeyor environments
6f56584 
They don't have MySQL 5.7 any more but only 8.x and starting mysql
service doesn't work any longer, so it has to be done manually, see
appveyor/ci#3894
Giorgi added a commit to Giorgi/EntityFramework.Exceptions that referenced this issue Dec 8, 2023
@Giorgi
Workaround for MySql not working
40b0144 
appveyor/ci#3894
vadz added a commit to SOCI/soci that referenced this issue Dec 11, 2023
@vadz
Fix using MySQL in recent AppVeyor environments
ea6e14c 
They don't have MySQL 5.7 any more but only 8.x and starting mysql
service doesn't work any longer, so it has to be done manually, see
appveyor/ci#3894
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BAndysc @OwenMcDonnell