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

mariadb 10.0.* /etc/init.d/mysql start Failed ?

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.0.20
    • 10.0.20
    • Scripts & Clients
    • None
    • CentOS 5.6, MariaDB Server 10.0.20

    Description

      when use mysql start scrit , after 15 minutes , show start failed:

      # /etc/init.d/mysql start
      Starting MySQL....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................[FAILED]

      But, mysql error log show , mysqld already normal start .

      151101 18:00:40 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.0.20-MariaDB'  socket: '/home/maria20/data/mysql.sock'  port: 3306  MariaDB Server
      2015-11-01 18:00:40 4e209940 InnoDB: Buffer pool(s) load completed at 151101 18:00:40

      mysql client access normal too, if use mysqld_safe --defaults-file=/etc/my.cnf.d/server.cnf , mysqld service normal start . not error

      Attachments

        Activity

          sysdljr,

          If it happens all the time, the most common reason is that your mysqladmin settings, either the socket or the TCP host/port if you are using TCP protocol for mysqld, don't match those of mysqld.
          If it was a one-time thing, then you probably hit some kind of a race-condition, when the server was started twice, or when a socket was removed by an accident.

          If you are sure neither of those was the case, please provide your config files (all of them), and the complete error log.

          Thanks.

          elenst Elena Stepanova added a comment - sysdljr , If it happens all the time, the most common reason is that your mysqladmin settings, either the socket or the TCP host/port if you are using TCP protocol for mysqld, don't match those of mysqld . If it was a one-time thing, then you probably hit some kind of a race-condition, when the server was started twice, or when a socket was removed by an accident. If you are sure neither of those was the case, please provide your config files (all of them), and the complete error log. Thanks.
          sysdljr sysdljr added a comment -

          reason: mysqladmin setting problem. It is OK now.
          Thank you very much

          sysdljr sysdljr added a comment - reason: mysqladmin setting problem. It is OK now. Thank you very much

          People

            Unassigned Unassigned
            sysdljr sysdljr
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.