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

[PATCH] systemd capability for --memlock

Details

    • 10.1.9-3, 10.1.10

    Description

      As mentioned by serg in MDEV8995 comment 77779 memlock can't be achieved in system configuration because of running as User=mysql

      Referenced patch reworks implementation to expose capability IPC_LOCK to allow the unpriv mysql to achieve this functionality.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33301 memlock with systemd still not working even with MDEV-9095 fix

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8995 [PATCH] max_connections setting is ignored on start on Debian 8

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          links to

          Web Link github pull request 117

          Web Link Github revision

          Activity

            Ascending order - Click to sort in descending order
            danblack Daniel Black added a comment -

            patch as per github pull request 117

            danblack Daniel Black added a comment - patch as per github pull request 117
            svoj Sergey Vojtovich added a comment -

            serg, please review fix for this bug.

            svoj Sergey Vojtovich added a comment - serg , please review fix for this bug.
            svoj Sergey Vojtovich added a comment -

            ...second version of patch

            svoj Sergey Vojtovich added a comment - ...second version of patch
            hholzgra Hartmut Holzgraefe added a comment -

            This does not seem to work for me with 10.6.16 (on Rocky Linux 9)

            The mariadb.service file clearly has

            CapabilityBoundingSet=CAP_IPC_LOCK CAP_DAC_OVERRIDE CAP_AUDIT_WRITE

            but when requesting memlock in the configuration I'm still getting

            [Warning] Failed to lock memory. Errno: 12

            hholzgra Hartmut Holzgraefe added a comment - This does not seem to work for me with 10.6.16 (on Rocky Linux 9) The mariadb.service file clearly has CapabilityBoundingSet=CAP_IPC_LOCK CAP_DAC_OVERRIDE CAP_AUDIT_WRITE but when requesting memlock in the configuration I'm still getting [Warning] Failed to lock memory. Errno: 12
            serg Sergei Golubchik added a comment -

            please, report a new issue

            serg Sergei Golubchik added a comment - please, report a new issue

            People

              svoj Sergey Vojtovich
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.