Bug 15858 - Problems connecting to mariadb
Summary: Problems connecting to mariadb
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-06 09:57 CEST by Karl Morten Ramberg
Modified: 2015-05-08 08:08 CEST (History)
4 users (show)

See Also:
Source RPM: mariadb
CVE:
Status comment:


Attachments

Description Karl Morten Ramberg 2015-05-06 09:57:08 CEST
I have installed mariadb and mysql workbench. As IDE I have tried Eclipse and Netbeans 8.02. From both IDEs connection to maria db is refused. Workbench cannot start mariadb either. There seems to be missing some parameters, and there is no documentation showing how.
From both IDEs I can easily connect to Postgres 9.4.
Furthermore in Ubuntu it works right out of the box as on win 10 and OSX (latest)


Version-Release number of selected component (if applicable):
Mageia 5 RC, maria and workbench from the repos


How reproducible:
Everytime. I have tried installing several times

Steps to Reproduce:
1.install RC
2. Install JDK maria and workbench
3. Download and install Netbeans
4. Register the database in the IDE and the errors appear


Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-05-06 10:15:40 CEST
Have you started mariadb after installing it? I'm not sure it starts automatically (although it does after a reboot)

Also, if you're trying to connect to mariadb via TCP/IP (and not a local socket), you must make sure that networking is enabled in my.cnf. Check for "skip-networking".
Comment 2 Karl Morten Ramberg 2015-05-06 11:19:40 CEST
Subject: Re: [Bug 15858] Problems starting mariadb
This is on a local machine. I have installed Ubuntu and win 10 on it and it works on those (but that is MySQL) .And yes I have done reboot, updates and reboot several times,   I can start maria db from the terminal and also from webmin, but neither Eclipse (luna) or Netbeans can connect to the database. I tried the skip networking, but no change
Comment 3 Samuel Verschelde 2015-05-06 11:28:53 CEST
Please be more precise about how you try to connect to the database. There are several ways and parameters, they all matter.

> I tried the skip networking, but no change

You mean, "I commented the line that starts with skip-networking then restarted the mysqld service, and afterwards I could still not connect"?
Samuel Verschelde 2015-05-06 11:30:44 CEST

Summary: Problems starting mariadb => Problems connecting to mariadb

Comment 4 Karl Morten Ramberg 2015-05-06 12:11:37 CEST
After reboot it worked, even though I run on a local machine. Perhaps an idea to either comment that line out in the distro or at least update documentation?
Comment 5 Samuel Verschelde 2015-05-06 12:22:27 CEST
(In reply to Karl Morten Ramberg from comment #4)
> After reboot it worked, even though I run on a local machine. Perhaps an
> idea to either comment that line out in the distro or at least update
> documentation?

Well, are you sure your IDEs and mysql-workbench are not capable to connect to localhost via local socket instead of 127.0.0.1 via tcp/ip? It used to work for me.

CCing maintainer and doc team in case they want to and can document that somewhere (or tell you about existing documentation).

To docteam : this is about skip-networking being present in my.cnf (for security reasons), and making it difficult to connect if you try to use tcp/ip connection instead of local socket.

Closing as INVALID since this is not a bug.

Status: NEW => RESOLVED
CC: (none) => alien, doc-bugs
Resolution: (none) => INVALID

Comment 6 papoteur 2015-05-08 08:08:57 CEST
For me, the best place for such an indication is in /usr/share/doc/mariadb/README.urpmi
And I think that the maintainer has a good place for doing that. 
Papoteur, for docteam.

CC: (none) => yves.brungard_mageia


Note You need to log in before you can comment on or make changes to this bug.