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

Wrong systemd section name in comment within mariadb.service

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.2.8
    • N/A
    • Scripts & Clients
    • None
    • Linux with systemd

    Description

      The following comment in mariadb.service says that the [service] section should be used to add values to the MYSQLD_OPTS environment variable. This doesn't work though, it has to be [Service] with an upper case 'S'

      # Start main service
      		 
      # MYSQLD_OPTS here is for users to set in /etc/systemd/system/mariadb.service.d/MY_SPECIAL.conf
      		 
      # Use the [service] section and Environment="MYSQLD_OPTS=...".
      		 
      # This isn't a replacement for my.cnf.
      		 
      # _WSREP_NEW_CLUSTER is for the exclusive use of the script galera_new_cluster
      		 
      ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13809 Wrong systemd section name in comment within mariadb.service

          • Major - Major loss of function.
          • Closed

          Activity

            hholzgra Hartmut Holzgraefe added a comment -

            Duplicate of MDEV-13809. I re-submitted after getting this error:

            ""Exception occurred: com.atlassian.jira.exception.DataAccessException: java.sql.SQLNonTransientConnectionException: Could not read resultset: unexpected end of stream, read 0 bytes from 4 Query is : set autocommit=0""

            but apparently the error only happened after creating the issue, when trying to display results.

            hholzgra Hartmut Holzgraefe added a comment - Duplicate of MDEV-13809 . I re-submitted after getting this error: ""Exception occurred: com.atlassian.jira.exception.DataAccessException: java.sql.SQLNonTransientConnectionException: Could not read resultset: unexpected end of stream, read 0 bytes from 4 Query is : set autocommit=0"" but apparently the error only happened after creating the issue, when trying to display results.

            People

              Unassigned Unassigned
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.