-
Notifications
You must be signed in to change notification settings - Fork 441
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.
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
Aborted connection to db: 'unconnected' user: 'unauthenticated' host: 'xxx' (This connection closed normally without authentication) #560
Aborted connection to db: 'unconnected' user: 'unauthenticated' host: 'xxx' (This connection closed normally without authentication) #560
Comments
Yeah and if i want to connect an application to it, i get the error |
Can second that: Message from Nextcloud: Going back to last image solved the problem for the moment. P.S. Bookstack container seems to have the same problem... |
I rolled back to 11.2 because none of my applications could connect to the mariadb. |
Found out, not all of my containers using MariaDB have this problem: |
We're looking into this right now. If anyone can provide an easy to reproduce test case, it would help out in diagnosing this. Relevant info:
|
I would like to add that the issue does not affect:
|
I believe this is the cause: https://jira.mariadb.org/browse/MDEV-32975 |
I'm not a Docker expert, so I'm trying to figure a workaround now, but basically the file
I'll see if I can investigate how to do this now, but if anyone has more Docker knowledge than me, please feel free to post it here. |
assuming if this only charset issue, docker wise can override command part with the charset.
|
That looks like it should work, I'm going to set up a test environment here shortly. |
it works for me! |
Yes without changes of collations for
I have tested suggested changes for
Same happens for other collation
|
Just to be clear: Are you running the |
the latest version -> 11.3.2 |
Hi All, Both, Netxcloud and Bookstack are running now with 11.3.2. And the other ones, which were not affected, are still running... |
First of all thank you @LinuxJedi for hitting the nail on the head. Many of us are here because our nextcloud setups went down and putting the collation into the docker command serves as a workaround for now. Nonetheless I would advise having a glance at the nextcloud documentations for docker compose examples and database config. The example already gives the following line: |
IT works for me |
So far I can tell, if the database created by latest Check on
Database created from :latest
Database from old version to latest
Stay same
|
It seems the dev wanted to modernize utf8mb4_general_ci to utf8mb4_uca1400_ai_cias as default |
I too thought that it was a typo too, but it is in fact correct (see https://mariadb.com/kb/en/server-system-variables/#character_set_collations). The problem stems from compatibility with the PHP MySQL connector and that default change for our Debian packages (which affects Docker images too). We already have a patch to fix the compatibility, but it hasn't been merged yet. This patch is now blocker level priority for us. I suspect something will be done on the Docker image as well in the mean time. |
I encountered the same problem when using this new image with wordpress docker image. I can connect using the mysql client from one container to the other, but wordpress can't. Rollbacking to the previous version resolved the problem. |
Unfortunately the last latest release broken PHP and nodejs because of a protocol issue. The configuration item character-set-collations added in the default 11.3/11.4 image generated this. Closes: MariaDB/mariadb-docker#560
Can confirm that all my containers running php scripts that connect to mariadb databases using mysqli also have this issue resulting in error "Aborted connection to db: 'unconnected' user: 'unauthenticated' host: 'IP' (This connection closed normally without authentication)". Connecting from the command line from inside the container using "mysql -h x -u y -p" did work properly as well as externally using dBeaver. Adding "command: --character-set-server=utf8mb4 --collation-server=utf8mb4_bin" to the docker-compose file on each container has "corrected" the issue. |
Docker hub contains new image as of ~15 mins ago. No work arounds should be required. |
Man, we had |
We apologise again for the inconvenience, I'm working an internal post-mortem right now (may make public too if there is interest) so that we can learn from it and prevent anything like this happening again for PHP / Docker users. |
I think it's fair to say there would be interest. We're all interested in building more robust systems, right? |
I keep the commabd even with the new version :) |
Had clearance to do that. I'll write it up in a more publicly consumable form in the next couple of days. |
I just deployed the latest and still received the same error. I've switched back to lts and it's fine but I believed that this issue was resolved already? |
I had the same problem in docker-compose, "latest" simply reused the most recent image, docker did not think the image had changed. I had to delete all mariadb images and pull latest again, then it worked. @mattdale77 |
Thanks. I've got a few so I'll need to track them all down. Thanks for the tip |
For those who requested it, post-mortem here: https://mariadb.org/post-mortem-php-and-mariadb-docker-issue/ |
Unfortunately the last latest release broken PHP and nodejs because of a protocol issue. The configuration item character-set-collations added in the default 11.3/11.4 image generated this. Closes: MariaDB/mariadb-docker#560
…ions" This reverts commit d7a950d.
This reverts commit 1e14bca. but only for 11.3/11.4 which haven't been updated.
…et-collations"" This reverts commit e067772.
…ations"" This reverts commit e067772.
Guys, I read this thread, but I could not figure out if the new collation Because if it's the new default, then we should create a migration script to update all of our databases on our production server. |
I just recently started using Docker, and I am using MariaDB's
and I am getting these errors every like 10 seconds:
But as far as I know I do not have anything on the same container that would connect over |
The original cause of this one was fixed with 11.4.2. The way I managed to generate that error was I also reproduced this with:
If your .my-healthcheck.sh is also has all permissions like #573 that could also be a causing factor if and unauthenticated tcp checks. |
My case is slightly different, than tat, but I'll post in that issue, since it's close to that. |
I'm running mariadb in docker with "latest"-tag. A nextcloud-container accesses the db via docker internal network.
Everything worked fine, but after I pull the latest (dae04d35ddd4ca837c1d330962eab9b5577325d1751e1877203b3fafe67b5daa) mariadb-image, Nextcloud can't connect anymore and mariadb throws the following:
Aborted connection to db: 'unconnected' user: 'unauthenticated' host: 'IP' (This connection closed normally without authentication)
When I start the container with the previous image I used before, everything works fine.
Anyone else?
The text was updated successfully, but these errors were encountered: