MySql-Workbench cant connect to MariaDb server

evelynn · October 10, 2024, 6:08pm

The cli connection with my user work just fine in the terminal. But MySQL-workbench is absolutely refusing to connect i did try switching from TCP/IP to the LocalSocet/pipe and configures the MySQL-workbench to MariaDB, but it won’t connect

i included an error log from my MySQL-Workbench logs there is a lot in there that i dont have any idea about (im getting into sql for the first time) and i did try feeding it to ChatGBT so i would waste anyones time but it was to no avail.

Notes

MariaDB is enabled and the service is running
the server is setup with Unix_socet authentication
i removed anonymes users
my made a user with my name and password in MariaDB login via that works in terminal
I have reinstalled mariaDB and MySQL-Workbench a bunch of times
Neither TCP/IP nor LocalSocet/pipe seems to let me connect
i added the ports in firewalld (im not sure if i did it right see screenshot)

                     ./o.                  evlarch@evelarchlaptop 
                   ./sssso-                ---------------------- 
                 `:osssssss+-              OS: EndeavourOS Linux x86_64 
               `:+sssssssssso/.            Host: X550LB 1.0 
             `-/ossssssssssssso/.          Kernel: 6.11.2-zen1-1-zen 
           `-/+sssssssssssssssso+:`        Uptime: 23 hours, 57 mins 
         `-:/+sssssssssssssssssso+/.       Packages: 1286 (pacman), 10 (f 
       `.://osssssssssssssssssssso++-      Shell: zsh 5.9 
      .://+ssssssssssssssssssssssso++:     Resolution: 1366x768 
    .:///ossssssssssssssssssssssssso++:    DE: Hyprland 
  `:////ssssssssssssssssssssssssssso+++.   WM: sway 
`-////+ssssssssssssssssssssssssssso++++-   Theme: Arc-Dark [GTK2/3] 
 `..-+oosssssssssssssssssssssssso+++++/`   Icons: Qogir-dark [GTK2/3] 
   ./++++++++++++++++++++++++++++++/:.     Terminal: kitty 
  `:::::::::::::::::::::::::------``       CPU: Intel i5-4200U (4) @ 2.60 
                                           GPU: NVIDIA GeForce GT 740M 
                                           GPU: Intel Haswell-ULT 
                                           Memory: 2608MiB / 7759MiB

	base dir: /usr/share/mysql-workbench
	plugin path: /usr/lib/mysql-workbench/plugins
	struct path: /usr/share/mysql-workbench/grt
	module path: /usr/lib/mysql-workbench/modules
	library path: /usr/share/mysql-workbench/libraries
	user data dir: /home/evlarch/.mysql/workbench
	open at start: 
	open type: 
	run at startup: 
	run type: 
	Force SW rendering: No
	Force OpenGL: No
	quit when done: No
19:16:23 [INF][      WBContext]: WbContext::init
19:16:24 [INF][            WBA]: Looking for extension modules for WBA...
19:16:24 [INF][            WBA]: 0 extension modules found
19:16:24 [WRN][            grt]: Duplicate plugin name wb.tools.cmdlineClient	There is more than one plugin with the name wb.tools.cmdlineClient (in PyWbUtils and PyWbUtils).
19:16:25 [WRN][            grt]: Duplicate plugin name wb.tools.cmdlineClient	There is more than one plugin with the name wb.tools.cmdlineClient (in PyWbUtils and PyWbUtils).
19:16:25 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Linux/Unix version 8.0.38 CE build 4270059 (64 bit)
	Configuration Directory: /home/evlarch/.mysql/workbench
	Data Directory: /usr/share/mysql-workbench
	Cairo Version: 1.18.2
	OS:  x86_64
	CPU: 4x Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz (2436.100MHz) - 7,58GiB RAM
No video adapter info available
	Distribution: EndeavourOS Linux

	Fips mode enabled: no

19:17:34 [INF][wb_utils_grt.py:generateCertificates:1234]: Running SSL Wizard
Parent: {<mforms.ObjectReference> (8a7f7cee-872b-11ef-8545-240a64cf2cfb)
type = Form, valid = 1}
User Folder: /home/evlarch/.mysql/workbench
Conn Parameters: {SQL_MODE = , hostName = 127.0.0.1, password = , port = 3306, schema = , sslCA = , sslCert = , sslCipher = , sslKey = , useSSL = 1, userName = evelynn}
Conn ID: 62a42d00-872b-11ef-8545-240a64cf2cfb
19:17:34 [INF][wb_utils_grt.py:generateCertificates:1236]: Running SSL Wizard
<mforms.Form; proxy of <Swig Object of type 'mforms::Form *' at 0x73a05c569110> >
19:17:39 [INF][wb_utils_grt.py:generateCertificates:1234]: Running SSL Wizard
Parent: {<mforms.ObjectReference> (8d2b3a32-872b-11ef-8545-240a64cf2cfb)
type = Form, valid = 1}
User Folder: /home/evlarch/.mysql/workbench
Conn Parameters: {SQL_MODE = , hostName = 127.0.0.1, password = , port = 3306, schema = , sslCA = , sslCert = , sslCipher = , sslKey = , useSSL = 1, userName = root}
Conn ID: 62a42d00-872b-11ef-8545-240a64cf2cfb
19:17:39 [INF][wb_utils_grt.py:generateCertificates:1236]: Running SSL Wizard
<mforms.Form; proxy of <Swig Object of type 'mforms::Form *' at 0x73a05c585e00> >
19:17:53 [ERR][      WBContext]: The name is not activatable
19:26:37 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: Couldn't find section [mysqld] in the config file /etc/my.cnf
19:26:37 [ERR][  GRTDispatcher]: worker: task 'wizard task' has failed with error:.Couldn't find section [mysqld] in the config file /etc/my.cnf
19:27:06 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
19:27:06 [ERR][SQL Editor Form]: Your connection attempt failed for user 'evelynn' to the MySQL server at 127.0.0.1:3306:
  The name is not activatable

Please:
1 Check that MySQL is running on address 127.0.0.1
2 Check that MySQL is reachable on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the user evelynn has rights to connect to 127.0.0.1 from your address (MySQL rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from
19:34:04 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
19:34:04 [ERR][SQL Editor Form]: Your connection attempt failed for user 'evelynn' to the MySQL server at 127.0.0.1:NULL:
  The name is not activatable

Please:
1 Check that MySQL is running on address 127.0.0.1
2 Check that MySQL is reachable on port NULL (note: 3306 is the default, but this can be changed)
3 Check the user evelynn has rights to connect to 127.0.0.1 from your address (MySQL rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from
19:38:46 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
19:38:46 [ERR][SQL Editor Form]: Your connection attempt failed for user 'evelynn' to the MySQL server at 127.0.0.1:NULL:
  The name is not activatable

Please:
1 Check that MySQL is running on address 127.0.0.1
2 Check that MySQL is reachable on port NULL (note: 3306 is the default, but this can be changed)
3 Check the user evelynn has rights to connect to 127.0.0.1 from your address (MySQL rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from
19:39:30 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
19:39:30 [ERR][SQL Editor Form]: Your connection attempt failed for user 'evelynn' to the MySQL server at 127.0.0.1:NULL:
  The name is not activatable

Please:
1 Check that MySQL is running on address 127.0.0.1
2 Check that MySQL is reachable on port NULL (note: 3306 is the default, but this can be changed)
3 Check the user evelynn has rights to connect to 127.0.0.1 from your address (MySQL rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from

chikenf00t · October 10, 2024, 6:46pm

evelynn:

19:17:53 [ERR][      WBContext]: The name is not activatable
19:26:37 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: Couldn't find section [mysqld] in the config file /etc/my.cnf
19:26:37 [ERR][  GRTDispatcher]: worker: task 'wizard task' has failed with error:.Couldn't find section [mysqld] in the config file /etc/my.cnf
19:27:06 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
19:27:06 [ERR][SQL Editor Form]: Your connection attempt failed for user 'evelynn' to the MySQL server at 127.0.0.1:3306:
  The name is not activatable

Has something to do with the account according to these error logs.
Did you go through the checklist that it added to the error?

Please:
1 Check that MySQL is running on address 127.0.0.1
2 Check that MySQL is reachable on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the user evelynn has rights to connect to 127.0.0.1 from your address (MySQL rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from
19:34:04 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
19:34:04 [ERR][SQL Editor Form]: Your connection attempt failed for user 'evelynn' to the MySQL server at 127.0.0.1:NULL:
  The name is not activatable

evelynn · October 10, 2024, 9:01pm

could you provide more info on what you mean by

Did you go through the checklist that it added to the error?

chikenf00t · October 10, 2024, 9:03pm

chikenf00t:

Please:
1 Check that MySQL is running on address 127.0.0.1
2 Check that MySQL is reachable on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the user evelynn has rights to connect to 127.0.0.1 from your address (MySQL rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from
19:34:04 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
19:34:04 [ERR][SQL Editor Form]: Your connection attempt failed for user 'evelynn' to the MySQL server at 127.0.0.1:NULL:
  The name is not activatable

Referring the second half of my post

evelynn · October 10, 2024, 9:30pm

How would i “check” if the user account has the rights to connect to the server when its fine in terminal?

(I did try this with regular root as well in one of my reinstalltion attempts and got the same error i must have done smth wrong)

chikenf00t · October 10, 2024, 9:35pm

Take a look at the answer from this link

dpa-snyder commented Mar 9, 2024 •

You have to have the gnome-keyring installed and setup.
this is the fix from the same error on shiftkey.

remove github-desktop-bin
delete the GitHub Desktop folder in ~/.config
install gnome-keyring with pacman -S gnome-keyring
reinstall github-desktop-bin with the AUR package manager you use
have browser singed into github account you wish to use
launch github desktop, sign in…

works - i’m running Arch via EndeavourOS with hyprland

Hope this helps.

evelynn · October 11, 2024, 8:49am

i do already use gnomes keyring so this confuses me even further

(i will try reinstalling git, and kill the folders as described as a test)

libsecret 0.21.4-1
--
polkit 125-1
polkit-gnome 0.105-11
polkit-qt6 0.200.0-1
--
python-secretstorage 3.3.3-5

xircon · October 11, 2024, 9:26am

I know diddly squat about workbench, but in firewalld shouldn’t the ports be “trusted”.

evelynn · October 11, 2024, 12:35pm

You just made me realize that i send the same screenshot twice and didnt specify that i tried both trusted and public bzt thank you

evelynn · October 14, 2024, 5:12pm

I reinstalled the gome-keyring and libsecret along with the gnome polkit updates my system and restartet mariaDB and now its working for some reason

sudo pacman -S gnome-keyring

system · October 16, 2024, 5:13pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

MySql-Workbench cant connect to MariaDb server

dpa-snyder commented Mar 9, 2024 •