Discovery for MariaDB (again)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2022 12:41 PM
Hi Everyone,
since this question is 3y old https://community.servicenow.com/community?id=community_question&sys_id=39f6c37edbf9b3c01cd8a345ca9619b7
I was wondering, if this is still valid. Unfortunately: no. In the meantime, MariaDB changed its processname from "mysqld" to "mariadbd" (validated on CentOS 9 Stream). So it not catched by the MySQL Pattern anymore.
So, is MariaDB Discovery already in the pipeline?
Regards,
Nick
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-14-2022 07:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-16-2022 12:06 PM
Hi Nick
did you validate discovery of mariadb from your end?
Hail
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2023 06:49 AM
I suppose the main reason is that distinguishing between MySQL and MariaDB can pose a challenge due to their shared history.
MariaDB emerged as a fork of MySQL, designed to replace it while seamlessly incorporating enhanced functionalities and performance improvements.
Consequently, the two databases exhibit many similarities, including default settings and compatible syntax.
One common aspect contributing to the confusion is their identical process name, 'mysqld' for Linux and 'mysqld.exe' for Windows, leading to MariaDB being classified as MySQL.
The second aspect is a configuration file for both databases is the same and called my.cnf
Here's an example of a basic my.cnf file used by both databases.
[mysqld]
datadir=/var/lib/mysql
socket=/var/run/mysqld/mysqld.sock
port=3306
bind-address=127.0.0.1 character-set-server=utf8mb4 [client] default- character-set=utf8mb4
Nonetheless, several methods still can help differentiate between the two:
Command-Line Client Output: By executing the "mysql --version" command, comprehensive version information is provided, along with details about the distribution.
For instance, MySQL output may appear as: "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 (Ubuntu),"
while MariaDB output may be displayed as: "mysql Ver 15.1 Distrib 10.5.12-MariaDB, for Linux (x86_64) using readline 5.1."
Package/Installation Location: The default installation directories for MySQL and MariaDB may differ, offering a potential clue for distinguishing between them.
For instance, MySQL might be found in /usr/sbin/ or C:\Program Files\MySQL, while MariaDB could be located in /usr/sbin/ or C:\Program Files\MariaDB.
Default Ports: By default, MySQL and MariaDB listen on distinct ports for incoming connections. Typically, MySQL uses port 3306, while MariaDB frequently employs port 3307.
It is essential to note that while these methods are generally reliable, certain customizations or alterations to default settings in both MySQL and MariaDB installations could complicate the distinction.