mariaex icon indicating copy to clipboard operation
mariaex copied to clipboard

mariaex error

Open active-infotronics opened this issue 6 years ago • 8 comments

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

active-infotronics avatar May 08 '18 06:05 active-infotronics

I have the same error after upgrading to MySQL 8.0

rebing avatar May 19 '18 09:05 rebing

We occasionally run into the same error.

pierot avatar Jul 11 '18 09:07 pierot

Can also confirm that the error happens when upgrading to MySQL 8.0, it disappears when downgrading to MySQL 5.7.

dragonwasrobot avatar Jul 11 '18 11:07 dragonwasrobot

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 use MariaDB 10.3

$ mix ecto.create

17:37:41.475 [error] GenServer #PID<0.200.0> terminating
** (RuntimeError) Connect raised a FunctionClauseError error. The exception details are hidden, as
they may contain sensitive data such as database credentials.

    (mariaex) lib/mariaex/protocol.ex:1006: Mariaex.Protocol.password/3
    (mariaex) lib/mariaex/protocol.ex:207: 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:249: :proc_lib.init_p_do_apply/3
Last message: nil
State: Mariaex.Protocol
** (Mix) The database for HelloPhoenix.Repo couldn't be created: an exception was raised:
    ** (RuntimeError) Connect raised a FunctionClauseError error. The exception details are hidden, as
they may contain sensitive data such as database credentials.

        (mariaex) lib/mariaex/protocol.ex:1006: Mariaex.Protocol.password/3
        (mariaex) lib/mariaex/protocol.ex:207: 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:249: :proc_lib.init_p_do_apply/3

Hokutosei avatar Jul 17 '18 08:07 Hokutosei

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?

Kitton avatar Jul 17 '18 10:07 Kitton

Seems like it, while running a gitlab CI task it kept failing on the same but after downgrading to mysql:5.7 now everything is working as expected

sigu avatar Sep 11 '18 09:09 sigu

MySQL 8 changes the default authorization plugin, to wokraround you need to to start MySQL with parameter: --default-authentication-plugin=mysql_native_password or include this in your my.cnf:

[mysqld]
default-authentication-plugin=mysql_native_password

b3k avatar Oct 05 '18 20:10 b3k

I am facing this intermittently with mysql:5.7 as well, it goes away when I deploy again only to comeback again later.

sahilpaudel-pe avatar Jan 17 '22 05:01 sahilpaudel-pe