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

No groups to be reported (check your GNRs) - mysqld_multi does not see instances

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.2.16
    • 10.2.17
    • Configuration
    • None
    • Debian 9.5 9 - Kernel 4.9.0-6
      MariaDB 10.2.15 and 10.2.16 and 10.3

    Description

      Hi,
      we tried to setup a new database Server with Debian 9 , MariaDB 10.2 and mysqld_multi with several instances.
      We always get this message:

      #mysqld_multi report
      		 
      Reporting MariaDB servers
      		 
      No groups to be reported (check your GNRs)

      In MariadDB 10.2.14 your test Multi Instance is working:

      #msqld_multi report
      		 
      Reporting MariaDB servers
      		 
      MariaDB server from group: mysqld16 is not running

      This happens with MariaDB 10.2.15, 10.2.16 ad 10.3
      Mysqld_multi.log has no helpful entries:

      Reporting MariaDB servers
      		 
      No groups to be reported (check your GNRs)
      		 
      mysqld_multi log file version 2.20; run: Mo Aug  6 15:15:37 2018

      best regards
      Andreas

      Attachments

        1. my.cnf
          2 kB
          Tech Nik
        2. mysql_slaves.cnf
          1 kB
          Tech Nik

        Activity

          Ascending order - Click to sort in descending order
          alice Alice Sherepa added a comment -

          Please provide your .cnf files.
          I tried with a group of Mariadb 10.2.16 and 10.3.8 in Docker image of Centos 7.5, seems to work

          [root@bc1b8047d3c0 etc]# mysqld_multi report 
          Reporting MariaDB servers
          		 
          MariaDB server from group: mysqld2 is not running
          		 
          MariaDB server from group: mysqld3 is not running
          		 
          [root@bc1b8047d3c0 etc]# mysqld_multi start 2
          		 
          [root@bc1b8047d3c0 etc]# mysqld_multi start 3
          		 
          [root@bc1b8047d3c0 farm]# mysqld_multi report 
          Reporting MariaDB servers
          		 
          MariaDB server from group: mysqld2 is running
          		 
          MariaDB server from group: mysqld3 is running
          		 
          [root@bc1b8047d3c0 etc]# top -cb |grep [m]ysqld
          		 
            798 root      20   0   11828   2720   2388 S   0.0  0.0   0:00.00 /bin/sh /usr/bin/mysqld_safe --socket=/a/m1-10.2.16/dt/my.sock --port=3307 --pid_file=/a/m1-10.2.16/dt/p.id --datadir=/a/m1-10.+
          		 
            880 root      20   0 1779240  97720  18388 S   0.0  0.3   0:00.20 /usr/sbin/mysqld --basedir=/usr --datadir=/a/m1-10.2.16/dt --plugin-dir=/usr/lib64/mysql/plugin --user=root --log-error=/a/m1-10.2+
          		 
            916 root      20   0   11828   2836   2500 S   0.0  0.0   0:00.00 /bin/sh /usr/bin/mysqld_safe --socket=/a/m0-10.3.8/dt/my.sock --port=3306 --pid-file=/a/m0-10.3.8/dt/p.id --datadir=/a/m0-10.3.+
          		 
            998 root      20   0 1779240  97764  18416 S   0.0  0.3   0:00.19 /usr/sbin/mysqld --basedir=/usr --datadir=/a/m0-10.3.8/dt --plugin-dir=/usr/lib64/mysql/plugin --user=root --log-error=/a/m0-10.3.+

          alice Alice Sherepa added a comment - Please provide your .cnf files. I tried with a group of Mariadb 10.2.16 and 10.3.8 in Docker image of Centos 7.5, seems to work [root@bc1b8047d3c0 etc]# mysqld_multi report Reporting MariaDB servers MariaDB server from group: mysqld2 is not running MariaDB server from group: mysqld3 is not running [root@bc1b8047d3c0 etc]# mysqld_multi start 2 [root@bc1b8047d3c0 etc]# mysqld_multi start 3 [root@bc1b8047d3c0 farm]# mysqld_multi report Reporting MariaDB servers MariaDB server from group: mysqld2 is running MariaDB server from group: mysqld3 is running [root@bc1b8047d3c0 etc]# top -cb |grep [m]ysqld 798 root 20 0 11828 2720 2388 S 0.0 0.0 0:00.00 /bin/sh /usr/bin/mysqld_safe --socket=/a/m1-10.2.16/dt/my.sock --port=3307 --pid_file=/a/m1-10.2.16/dt/p.id --datadir=/a/m1-10.+ 880 root 20 0 1779240 97720 18388 S 0.0 0.3 0:00.20 /usr/sbin/mysqld --basedir=/usr --datadir=/a/m1-10.2.16/dt --plugin-dir=/usr/lib64/mysql/plugin --user=root --log-error=/a/m1-10.2+ 916 root 20 0 11828 2836 2500 S 0.0 0.0 0:00.00 /bin/sh /usr/bin/mysqld_safe --socket=/a/m0-10.3.8/dt/my.sock --port=3306 --pid-file=/a/m0-10.3.8/dt/p.id --datadir=/a/m0-10.3.+ 998 root 20 0 1779240 97764 18416 S 0.0 0.3 0:00.19 /usr/sbin/mysqld --basedir=/usr --datadir=/a/m0-10.3.8/dt --plugin-dir=/usr/lib64/mysql/plugin --user=root --log-error=/a/m0-10.3.+
          technik@brandad-systems.de Tech Nik added a comment -

          Hi,
          attached you can find my config files.
          Could you please try to reproduce it on a fresh debian 9 installation.
          Best regards
          Andreas

          technik@brandad-systems.de Tech Nik added a comment - Hi, attached you can find my config files. Could you please try to reproduce it on a fresh debian 9 installation. Best regards Andreas
          alice Alice Sherepa added a comment -

          thanks for the report! Reproduced on Debian 9:

          root@27b421b34a0a:/a/m1-10.2.15# mysqld_multi report
          		 
          Reporting MariaDB servers
          		 
          No groups to be reported (check your GNRs)
          		 
          root@27b421b34a0a:/a/m1-10.2.15# cat /etc/issue
          		 
          Debian GNU/Linux 9 \n \l

          alice Alice Sherepa added a comment - thanks for the report! Reproduced on Debian 9: root@27b421b34a0a:/a/m1-10.2.15# mysqld_multi report Reporting MariaDB servers No groups to be reported (check your GNRs) root@27b421b34a0a:/a/m1-10.2.15# cat /etc/issue Debian GNU/Linux 9 \n \l

          People

            serg Sergei Golubchik
            technik@brandad-systems.de Tech Nik
            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.