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

Systemd not working the same as with 10.3.13

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.3.14
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
    • Environment:
      CENTOS 7.6 Kernel: 3.10.0-957.10.1.el7.x86_64

      Description

      We use our own Internal LDAP infrastructure to manage applications users. The mysql user is in LDAP but not local on any db server. In the previous version (10.3.13) I had this working in the mariadb.service unit file:

      [Unit]
      Description=MariaDB 10.3.13 database server
      Documentation=man:mysqld(8)
      Documentation=https://mariadb.com/kb/en/library/systemd/
      *Requires=nslcd.service*
      After=*nslcd.service* network.target
      

      Items in bold above were added so that the mariadb service would not start until the ldap service (nslcd.service) was up and running. This worked until the other day when I upgraded a few machines to 10.3.14. Since then this no longer works. The mariadb.service tries to start and fails because it cannot find the mysql user. Workaround is to add a local user on the affected system.

      I've compared the unit files from 10.3.13 and 103.14 and they are identical except for the Description field which should not matter.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jackpal Jack Palmadesso
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

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