Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-5334

Permission Error on softlink is wrong

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.0.7
    • None
    • None
    • None
    • Fedora 20

    Description

      I stopped the server, installed with yum, moved /var/lib/mysql to /data/mysql, created a softlink
      cd /var/lib
      ln -s /data/mysql .
      the I did the usual chown -R mysql:mysql mysql
      but I still keep getting this error. This is a valid and common operation y regular mysql, to reload the data directory to another drive.

      [ERROR] mysqld: Can't create/write to file '/var/lib/mysql/aria_log_control' (Errcode: 13 "Permission denied")
      [ERROR] mysqld: Got error 'Can't create file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
      [ERROR] Plugin 'Aria' init function returned error.
      [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-5378 mysql init script sets a wrong default value for datadir

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 5 older comments
            philip_38 Philip orleans added a comment -

            No, you are right. I found the issue on my new Fedora 20. I apologize.
            If you send me your ssh public key I can give you access and we we
            could reproduce the issue.
            This is my selinux
            cd /etc/selinux
            [root@fedora20 selinux]# cat config

            1. This file controls the state of SELinux on the system.
            2. SELINUX= can take one of these three values:
            3. enforcing - SELinux security policy is enforced.
            4. permissive - SELinux prints warnings instead of enforcing.
            5. disabled - No SELinux policy is loaded.
              SELINUX=disabled
            6. SELINUXTYPE= can take one of these two values:
            7. targeted - Targeted processes are protected,
            8. minimum - Modification of targeted policy. Only selected
              processes are protected.
            9. mls - Multi Level Security protection.
              SELINUXTYPE=targeted

            On Mon, Dec 2, 2013 at 4:13 PM, Elena Stepanova (JIRA)

            philip_38 Philip orleans added a comment - No, you are right. I found the issue on my new Fedora 20. I apologize. If you send me your ssh public key I can give you access and we we could reproduce the issue. This is my selinux cd /etc/selinux [root@fedora20 selinux] # cat config This file controls the state of SELinux on the system. SELINUX= can take one of these three values: enforcing - SELinux security policy is enforced. permissive - SELinux prints warnings instead of enforcing. disabled - No SELinux policy is loaded. SELINUX=disabled SELINUXTYPE= can take one of these two values: targeted - Targeted processes are protected, minimum - Modification of targeted policy. Only selected processes are protected. mls - Multi Level Security protection. SELINUXTYPE=targeted On Mon, Dec 2, 2013 at 4:13 PM, Elena Stepanova (JIRA)
            elenst Elena Stepanova added a comment -

            Here is my public key:
            https://launchpad.net/~elenst/+sshkeys

            elenst Elena Stepanova added a comment - Here is my public key: https://launchpad.net/~elenst/+sshkeys
            philip_38 Philip orleans added a comment -

            Done
            I want to send you the IP in private.
            if you can please send me a private email of do instruct me as to how
            to do this using JIRA
            Yours
            Philip

            On Mon, Dec 2, 2013 at 5:10 PM, Elena Stepanova (JIRA)

            philip_38 Philip orleans added a comment - Done I want to send you the IP in private. if you can please send me a private email of do instruct me as to how to do this using JIRA Yours Philip On Mon, Dec 2, 2013 at 5:10 PM, Elena Stepanova (JIRA)
            elenst Elena Stepanova added a comment -

            Logged, took a look, sent a reply by email.
            Summary: so far the described problem is not anyhow visible on the provided machine.

            elenst Elena Stepanova added a comment - Logged, took a look, sent a reply by email. Summary: so far the described problem is not anyhow visible on the provided machine.
            elenst Elena Stepanova added a comment -

            Hi,

            As already discussed in the email, further investigation has shown that there is a real underlying problem in how /etc/init.d/mysql script treats custom basedir/datadir settings. The bug is filed on your behalf as MDEV-5378.
            I suppose that the initial reconfiguration caused startup failure as explained in MDEV-5378; after that in attempts to fix the issue wrong changes were made to file/folder permissions which caused the pile of assorted access failures.

            So, I will close this report as a duplicate of MDEV-5378 – although the latter is newer, it is not cluttered with irrelevant information which might be confusing.

            However, I don't rule out completely that some other bugs in the mysql init script caused more access problems, so if you encounter something else that cannot be explained by MDEV-5378 description, please feel free to comment here and we'll re-open the report.

            Thanks.

            elenst Elena Stepanova added a comment - Hi, As already discussed in the email, further investigation has shown that there is a real underlying problem in how /etc/init.d/mysql script treats custom basedir/datadir settings. The bug is filed on your behalf as MDEV-5378 . I suppose that the initial reconfiguration caused startup failure as explained in MDEV-5378 ; after that in attempts to fix the issue wrong changes were made to file/folder permissions which caused the pile of assorted access failures. So, I will close this report as a duplicate of MDEV-5378 – although the latter is newer, it is not cluttered with irrelevant information which might be confusing. However, I don't rule out completely that some other bugs in the mysql init script caused more access problems, so if you encounter something else that cannot be explained by MDEV-5378 description, please feel free to comment here and we'll re-open the report. Thanks.

            People

              elenst Elena Stepanova
              philip_38 Philip orleans
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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