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

ERROR 1062 (23000) at line 365: Duplicate entry 'spider' for key 'PRIMARY'

Details

    Description

      Reinstalling the spider plugin after a MariaDB 10.2.13 - - > 10.2.14 upgrade fails with the following error;

      # apt-get install mariadb-plugin-spider
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      The following NEW packages will be installed:
        mariadb-plugin-spider
      0 upgraded, 1 newly installed, 0 to remove and 80 not upgraded.
      Need to get 0 B/286 kB of archives.
      After this operation, 916 kB of additional disk space will be used.
      Selecting previously unselected package mariadb-plugin-spider.
      (Reading database ... 20688 files and directories currently installed.)
      Preparing to unpack .../mariadb-plugin-spider_10.2.14+maria~xenial_amd64.deb ...
      Unpacking mariadb-plugin-spider (10.2.14+maria~xenial) ...
      Setting up mariadb-plugin-spider (10.2.14+maria~xenial) ...
      ERROR 1062 (23000) at line 365: Duplicate entry 'spider' for key 'PRIMARY'
      

      Attachments

        Activity

          jacob-mathew,
          I think it's not the point. The script should be able to handle the situation when the plugin is not installed, but an orphan record exists in mysql.plugin.

          elenst Elena Stepanova added a comment - jacob-mathew , I think it's not the point. The script should be able to handle the situation when the plugin is not installed, but an orphan record exists in mysql.plugin .

          I now understand the inconsistency that results after upgrades to MariaDB and Spider on Ubuntu. I was able to artifcially create this situation on my development machine and verified that the reported error occurs upon re-installing Spider. I have fixed the problem by making changes to the Spider installation script for recognizing and correcting the inconsistency.

          jacob-mathew Jacob Mathew (Inactive) added a comment - I now understand the inconsistency that results after upgrades to MariaDB and Spider on Ubuntu. I was able to artifcially create this situation on my development machine and verified that the reported error occurs upon re-installing Spider. I have fixed the problem by making changes to the Spider installation script for recognizing and correcting the inconsistency.

          Kentoku, please review my fix for this problem in commit 0897d81 on my branch.

          jacob-mathew Jacob Mathew (Inactive) added a comment - Kentoku, please review my fix for this problem in commit 0897d81 on my branch .

          LGTM
          It's O.K. to push.

          Kentoku Kentoku Shiba (Inactive) added a comment - LGTM It's O.K. to push.

          Fix is pushed to 10.3 and 10.2.

          jacob-mathew Jacob Mathew (Inactive) added a comment - Fix is pushed to 10.3 and 10.2.

          People

            jacob-mathew Jacob Mathew (Inactive)
            Dermot.Brereton Dermot Brereton
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.