Forums WoW Modding Support Archives Azerothcore Discord Archives [DiscordArchive] <@184039710513954818> Looks like dB connection is failing for dbimport of the container. If you run

[DiscordArchive] <@184039710513954818> Looks like dB connection is failing for dbimport of the container. If you run

[DiscordArchive] <@184039710513954818> Looks like dB connection is failing for dbimport of the container. If you run

rektbyfaith
Administrator
0
09-09-2023, 05:49 AM
#1
Archived author: volek • Posted: 2023-09-09T05:49:21.394000+00:00
Original source

<@184039710513954818> Looks like dB connection is failing for dbimport of the container. If you run docker container ls, do you see a running mysql 8.0 container?
rektbyfaith
09-09-2023, 05:49 AM #1

Archived author: volek • Posted: 2023-09-09T05:49:21.394000+00:00
Original source

<@184039710513954818> Looks like dB connection is failing for dbimport of the container. If you run docker container ls, do you see a running mysql 8.0 container?

rektbyfaith
Administrator
0
09-09-2023, 05:57 AM
#2
Archived author: volek • Posted: 2023-09-09T05:57:32.310000+00:00
Original source

I am going to head to bed so I will leave you a few things that may help

1. Check the dbimport.conf under env/ folder see what the credentials are and attempt to use them to connect the running mysql container.
2. If it fails you have a user permission issue on the db user. I believe dbimport uses acore username.
3. Add username to running database using root username and password found in .conf files root/password for new install.
4. Make sure to create the acore user and password and update it in the dbimport.conf file.
5. Attempt to manually connect to the table with new credentials, then on success rerun docker compose up.

Hope it helps, I had a similar issue when the acore@% user wad not setup and granted correct permission on initial install.
rektbyfaith
09-09-2023, 05:57 AM #2

Archived author: volek • Posted: 2023-09-09T05:57:32.310000+00:00
Original source

I am going to head to bed so I will leave you a few things that may help

1. Check the dbimport.conf under env/ folder see what the credentials are and attempt to use them to connect the running mysql container.
2. If it fails you have a user permission issue on the db user. I believe dbimport uses acore username.
3. Add username to running database using root username and password found in .conf files root/password for new install.
4. Make sure to create the acore user and password and update it in the dbimport.conf file.
5. Attempt to manually connect to the table with new credentials, then on success rerun docker compose up.

Hope it helps, I had a similar issue when the acore@% user wad not setup and granted correct permission on initial install.

rektbyfaith
Administrator
0
09-09-2023, 06:05 AM
#3
Archived author: NiceGentleman • Posted: 2023-09-09T06:05:34.518000+00:00
Original source

yes there is a running mysql container. Thank you I'll work through these steps and get back to you
rektbyfaith
09-09-2023, 06:05 AM #3

Archived author: NiceGentleman • Posted: 2023-09-09T06:05:34.518000+00:00
Original source

yes there is a running mysql container. Thank you I'll work through these steps and get back to you

rektbyfaith
Administrator
0
09-09-2023, 04:51 PM
#4
Archived author: mynameismeat • Posted: 2023-09-09T16:51:17.062000+00:00
Original source

You should be able to merge in the changes from this PR to fix that

https://github.com/azerothcore/acore-doc...7775bed0d3
rektbyfaith
09-09-2023, 04:51 PM #4

Archived author: mynameismeat • Posted: 2023-09-09T16:51:17.062000+00:00
Original source

You should be able to merge in the changes from this PR to fix that

https://github.com/azerothcore/acore-doc...7775bed0d3

rektbyfaith
Administrator
0
09-09-2023, 06:52 PM
#5
Archived author: NiceGentleman • Posted: 2023-09-09T18:52:32.474000+00:00
Original source

I pulled your branch but I'm getting the same error unfortunately and I have confirmed that I'm able to connect to the mysql container manually. I can try the non-docker setup if that's more likely to work. I was hoping for some It Just Works docker magic but I guess that's not the case today
rektbyfaith
09-09-2023, 06:52 PM #5

Archived author: NiceGentleman • Posted: 2023-09-09T18:52:32.474000+00:00
Original source

I pulled your branch but I'm getting the same error unfortunately and I have confirmed that I'm able to connect to the mysql container manually. I can try the non-docker setup if that's more likely to work. I was hoping for some It Just Works docker magic but I guess that's not the case today

rektbyfaith
Administrator
0
09-09-2023, 07:11 PM
#6
Archived author: volek • Posted: 2023-09-09T19:11:55.604000+00:00
Original source

Did you look in the dberrors log file to see if that has any additional details?
rektbyfaith
09-09-2023, 07:11 PM #6

Archived author: volek • Posted: 2023-09-09T19:11:55.604000+00:00
Original source

Did you look in the dberrors log file to see if that has any additional details?

Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)