Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-8701

puppetlabs-mysql : Changes introduced to my.cnf after MySQL rerstart

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: mysql
    • Labels:
      None
    • Environment:

      Ubuntu 16 and Ubuntu 18.

      Puppet Versions 3.4.3

      puppetlabs-mysql versions 5.4.0 and 8.0.0

    • Template:
      MODULES Bug Template
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Whenever there is change to my.cnf affecting ibdata file size mysql won't restart afterwards. You will get following error:

       

      2019-02-26T15:44:40.937781Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 768 pages (rounded down to MB) than specified in the .cnf file: initial 64000 pages, max 0 (relevant if non-zero) pages!
      2019-02-26T15:44:40.937817Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error

       

      Reason for that is this:

      1) MySQL gets installed with default my.cnf provided by Ubuntu

      2) It gets started and MySQL initializes ibdata files

      3) Puppet updates my.cnf with incompatible settings

      After deployment MySQL is running fine because it uses old settings. After restart/reload it tries to use new one that is incompatible with already created ibdata files.

       

      Solution would be:

      1) Install MySQL but don't start it

      2) Update my.cnf

      3) Start mysqld

       

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            mmargula Michał Margula
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support