Repository navigation
mariaex error #222
Description
mix ecto.create
** (Mix) The database for Myapp.Repo couldn't be created: an exception was raised:
** (RuntimeError) Connect raised a CaseClauseError error. The exception details are hidden, as
they may contain sensitive data such as database credentials.
(mariaex) lib/mariaex/protocol.ex:1155: Mariaex.Protocol.abort_statement/3
(mariaex) lib/mariaex/protocol.ex:227: Mariaex.Protocol.handle_handshake/3
(mariaex) lib/mariaex/protocol.ex:166: Mariaex.Protocol.handshake_recv/2
(db_connection) lib/db_connection/connection.ex:135: DBConnection.Connection.connect/2
(connection) lib/connection.ex:622: Connection.enter_connect/5
(stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3
05:30:56.398 [error] GenServer #PID<0.724.0> terminating
** (RuntimeError) Connect raised a CaseClauseError error. The exception details are hidden, as
they may contain sensitive data such as database credentials.
(mariaex) lib/mariaex/protocol.ex:1155: Mariaex.Protocol.abort_statement/3
(mariaex) lib/mariaex/protocol.ex:227: Mariaex.Protocol.handle_handshake/3
(mariaex) lib/mariaex/protocol.ex:166: Mariaex.Protocol.handshake_recv/2
(db_connection) lib/db_connection/connection.ex:135: DBConnection.Connection.connect/2
(connection) lib/connection.ex:622: Connection.enter_connect/5
(stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3
Last message: nil
State: Mariaex.Protocol
Activity
rebing commentedon May 19, 2018
I have the same error after upgrading to MySQL 8.0
pierot commentedon Jul 11, 2018
We occasionally run into the same error.
dragonwasrobot commentedon Jul 11, 2018
Can also confirm that the error happens when upgrading to MySQL 8.0, it disappears when downgrading to MySQL 5.7.
Hokutosei commentedon Jul 17, 2018
I thought I was the only who is having the same error while following the tutorial using
mysql Ver 8.0.11 for Linux on x86_64 (MySQL Community Server - GPL)but everything seems to be working fine if I useMariaDB 10.3Kitton commentedon Jul 17, 2018
I can't find this info anywhere, but looks like currently mariaex doesn't support MySQL 8.0.x? Can anyone from maintainers confirm it?
sigu commentedon Sep 11, 2018
Seems like it, while running a gitlab CI task it kept failing on the same but after downgrading to
mysql:5.7now everything is working as expectedb3k commentedon Oct 5, 2018
MySQL 8 changes the default authorization plugin, to wokraround you need to to start MySQL with parameter:
--default-authentication-plugin=mysql_native_passwordor include this in yourmy.cnf:sahilpaudel-pe commentedon Jan 17, 2022
I am facing this intermittently with
mysql:5.7as well, it goes away when I deploy again only to comeback again later.