# Observability Lab 2.2 - mysql incorrect creds **URL:** \ **Category:** Elastic Training\ **Created:** [February 22, 2023, 12:38am UTC](https://discuss.elastic.co/t/observability-lab-2-2-mysql-incorrect-creds/326111 "2023-02-22T00:38:18Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![deccman](https://avatars.discourse-cdn.com/v4/letter/d/ecc23a/32.png) [@deccman](https://discuss.elastic.co/u/deccman)\ **Post date:** [February 22, 2023, 12:38am UTC](https://discuss.elastic.co/t/observability-lab-2-2-mysql-incorrect-creds/326111/1 "2023-02-22T00:38:18Z")
Course: Observability Engineer Version: 7.9 Question: I am currently doing the Observability Engineer Training for version 7.9 and have hit a roadblock in the lab training. In lab 2.2 you set up Metricbeats for MySQL. I have followed the instructions carefully, done the correct changes to metricbeat.yml and confirmed that the changes are correct. However after enabling the mysql module and doing the changes to modules.d/mysql I am unable to to do step 14 in the lab instructions. It comes back with an error saying the account details are incorrect for connecting to the mysql instance on the server. Is there anyway of resetting the password for the MySQL instance on mysql server or find out what the correct root password is? I have tried seeing if I can reset the root password in MySQL but have not had any success. I will attach screenshots of the mysql.yml file as well as the output I get when I run a test against the mysql module ![mysql_error](https://us1.discourse-cdn.com/elastic/original/3X/c/4/c4941d53df11f0570d7bd3780a32789f509aa825.png) ![mysql_yml](https://us1.discourse-cdn.com/elastic/original/3X/7/3/733feacd62a263f12813e250677d274c510c64f1.png) ---
**Author:** ![Andre\_Murbach\_Maidl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_murbach_maidl/32/83508_2.png) [@Andre\_Murbach\_Maidl](https://discuss.elastic.co/u/Andre_Murbach_Maidl)\ **Post date:** [February 22, 2023, 1:04pm UTC](https://discuss.elastic.co/t/observability-lab-2-2-mysql-incorrect-creds/326111/2 "2023-02-22T13:04:01Z")
Hi @deccman , your configuration file looks good. Did you try running the test command after you setup `mysql:3306` as the host and port for the MySQL server? In your first screenshot it looks like it tried `127.0.0.1:3306` instead. Also, are your executing labs inside the `mysql` container? Best, Andre ---
**Author:** ![deccman](https://avatars.discourse-cdn.com/v4/letter/d/ecc23a/32.png) [@deccman](https://discuss.elastic.co/u/deccman)\ **Post date:** [February 22, 2023, 8:56pm UTC](https://discuss.elastic.co/t/observability-lab-2-2-mysql-incorrect-creds/326111/3 "2023-02-22T20:56:38Z")
Hi Andre, I am running the test command with the mysql.yml file set to mysql:3306 in the mysql container. I have run `ps -eaf` on the mysql server to make confirm mysql is running. I have also tried running the test command without a password in the mysql.yml file and still have no success. There are no issues with the metricbeats.yml file, the test command comes back OK. Cheers, Declan ---
**Author:** ![Andre\_Murbach\_Maidl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_murbach_maidl/32/83508_2.png) [@Andre\_Murbach\_Maidl](https://discuss.elastic.co/u/Andre_Murbach_Maidl)\ **Post date:** [February 23, 2023, 2:44pm UTC](https://discuss.elastic.co/t/observability-lab-2-2-mysql-incorrect-creds/326111/4 "2023-02-23T14:44:59Z")
hi @deccman , since you are at the beginning of the training it would be a good idea to replace your environment so you can start over again. Please send me a direct message with your e-mail so I can replace your machine. Best, Andre ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 25, 2023, 2:45pm UTC](https://discuss.elastic.co/t/observability-lab-2-2-mysql-incorrect-creds/326111/5 "2023-03-25T14:45:21Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.