[MXS-3346] When using --basedir, mysql/plugin dir needs to be writable Created: 2020-12-18  Updated: 2021-04-19  Resolved: 2021-01-14

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.4.15, 2.5.7

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-122

 Description    

# sudo -u maxscale bin/maxscale --basedir=/MARIADB
 
alert  : Opening file '/MARIADB/var//mysql/plugin' for writing failed.: Permission denied.
 
alert  : MaxScale doesn't have write permission to '/MARIADB/var//mysql/plugin'.

Looking at strace output, access() checks on the plugin dir path only occur when the --basedir option is actually used.

That's why it's not a problem that the default /var/lib64/mysql/plugin is not writable for the maxscale user when using default paths, esp. when using standard package installs.

It only becomes a problem when trying to use the binary tarball, and having all paths local for a non-root install ...

 Comments   
Comment by markus makela [ 2021-01-13 ]

Fixed the permission check and corrected the path used for the plugin directory when --basedir is used. Now the tarball installation will correctly look for the connector plugins in the correct place (e.g. lib64/mysql/plugin/ for CentOS).

Generated at Thu Feb 08 04:20:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.