[MXS-2293] Monitor fails PAM authentication with error: Plugin dialog could not be loaded - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Not a Bug
Affects Version/s: 2.3.3
Fix Version/s: N/A
Component/s: Authenticator, galeramon, Monitor
Labels:
None

Description

I enabled PAM authentication in MaxScale 2.3.3, and I'm now seeing GaleraMon fail because it can't load dialog.so. For example:

2019-01-26 03:56:11   error  : [Galera-Monitor] Failed to connect to server 'C1N1' ([172.30.0.249]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory

2019-01-26 03:56:11   error  : [Galera-Monitor] Failed to connect to server 'C1N2' ([172.30.0.32]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory

Is the MaxScale package supposed to include a file /var/lib/plugin/dialog.so? It does not seem to:

[ec2-user@ip-172-30-0-106 ~]$ rpm -q maxscale

maxscale-2.3.3-1.x86_64

[ec2-user@ip-172-30-0-106 ~]$ rpm -ql maxscale | grep dialog

[ec2-user@ip-172-30-0-106 ~]$ ls -l /var/lib/plugin/dialog.so

ls: cannot access /var/lib/plugin/dialog.so: No such file or directory

I know that the MariaDB-common package includes a dialog.so file, but that is not in /var/lib/plugin either:

[ec2-user@ip-172-30-0-106 ~]$ ls -l /usr/lib64/mysql/plugin/dialog.so

-rwxr-xr-x. 1 root root 47656 Jan  4 10:53 /usr/lib64/mysql/plugin/dialog.so

[ec2-user@ip-172-30-0-106 ~]$ rpm -qf /usr/lib64/mysql/plugin/dialog.so

MariaDB-common-10.3.12-1.el7.centos.x86_64

Is the maxscale package supposed to install its own dialog.so, or is it supposed to have a dependency on the MariaDB-common package, and load the dialog.so plugin from /usr/lib64/mysql/plugin/?

I was able to workaround the problem with:

[ec2-user@ip-172-30-0-106 ~]$ sudo mkdir -p /var/lib/plugin

[ec2-user@ip-172-30-0-106 ~]$ sudo install --mode=0755 /usr/lib64/mysql/plugin/dialog.so /var/lib/plugin/

[ec2-user@ip-172-30-0-106 ~]$ sudo systemctl restart maxscale

Attachments

Issue Links

is caused by

MXS-2308 Change default for connector_plugindir

Closed

relates to

MXS-2294 Document how to configure user and group mapping for PAM authenticators

Closed

MXS-2292 Allow PAM user and group mapping to work with more specific host than '%'

Closed

Activity

Ascending order - Click to sort in descending order

Geoff Montee (Inactive) created issue - 2019-01-26 09:06

Geoff Montee (Inactive) made changes - 2019-01-26 09:06

Field	Original Value	New Value
Link		This issue relates to ~~MXS-2292~~ [ ~~MXS-2292~~ ]

Geoff Montee (Inactive) made changes - 2019-01-26 09:13

Description

I enabled PAM authentication in MaxScale 2.3.3, and I'm now seeing GaleraMon fail because it can't load dialog.so. For example:

{noformat}
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N1' ([172.30.0.249]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N2' ([172.30.0.32]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
{noformat}

Is the MaxScale package supposed to include a file /var/lib/plugin/dialog.so? It does not seem to:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ rpm -q maxscale
maxscale-2.3.3-1.x86_64
[ec2-user@ip-172-30-0-106 ~]$ rpm -ql maxscale | grep dialog
[ec2-user@ip-172-30-0-106 ~]$ ls -l /var/lib/plugin/dialog.so
ls: cannot access /var/lib/plugin/dialog.so: No such file or directory
{noformat}

I know that the MariaDB-common package includes a dialog.so file, but that is not in /var/lib/plugin either:

{noformat}
[ec2-user@ip-172-30-0-32 ~]$ ls -l /usr/lib64/mysql/plugin/dialog.so
-rwxr-xr-x 1 root root 51968 Oct 31 18:07 /usr/lib64/mysql/plugin/dialog.so
[ec2-user@ip-172-30-0-32 ~]$ rpm -qf /usr/lib64/mysql/plugin/dialog.so
MariaDB-common-10.1.37-1.el7.centos.x86_64
{noformat}

Is the maxscale package supposed to install its own dialog.so, or is it supposed to have a dependency on the MariaDB-common package, and load the dialog.so plugin from /usr/lib64/mysql/plugin/?

I enabled PAM authentication in MaxScale 2.3.3, and I'm now seeing GaleraMon fail because it can't load dialog.so. For example:

{noformat}
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N1' ([172.30.0.249]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N2' ([172.30.0.32]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
{noformat}

Is the MaxScale package supposed to include a file /var/lib/plugin/dialog.so? It does not seem to:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ rpm -q maxscale
maxscale-2.3.3-1.x86_64
[ec2-user@ip-172-30-0-106 ~]$ rpm -ql maxscale | grep dialog
[ec2-user@ip-172-30-0-106 ~]$ ls -l /var/lib/plugin/dialog.so
ls: cannot access /var/lib/plugin/dialog.so: No such file or directory
{noformat}

I know that the MariaDB-common package includes a dialog.so file, but that is not in /var/lib/plugin either:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ ls -l /usr/lib64/mysql/plugin/dialog.so
-rwxr-xr-x. 1 root root 47656 Jan 4 10:53 /usr/lib64/mysql/plugin/dialog.so
[ec2-user@ip-172-30-0-106 ~]$ rpm -qf /usr/lib64/mysql/plugin/dialog.so
MariaDB-common-10.3.12-1.el7.centos.x86_64
{noformat}

Is the maxscale package supposed to install its own dialog.so, or is it supposed to have a dependency on the MariaDB-common package, and load the dialog.so plugin from /usr/lib64/mysql/plugin/?

Geoff Montee (Inactive) made changes - 2019-01-26 09:16

Description

I enabled PAM authentication in MaxScale 2.3.3, and I'm now seeing GaleraMon fail because it can't load dialog.so. For example:

{noformat}
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N1' ([172.30.0.249]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N2' ([172.30.0.32]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
{noformat}

Is the MaxScale package supposed to include a file /var/lib/plugin/dialog.so? It does not seem to:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ rpm -q maxscale
maxscale-2.3.3-1.x86_64
[ec2-user@ip-172-30-0-106 ~]$ rpm -ql maxscale | grep dialog
[ec2-user@ip-172-30-0-106 ~]$ ls -l /var/lib/plugin/dialog.so
ls: cannot access /var/lib/plugin/dialog.so: No such file or directory
{noformat}

I know that the MariaDB-common package includes a dialog.so file, but that is not in /var/lib/plugin either:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ ls -l /usr/lib64/mysql/plugin/dialog.so
-rwxr-xr-x. 1 root root 47656 Jan 4 10:53 /usr/lib64/mysql/plugin/dialog.so
[ec2-user@ip-172-30-0-106 ~]$ rpm -qf /usr/lib64/mysql/plugin/dialog.so
MariaDB-common-10.3.12-1.el7.centos.x86_64
{noformat}

Is the maxscale package supposed to install its own dialog.so, or is it supposed to have a dependency on the MariaDB-common package, and load the dialog.so plugin from /usr/lib64/mysql/plugin/?

I enabled PAM authentication in MaxScale 2.3.3, and I'm now seeing GaleraMon fail because it can't load dialog.so. For example:

{noformat}
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N1' ([172.30.0.249]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
2019-01-26 03:56:11 error : [Galera-Monitor] Failed to connect to server 'C1N2' ([172.30.0.32]:3306) when checking monitor user credentials and permissions: Plugin dialog could not be loaded: /var/lib/plugin/dialog.so: cannot open shared object file: No such file or directory
{noformat}

Is the MaxScale package supposed to include a file /var/lib/plugin/dialog.so? It does not seem to:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ rpm -q maxscale
maxscale-2.3.3-1.x86_64
[ec2-user@ip-172-30-0-106 ~]$ rpm -ql maxscale | grep dialog
[ec2-user@ip-172-30-0-106 ~]$ ls -l /var/lib/plugin/dialog.so
ls: cannot access /var/lib/plugin/dialog.so: No such file or directory
{noformat}

I know that the MariaDB-common package includes a dialog.so file, but that is not in /var/lib/plugin either:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ ls -l /usr/lib64/mysql/plugin/dialog.so
-rwxr-xr-x. 1 root root 47656 Jan 4 10:53 /usr/lib64/mysql/plugin/dialog.so
[ec2-user@ip-172-30-0-106 ~]$ rpm -qf /usr/lib64/mysql/plugin/dialog.so
MariaDB-common-10.3.12-1.el7.centos.x86_64
{noformat}

Is the maxscale package supposed to install its own dialog.so, or is it supposed to have a dependency on the MariaDB-common package, and load the dialog.so plugin from /usr/lib64/mysql/plugin/?

I was able to workaround the problem with:

{noformat}
[ec2-user@ip-172-30-0-106 ~]$ sudo mkdir -p /var/lib/plugin
[ec2-user@ip-172-30-0-106 ~]$ sudo install --mode=0755 /usr/lib64/mysql/plugin/dialog.so /var/lib/plugin/
[ec2-user@ip-172-30-0-106 ~]$ sudo systemctl restart maxscale
{noformat}

Geoff Montee (Inactive) made changes - 2019-01-26 09:53

Link

This issue relates to ~~MXS-2294~~ [ ~~MXS-2294~~ ]

Geoff Montee (Inactive) made changes - 2019-01-26 10:00

Summary

Monitor fails with PAM authentication with error: Plugin dialog could not be loaded

Monitor fails PAM authentication with error: Plugin dialog could not be loaded

markus makela added a comment - 2019-01-28 07:45

Did the monitor user use PAM authentication as well? If it didn't, I'd expect it to work.

markus makela added a comment - 2019-01-28 07:45 Did the monitor user use PAM authentication as well? If it didn't, I'd expect it to work.

Geoff Montee (Inactive) added a comment - 2019-01-28 08:47

Yeah, the monitor user used PAM authentication. If you want all of the details, it's the configuration that I used in ~~MXS-2294~~.

Geoff Montee (Inactive) added a comment - 2019-01-28 08:47 Yeah, the monitor user used PAM authentication. If you want all of the details, it's the configuration that I used in MXS-2294 .

markus makela added a comment - 2019-01-30 11:50

Maybe this can be fixed by adjusting connector_plugindir and installing the required libraries?

markus makela added a comment - 2019-01-30 11:50 Maybe this can be fixed by adjusting connector_plugindir and installing the required libraries?

Geoff Montee (Inactive) added a comment - 2019-01-30 18:57

Pointing connector_plugindir to the proper location solved the issue:

[ec2-user@ip-172-30-0-106 ~]$ grep "connector_plugindir" /etc/maxscale.cnf

connector_plugindir=/usr/lib64/mysql/plugin/

[ec2-user@ip-172-30-0-106 ~]$ sudo rm /var/lib/plugin/dialog.so

[ec2-user@ip-172-30-0-106 ~]$ sudo systemctl start maxscale

Is there a specific reason that connector_plugindir defaults to /var/lib/plugin? I think it should default to the location where the MariaDB-common package installs authentication plugins on the specific OS. On RHEL/CentOS, that's /usr/lib64/mysql/plugin/:

[ec2-user@ip-172-30-0-106 ~]$ sudo rpm -q MariaDB-common

MariaDB-common-10.3.12-1.el7.centos.x86_64

[ec2-user@ip-172-30-0-106 ~]$ sudo rpm -q MariaDB-common --list | grep "plugin"

/usr/lib64/mysql/plugin

/usr/lib64/mysql/plugin/auth_gssapi_client.so

/usr/lib64/mysql/plugin/caching_sha2_password.so

/usr/lib64/mysql/plugin/client_ed25519.so

/usr/lib64/mysql/plugin/dialog.so

/usr/lib64/mysql/plugin/mysql_clear_password.so

/usr/lib64/mysql/plugin/sha256_password.so

Geoff Montee (Inactive) added a comment - 2019-01-30 18:57 Pointing connector_plugindir to the proper location solved the issue: [ec2-user@ip-172-30-0-106 ~]$ grep "connector_plugindir" /etc/maxscale.cnf connector_plugindir=/usr/lib64/mysql/plugin/ [ec2-user@ip-172-30-0-106 ~]$ sudo rm /var/lib/plugin/dialog.so [ec2-user@ip-172-30-0-106 ~]$ sudo systemctl start maxscale Is there a specific reason that connector_plugindir defaults to /var/lib/plugin? I think it should default to the location where the MariaDB-common package installs authentication plugins on the specific OS. On RHEL/CentOS, that's /usr/lib64/mysql/plugin/: [ec2-user@ip-172-30-0-106 ~]$ sudo rpm -q MariaDB-common MariaDB-common-10.3.12-1.el7.centos.x86_64 [ec2-user@ip-172-30-0-106 ~]$ sudo rpm -q MariaDB-common --list | grep "plugin" /usr/lib64/mysql/plugin /usr/lib64/mysql/plugin/auth_gssapi_client.so /usr/lib64/mysql/plugin/caching_sha2_password.so /usr/lib64/mysql/plugin/client_ed25519.so /usr/lib64/mysql/plugin/dialog.so /usr/lib64/mysql/plugin/mysql_clear_password.so /usr/lib64/mysql/plugin/sha256_password.so

Geoff Montee (Inactive) made changes - 2019-01-30 19:18

Link

This issue is caused by ~~MXS-2308~~ [ ~~MXS-2308~~ ]

Geoff Montee (Inactive) added a comment - 2019-01-30 19:20

I created ~~MXS-2308~~ about potentially changing the default connector_plugindir.

Geoff Montee (Inactive) added a comment - 2019-01-30 19:20 I created MXS-2308 about potentially changing the default connector_plugindir.

Geoff Montee (Inactive) made changes - 2019-01-30 19:20

Fix Version/s		N/A [ 22001 ]
Resolution		Not a Bug [ 6 ]
Status	Open [ 1 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2021-12-06 21:31

Workflow

MariaDB v3 [ 92070 ]

MariaDB v4 [ 138353 ]

Jira Automation (IT) made changes - 2024-07-03 21:37

Zendesk Related Tickets

139992

People

Assignee:: Esa Korhonen

Reporter:: Geoff Montee (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2019-01-26 09:06

Updated:: 2024-07-07 17:14

Resolved:: 2019-01-30 19:20

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB MaxScale

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration