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

Server fails to start when parameter is unknown with no reference to the problem

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Duplicate
    • 10.1(EOL), 10.2(EOL)
    • N/A
    • Server, wsrep
    • None

    Description

      If you mistype a parameter or use a valid parameter but in the wrong section MariaDB fails to start logging only two rows in the error log:

      [root@tossanc 10209]# grep fantasy mh-my.cnf.10209 
      fantasy_parameter=yes
       
      [root@tossanc 10209]# mh service start 10209
      Welcome to MyHarem (c)2003-2014 By Claudio Nanni
       
      Working Basedir in: /home/myharem....
       
       
      [root@tossanc 10209]# 171107 14:44:05 mysqld_safe Logging to '/home/myharem/instances/10209/data/error.10209.log'.
      171107 14:44:05 mysqld_safe Starting mysqld daemon with databases from /home/myharem/instances/10209/data
       
      [root@tossanc 10209]# cat data/error.10209.log
      171107 14:44:05 mysqld_safe Starting mysqld daemon with databases from /home/myharem/instances/10209/data
      171107 14:44:05 mysqld_safe WSREP: Running position recovery with --disable-log-error  --pid-file='/home/myharem/instances/10209/data/tossanc-recover.pid'
       
       
      [root@tossanc 10209]# sed -i 's/^fantasy/#fantasy/g' mh-my.cnf.10209 
       
      [root@tossanc 10209]# grep fantasy mh-my.cnf.10209 
      #fantasy_parameter=yes
       
      [root@tossanc 10209]# mh service start 10209
      Welcome to MyHarem (c)2003-2014 By Claudio Nanni
       
      Working Basedir in: /home/myharem....
       
       
      [root@tossanc 10209]# 171107 14:45:20 mysqld_safe Logging to '/home/myharem/instances/10209/data/error.10209.log'.
      171107 14:45:20 mysqld_safe Starting mysqld daemon with databases from /home/myharem/instances/10209/data
       
      [root@tossanc 10209]# tail -5 data/error.10209.log
      2017-11-07 14:45:23 140481334458112 [Note] WSREP: REPL Protocols: 7 (3, 2)
      2017-11-07 14:45:23 140481334458112 [Note] WSREP: Assign initial position for certification: 0, protocol version: 3
      2017-11-07 14:45:23 140481125705472 [Note] WSREP: Service thread queue flushed.
      2017-11-07 14:45:23 140481334458112 [Note] WSREP: Synchronized with group, ready for connections
      2017-11-07 14:45:23 140481334458112 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      

      I actually encountered this problem when configuring `streamfmt` in the wrong section, [mysqld] instead of [sst].
      Since I faced many times the case that a Galera node would not join and only those two lines were added to the error log, I suspect now that in most cases was just a wrong or mistyped configuration parameter.

      Imho It would be the case to point to the reason why the server failed to start, either non existing parameter or non existing for that section.

      Attachments

        Issue Links

          Activity

            People

              anikitin Andrii Nikitin (Inactive)
              claudio.nanni Claudio Nanni
              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.