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

Change error messages inside code to have mariadb instead of mysql

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Fix Version/s: 10.6.2
    • Component/s: Server
    • Labels:
      None

      Description

      Error messages inside the code

      There are error messages which are composed in the code directly, particularly (but probably not only) in replication. At the very least they can appear in error logs or stderr, but possibly they can also be added to SQL errors with generic patterns, like errors passed through from an engine.

      Examples:

      client/mysql_upgrade.c:    print_error("Version check failed. Got the following error when calling "
      client/mysql_upgrade.c-                "the 'mysql' command line client", &ds_version);
      

      sql/slave.cc:      errmsg= "The slave I/O thread stops because master and slave have equal \
      sql/slave.cc-MySQL server ids; these ids must be different for replication to work (or \
      

      sql/slave.cc-  rli->report(ERROR_LEVEL, ER_SLAVE_RELAY_LOG_READ_FAILURE, NULL,
      sql/slave.cc-              ER_THD(thd, ER_SLAVE_RELAY_LOG_READ_FAILURE), "\
      sql/slave.cc-Could not parse relay log event entry. The possible reasons are: the master's \
      sql/slave.cc-binary log is corrupted (you can check this by running 'mysqlbinlog' on the \
      sql/slave.cc-binary log), the slave's relay log is corrupted (you can check this by running \
      sql/slave.cc:'mysqlbinlog' on the relay log), a network problem, or a bug in the master's \
      sql/slave.cc-or slave's MySQL code. If you want to check the master's binary log or slave's \
      sql/slave.cc-relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' \
      

      and then the corresponding test results will have to be updated, e.g.

      ./suite/rpl/r/rpl_server_id1.result:Last_IO_Error = 'Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the -
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rucha174 Rucha Deodhar
              Reporter:
              ratzpo Rasmus Johansson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration