Skip to main content
ONTAP MetroCluster
本繁體中文版使用機器翻譯,譯文僅供參考,若與英文版本牴觸,應以英文版本為準。

安裝 MetroCluster tiebreaker 1.5 相依性

貢獻者

視主機 Linux 作業系統而定、您必須先安裝 MySQL 或 MariaDB 伺服器、才能安裝或升級 tiebreaker 軟體。

步驟
  1. 安裝 JDK

  2. 安裝及設定Vault

  3. 安裝MySQL或MariaDB伺服器:

    如果Linux主機是

    然後…​

    Red Hat Enterprise Linux 7/CentOS 7.

    Red Hat Enterprise Linux 8

安裝 JDK

在安裝或升級 tiebreaker 軟體之前、您必須在主機系統上安裝 JDK 。Tiebreaker 1.5 及更新版本支援 OpenJDK 17 、 18 或 19 。

步驟
  1. 以「root」使用者或可變更為進階權限模式的Sudo使用者身分登入。

    login as: root
    root@mcctb's password:
    Last login: Fri Jan  8 21:33:00 2017 from host.domain.com
  2. 檢查可用的 JDK 版本:

    yum search openjdk

  3. 安裝 JDK 17 、 18 或 19 。

    下列命令會安裝 JDK 17 :

    yum install java-17-openjdk

  4. 驗證安裝:

    java -version

    成功安裝時會顯示下列輸出:

    openjdk version "17.0.2" 2022-01-18 LTS
    OpenJDK Runtime Environment 21.9 (build 17.0.2+8-LTS)
    OpenJDK 64-Bit Server VM 21.9 (build 17.0.2+8-LTS, mixed mode, sharing)

安裝及設定Vault

如果您沒有或想要使用本機Vault伺服器、則必須安裝Vault。您可以參閱本標準程序來安裝Vault、或參閱《橋式安裝說明》以取得替代準則。

註 如果您的網路中有Vault伺服器、您可以設定MetroCluster 使用該Vault安裝的還原斷路器主機。如果您這麼做、就不需要在主機上安裝 Vault 。
步驟
  1. 瀏覽至 /bin 目錄:

    [root@mcctb] cd /bin
  2. 下載Vault壓縮檔。

    [root@mcctb /bin]#  curl -sO https://releases.hashicorp.com/vault/1.12.2/vault_1.12.2_linux_amd64.zip
  3. 解壓縮Vault檔案。

    [root@mcctb /bin]# unzip vault_1.12.2_linux_amd64.zip
    Archive:  vault_1.12.2_linux_amd64.zip
      inflating: vault
  4. 驗證安裝。

    [root@mcctb /bin]# vault -version
    Vault v1.12.2 (415e1fe3118eebd5df6cb60d13defdc01aa17b03), built 2022-11-23T12:53:46Z
  5. 瀏覽至 /root 目錄:

    [root@mcctb /bin] cd /root
  6. 在下建立 Vault 組態檔案 /root 目錄。

    [root@mcctb ~] 提示、複製並執行下列命令以建立 config.hcl 檔案:

    # cat > config.hcl << EOF
     storage "file" {
      address = "127.0.0.1:8500"
      path    = "/mcctb_vdata/data"
     }
     listener "tcp" {
       address     = "127.0.0.1:8200"
       tls_disable = 1
     }
    EOF
  7. 啟動Vault伺服器:

    [root@mcctb ~] vault server -config config.hcl &
  8. 匯出Vault位址。

    [root@mcctb ~]# export VAULT_ADDR="http://127.0.0.1:8200"
  9. 初始化Vault。

    [root@mcctb ~]# vault operator init
    2022-12-15T14:57:22.113+0530 [INFO]  core: security barrier not initialized
    2022-12-15T14:57:22.113+0530 [INFO]  core: seal configuration missing, not initialized
    2022-12-15T14:57:22.114+0530 [INFO]  core: security barrier not initialized
    2022-12-15T14:57:22.116+0530 [INFO]  core: security barrier initialized: stored=1 shares=5 threshold=3
    2022-12-15T14:57:22.118+0530 [INFO]  core: post-unseal setup starting
    2022-12-15T14:57:22.137+0530 [INFO]  core: loaded wrapping token key
    2022-12-15T14:57:22.137+0530 [INFO]  core: Recorded vault version: vault version=1.12.2 upgrade time="2022-12-15 09:27:22.137200412 +0000 UTC" build date=2022-11-23T12:53:46Z
    2022-12-15T14:57:22.137+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
    2022-12-15T14:57:22.137+0530 [INFO]  core: no mounts; adding default mount table
    2022-12-15T14:57:22.143+0530 [INFO]  core: successfully mounted backend: type=cubbyhole version="" path=cubbyhole/
    2022-12-15T14:57:22.144+0530 [INFO]  core: successfully mounted backend: type=system version="" path=sys/
    2022-12-15T14:57:22.144+0530 [INFO]  core: successfully mounted backend: type=identity version="" path=identity/
    2022-12-15T14:57:22.148+0530 [INFO]  core: successfully enabled credential backend: type=token version="" path=token/ namespace="ID: root. Path: "
    2022-12-15T14:57:22.149+0530 [INFO]  rollback: starting rollback manager
    2022-12-15T14:57:22.149+0530 [INFO]  core: restoring leases
    2022-12-15T14:57:22.150+0530 [INFO]  expiration: lease restore complete
    2022-12-15T14:57:22.150+0530 [INFO]  identity: entities restored
    2022-12-15T14:57:22.150+0530 [INFO]  identity: groups restored
    2022-12-15T14:57:22.151+0530 [INFO]  core: usage gauge collection is disabled
    2022-12-15T14:57:23.385+0530 [INFO]  core: post-unseal setup complete
    2022-12-15T14:57:23.387+0530 [INFO]  core: root token generated
    2022-12-15T14:57:23.387+0530 [INFO]  core: pre-seal teardown starting
    2022-12-15T14:57:23.387+0530 [INFO]  rollback: stopping rollback manager
    2022-12-15T14:57:23.387+0530 [INFO]  core: pre-seal teardown complete
    Unseal Key 1: <unseal_key_1_id>
    Unseal Key 2: <unseal_key_2_id>
    Unseal Key 3: <unseal_key_3_id>
    Unseal Key 4: <unseal_key_4_id>
    Unseal Key 5: <unseal_key_5_id>
    
    Initial Root Token: <initial_root_token_id>
    
    
    Vault initialized with 5 key shares and a key threshold of 3. Please securely
    distribute the key shares printed above. When the Vault is re-sealed,
    restarted, or stopped, you must supply at least 3 of these keys to unseal it
    before it can start servicing requests.
    
    Vault does not store the generated root key. Without at least 3 keys to
    reconstruct the root key, Vault will remain permanently sealed!
    
    It is possible to generate new unseal keys, provided you have a quorum of
    existing unseal keys shares. See "vault operator rekey" for more information.
    重要 您必須將金鑰 ID 和初始根權杖記錄並儲存在安全位置、以便稍後在程序中使用。
  10. 匯出Vault根憑證。

    [root@mcctb ~]#  export VAULT_TOKEN="<initial_root_token_id>"
  11. 使用建立的五個金鑰中的任何三個來解除保存 Vault 的密封。

    您必須執行 vault operator unseal 三個按鍵的命令:

    1. 使用第一個金鑰來解除保存資料保險箱的密封:

      [root@mcctb ~]# vault operator unseal
      Unseal Key (will be hidden):
      Key                Value
      ---                -----
      Seal Type          shamir
      Initialized        true
      Sealed             true
      Total Shares       5
      Threshold          3
      Unseal Progress    1/3
      Unseal Nonce       <unseal_key_1_id>
      Version            1.12.2
      Build Date         2022-11-23T12:53:46Z
      Storage Type       file
      HA Enabled         false
    2. 使用第二個金鑰來解除保存資料保險箱的密封:

      [root@mcctb ~]# vault operator unseal
      Unseal Key (will be hidden):
      Key                Value
      ---                -----
      Seal Type          shamir
      Initialized        true
      Sealed             true
      Total Shares       5
      Threshold          3
      Unseal Progress    2/3
      Unseal Nonce       <unseal_key_2_id>
      Version            1.12.2
      Build Date         2022-11-23T12:53:46Z
      Storage Type       file
      HA Enabled         false
    3. 使用第三個金鑰來解除保存資料保險箱的密封:

      [root@mcctb ~]# vault operator unseal
      Unseal Key (will be hidden):
      2022-12-15T15:15:00.980+0530 [INFO]  core.cluster-listener.tcp: starting listener: listener_address=127.0.0.1:8201
      2022-12-15T15:15:00.980+0530 [INFO]  core.cluster-listener: serving cluster requests: cluster_listen_address=127.0.0.1:8201
      2022-12-15T15:15:00.981+0530 [INFO]  core: post-unseal setup starting
      2022-12-15T15:15:00.981+0530 [INFO]  core: loaded wrapping token key
      2022-12-15T15:15:00.982+0530 [INFO]  core: successfully setup plugin catalog: plugin-directory=""
      2022-12-15T15:15:00.983+0530 [INFO]  core: successfully mounted backend: type=system version="" path=sys/
      2022-12-15T15:15:00.984+0530 [INFO]  core: successfully mounted backend: type=identity version="" path=identity/
      2022-12-15T15:15:00.984+0530 [INFO]  core: successfully mounted backend: type=cubbyhole version="" path=cubbyhole/
      2022-12-15T15:15:00.986+0530 [INFO]  core: successfully enabled credential backend: type=token version="" path=token/ namespace="ID: root. Path: "
      2022-12-15T15:15:00.986+0530 [INFO]  rollback: starting rollback manager
      2022-12-15T15:15:00.987+0530 [INFO]  core: restoring leases
      2022-12-15T15:15:00.987+0530 [INFO]  expiration: lease restore complete
      2022-12-15T15:15:00.987+0530 [INFO]  identity: entities restored
      2022-12-15T15:15:00.987+0530 [INFO]  identity: groups restored
      2022-12-15T15:15:00.988+0530 [INFO]  core: usage gauge collection is disabled
      2022-12-15T15:15:00.989+0530 [INFO]  core: post-unseal setup complete
      2022-12-15T15:15:00.989+0530 [INFO]  core: vault is unsealed
      Key             Value
      ---             -----
      Seal Type       shamir
      Initialized     true
      Sealed          false
      Total Shares    5
      Threshold       3
      Version         1.12.2
      Build Date      2022-11-23T12:53:46Z
      Storage Type    file
      Cluster Name    vault-cluster
      Cluster ID      <cluster_id>
      HA Enabled      false
  12. 確認Vault密封狀態為假。

    [root@mcctb ~]# vault status
    Key             Value
    ---             -----
    Seal Type       shamir
    Initialized     true
    Sealed          false
    Total Shares    5
    Threshold       3
    Version         1.12.2
    Build Date      2022-11-23T12:53:46Z
    Storage Type    file
    Cluster Name    vault-cluster
    Cluster ID      <cluster_id>
    HA Enabled      false
  13. 將 Vault 服務設定為開機時啟動。

    1. 執行下列命令: cd /etc/systemd/system

      [root@mcctb ~]#  cd /etc/systemd/system
    2. [root@mcctb system] 提示、複製並執行下列命令以建立 Vault 服務檔案。

      # cat > vault.service << EOF
      [Unit]
      Description=Vault Service
      After=mariadb.service
      
      [Service]
      Type=forking
      ExecStart=/usr/bin/vault server -config /root/config.hcl &
      Restart=on-failure
      
      [Install]
      WantedBy=multi-user.target
      EOF
    3. 執行下列命令: systemctl daemon-reload

      [root@mcctb system]#  systemctl daemon-reload
    4. 執行下列命令: systemctl enable vault.service

      [root@mcctb system]#  systemctl enable vault.service
      Created symlink /etc/systemd/system/multi-user.target.wants/vault.service → /etc/systemd/system/vault.service.
      註 安裝MetroCluster 完ESITiebreaker時、系統會提示您使用此功能。如果您想要變更解封Vault的方法、則需要解除安裝並重新安裝MetroCluster 還原器軟體。

在 Red Hat Enterprise Linux 7 或 CentOS 7 上安裝 MySQL Server 5.5.30 或更新版本和 5.6.x 版本

安裝或升級Tiebreaker軟體之前、您必須先在主機系統上安裝MySQL Server 5.5.30或更新版本及5.6.x版本。對於 Red Hat Enterprise Linux 8 、 安裝 MariaDB 伺服器

步驟
  1. 以root使用者或可變更為進階權限模式的Sudo使用者身分登入。

    login as: root
    root@mcctb's password:
    Last login: Fri Jan  8 21:33:00 2016 from host.domain.com
  2. 將MySQL儲存庫新增至主機系統:

    [root@mcctb ~]# yum localinstall https://dev.mysql.com/get/mysql57-community-release-el6-11.noarch.rpm`

    Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
    Setting up Local Package Process
    Examining /var/tmp/yum-root-LLUw0r/mysql-community-release-el6-5.noarch.rpm: mysql-community-release-el6-5.noarch
    Marking /var/tmp/yum-root-LLUw0r/mysql-community-release-el6-5.noarch.rpm to be installed
    Resolving Dependencies
    --> Running transaction check
    ---> Package mysql-community-release.noarch 0:el6-5 will be installed
    --> Finished Dependency Resolution
    Dependencies Resolved
    ================================================================================
    Package               Arch   Version
                                        Repository                             Size
    ================================================================================
    Installing:
    mysql-community-release
                           noarch el6-5 /mysql-community-release-el6-5.noarch 4.3 k
    Transaction Summary
    ================================================================================
    Install       1 Package(s)
    Total size: 4.3 k
    Installed size: 4.3 k
    Is this ok [y/N]: y
    Downloading Packages:
    Running rpm_check_debug
    Running Transaction Test
    Transaction Test Succeeded
    Running Transaction
      Installing : mysql-community-release-el6-5.noarch                         1/1
      Verifying  : mysql-community-release-el6-5.noarch                         1/1
    Installed:
      mysql-community-release.noarch 0:el6-5
    Complete!
  3. 停用MySQL 57儲存庫:

    [root@mcctb ~]# yum-config-manager -disablemysql57-community

  4. 啟用MySQL 56儲存庫:

    [root@mcctb ~]# yum-config-manager --enable mysql56-community

  5. 啟用儲存庫:

    [root@mcctb ~]# yum repolist enabled| grep "mysql.-community.

    mysql-connectors-community           MySQL Connectors Community            21
    mysql-tools-community                MySQL Tools Community                 35
    mysql56-community                    MySQL 5.6 Community Server           231
  6. 安裝MySQL社群伺服器:

    [root@mcctb ~]# yum install mysql-community-server'

    Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
    This system is not registered to Red Hat Subscription Management. You can use subscription-manager
    to register.
    Setting up Install Process
    Resolving Dependencies
    --> Running transaction check
     .....Output truncated.....
    ---> Package mysql-community-libs-compat.x86_64 0:5.6.29-2.el6 will be obsoleting
    --> Finished Dependency Resolution
    Dependencies Resolved
    ==============================================================================
    Package                          Arch   Version       Repository          Size
    ==============================================================================
    Installing:
     mysql-community-client         x86_64  5.6.29-2.el6  mysql56-community  18  M
         replacing  mysql.x86_64 5.1.71-1.el6
     mysql-community-libs           x86_64  5.6.29-2.el6  mysql56-community  1.9 M
         replacing  mysql-libs.x86_64 5.1.71-1.el6
     mysql-community-libs-compat    x86_64  5.6.29-2.el6  mysql56-community  1.6 M
         replacing  mysql-libs.x86_64 5.1.71-1.el6
     mysql-community-server         x86_64  5.6.29-2.el6  mysql56-community  53  M
         replacing  mysql-server.x86_64 5.1.71-1.el6
    Installing for dependencies:
    mysql-community-common          x86_64  5.6.29-2.el6  mysql56-community   308 k
    
    Transaction Summary
    ===============================================================================
    Install       5 Package(s)
    Total download size: 74 M
    Is this ok [y/N]: y
    Downloading Packages:
    (1/5): mysql-community-client-5.6.29-2.el6.x86_64.rpm       |  18 MB     00:28
    (2/5): mysql-community-common-5.6.29-2.el6.x86_64.rpm       | 308 kB     00:01
    (3/5): mysql-community-libs-5.6.29-2.el6.x86_64.rpm         | 1.9 MB     00:05
    (4/5): mysql-community-libs-compat-5.6.29-2.el6.x86_64.rpm  | 1.6 MB     00:05
    (5/5): mysql-community-server-5.6.29-2.el6.x86_64.rpm       |  53 MB     03:42
     -------------------------------------------------------------------------------
    Total                                              289 kB/s |  74 MB     04:24
    warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID <key_id> NOKEY
    Retrieving key from file:/etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
    Importing GPG key 0x5072E1F5:
     Userid : MySQL Release Engineering <mysql-build@oss.oracle.com>
    Package: mysql-community-release-el6-5.noarch
             (@/mysql-community-release-el6-5.noarch)
     From   : file:/etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
    Is this ok [y/N]: y
    Running rpm_check_debug
    Running Transaction Test
    Transaction Test Succeeded
    Running Transaction
      Installing : mysql-community-common-5.6.29-2.el6.x86_64
    ....Output truncated....
    1.el6.x86_64                                                               7/8
      Verifying  : mysql-5.1.71-1.el6.x86_64                       	           8/8
    Installed:
      mysql-community-client.x86_64 0:5.6.29-2.el6
      mysql-community-libs.x86_64 0:5.6.29-2.el6
      mysql-community-libs-compat.x86_64 0:5.6.29-2.el6
      mysql-community-server.x86_64 0:5.6.29-2.el6
    
    Dependency Installed:
      mysql-community-common.x86_64 0:5.6.29-2.el6
    
    Replaced:
      mysql.x86_64 0:5.1.71-1.el6 mysql-libs.x86_64 0:5.1.71-1.el6
      mysql-server.x86_64 0:5.1.71-1.el6
    Complete!
  7. 啟動MySQL伺服器:

    Initializing MySQL database:  2016-04-05 19:44:38 0 [Warning] TIMESTAMP
    with implicit DEFAULT value is deprecated. Please use
    --explicit_defaults_for_timestamp server option (see documentation
    for more details).
    2016-04-05 19:44:38 0 [Note] /usr/sbin/mysqld (mysqld 5.6.29)
            starting as process 2487 ...
    2016-04-05 19:44:38 2487 [Note] InnoDB: Using atomics to ref count
            buffer pool pages
    2016-04-05 19:44:38 2487 [Note] InnoDB: The InnoDB memory heap is disabled
    ....Output truncated....
    2016-04-05 19:44:42 2509 [Note] InnoDB: Shutdown completed; log sequence
           number 1625987
    
    PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER!
    To do so, start the server, then issue the following commands:
    
      /usr/bin/mysqladmin -u root password 'new-password'
      /usr/bin/mysqladmin -u root -h mcctb password 'new-password'
    
    Alternatively, you can run:
      /usr/bin/mysql_secure_installation
    
    which will also give you the option of removing the test
    databases and anonymous user created by default.  This is
    strongly recommended for production servers.
    .....Output truncated.....
    WARNING: Default config file /etc/my.cnf exists on the system
    This file will be read by default by the MySQL server
    If you do not want to use this, either remove it, or use the
    --defaults-file argument to mysqld_safe when starting the server
    
                                                               [  OK  ]
    Starting mysqld:                                           [  OK  ]
  8. 確認MySQL伺服器正在執行:

    [root@mcctb ~]#服務mysqLD狀態

    mysqld (pid  2739) is running...
  9. 設定安全性和密碼設定:

    NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
           SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!
    
     In order to log into MySQL to secure it, we'll need the current
     password for the root user.  If you've just installed MySQL, and
     you haven't set the root password yet, the password will be blank,
     so you should just press enter here.
    
     Enter current password for root (enter for none):   <== on default install
                                                             hit enter here
     OK, successfully used password, moving on...
    
     Setting the root password ensures that nobody can log into the MySQL
     root user without the proper authorization.
    
     Set root password? [Y/n] y
     New password:
     Re-enter new password:
     Password updated successfully!
     Reloading privilege tables..
      ... Success!
    
     By default, a MySQL installation has an anonymous user, allowing anyone
     to log into MySQL without having to have a user account created for
     them.  This is intended only for testing, and to make the installation
     go a bit smoother.  You should remove them before moving into a
     production environment.
    
     Remove anonymous users? [Y/n] y
      ... Success!
    
     Normally, root should only be allowed to connect from 'localhost'.  This
     ensures that someone cannot guess at the root password from the network.
    
     Disallow root login remotely? [Y/n] y
      ... Success!
    
     By default, MySQL comes with a database named 'test' that anyone can
     access.  This is also intended only for testing, and should be removed
     before moving into a production environment.
    
     Remove test database and access to it? [Y/n] y
      - Dropping test database...
     ERROR 1008 (HY000) at line 1: Can't drop database 'test';
     database doesn't exist
      ... Failed!  Not critical, keep moving...
      - Removing privileges on test database...
      ... Success!
    
     Reloading the privilege tables will ensure that all changes made so far
     will take effect immediately.
    
     Reload privilege tables now? [Y/n] y
      ... Success!
    
     All done!  If you've completed all of the above steps, your MySQL
     installation should now be secure.
    
     Thanks for using MySQL!
    
     Cleaning up...
  10. 驗證MySQL登入是否正常運作:

    Enter password: <configured_password>
    Welcome to the MySQL monitor.  Commands end with ; or \g.
    Your MySQL connection id is 17
    Server version: 5.6.29 MySQL Community Server (GPL)
    
    Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.
    
    Oracle is a registered trademark of Oracle Corporation and/or its
    affiliates. Other names may be trademarks of their respective
    owners.
    
    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
    mysql>

    如果MySQL登入正常運作、輸出將在「mysql>」提示字元結束。

啟用 MySQL 自動啟動設定

您應該確認MySQL精靈的自動啟動功能已開啟。開啟MySQL精靈會在MetroCluster 系統重新開機時、自動重新啟動MySQL。如果MySQL精靈未執行、則tiebreaker軟體會繼續執行、但無法重新啟動、也無法進行組態變更。

步驟
  1. 驗證MySQL在開機時是否已啟用自動啟動:

    [root@mcctb ~]# systemctl list-unit-filesmysqld.service`

    UNIT FILE          State
    ------------------ ----------
    mysqld.service     enabled

    如果MySQL在開機時未啟用自動啟動、請參閱MySQL文件、以啟用安裝的自動啟動功能。

在 Red Hat Enterprise Linux 8 上安裝 MariaDB 伺服器

您必須先在主機系統上安裝MariaDB伺服器、才能安裝或升級tiebreaker軟體。對於 Red Hat Enterprise Linux 7 或 CentOS 7 、 安裝 MySQL Server

開始之前

您的主機系統必須在Red Hat Enterprise Linux(RHEL)8上執行。

步驟
  1. 以登入 root 使用者或可Sudo進階權限模式的使用者。

    login as: root
    root@mcctb's password:
    Last login: Fri Jan  8 21:33:00 2017 from host.domain.com
  2. 安裝 MariaDB 伺服器:

    [root@mcctb ~]# yum install MariaDB-server.x86_64

    [root@mcctb ~]# yum install mariadb-server.x86_64
    Loaded plugins: fastestmirror, langpacks
     ...
     ...
    
    ===========================================================================
     Package                      Arch   Version         Repository        Size
    ===========================================================================
    Installing:
    mariadb-server               x86_64   1:5.5.56-2.el7   base            11 M
    Installing for dependencies:
    
    Transaction Summary
    ===========================================================================
    Install  1 Package  (+8 Dependent packages)
    Upgrade             ( 1 Dependent package)
    
    Total download size: 22 M
    Is this ok [y/d/N]: y
    
    Downloading packages:
    No Presto metadata available for base warning:
    /var/cache/yum/x86_64/7/base/packages/mariadb-libs-5.5.56-2.el7.x86_64.rpm:
    Header V3 RSA/SHA256 Signature,
    key ID f4a80eb5: NOKEY] 1.4 MB/s | 3.3 MB  00:00:13 ETA
    Public key for mariadb-libs-5.5.56-2.el7.x86_64.rpm is not installed
    (1/10): mariadb-libs-5.5.56-2.el7.x86_64.rpm  | 757 kB  00:00:01
    ..
    ..
    (10/10): perl-Net-Daemon-0.48-5.el7.noarch.rpm|  51 kB  00:00:01
    -----------------------------------------------------------------------------------------
    Installed:
      mariadb-server.x86_64 1:5.5.56-2.el7
    
    Dependency Installed:
    mariadb.x86_64 1:5.5.56-2.el7
    perl-Compress-Raw-Bzip2.x86_64 0:2.061-3.el7
    perl-Compress-Raw-Zlib.x86_64 1:2.061-4.el7
    perl-DBD-MySQL.x86_64 0:4.023-5.el7
    perl-DBI.x86_64 0:1.627-4.el7
    perl-IO-Compress.noarch 0:2.061-2.el7
    perl-Net-Daemon.noarch 0:0.48-5.el7
    perl-PlRPC.noarch 0:0.2020-14.el7
    
    Dependency Updated:
      mariadb-libs.x86_64 1:5.5.56-2.el7
    Complete!
  3. 啟動MariaDB伺服器:

    [root@mcctb ~]# systemcl start MariaDB

  4. 確認MariaDB伺服器已啟動:

    [root@mcctb ~]# systemctl狀態MariaDB

    [root@mcctb ~]# systemctl status mariadb
    mariadb.service - MariaDB database server
    ...
    Nov 08 21:28:59 mcctb systemd[1]: Starting MariaDB database server...
    ...
    Nov 08 21:29:01 mcctb systemd[1]: Started MariaDB database server.
  5. 設定安全性和密碼設定:

    註 當系統提示您輸入 root 密碼時、請將其保留空白、然後按 Enter 鍵繼續設定安全性和密碼設定。
    root@localhost systemd]# mysql_secure_installation
    
     NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
          SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!
    
    In order to log into MariaDB to secure it, we'll need the current
    password for the root user.  If you've just installed MariaDB, and
    you haven't set the root password yet, the password will be blank,
    so you should just press enter here.
    
    Enter current password for root (enter for none):
    OK, successfully used password, moving on...
    
    Setting the root password ensures that nobody can log into the MariaDB
    root user without the proper authorisation.
    
    Set root password? [Y/n] y
    New password:
    Re-enter new password:
    Password updated successfully!
    Reloading privilege tables..
     ... Success!
    
    
    By default, a MariaDB installation has an anonymous user, allowing anyone
    to log into MariaDB without having to have a user account created for
    them.  This is intended only for testing, and to make the installation
    go a bit smoother.  You should remove them before moving into a
    production environment.
    
    Remove anonymous users? [Y/n] y
     ... Success!
    
    Normally, root should only be allowed to connect from 'localhost'.  This
    ensures that someone cannot guess at the root password from the network.
    
    Disallow root login remotely? [Y/n] y
     ... Success!
    
    By default, MariaDB comes with a database named 'test' that anyone can
    access.  This is also intended only for testing, and should be removed
    before moving into a production environment.
    
    Remove test database and access to it? [Y/n] y
     - Dropping test database...
      ... Success!
     - Removing privileges on test database...
       ... Success!
    
    Reloading the privilege tables will ensure that all changes made so far
    will take effect immediately.
    
    Reload privilege tables now? [Y/n]
    
     ... Success!
    
    Cleaning up...
    
    All done!  If you've completed all of the above steps, your MariaDB
    installation should now be secure.
    
    Thanks for using MariaDB!

啟用 MariaDB 伺服器的自動啟動設定

您應該確認 MariaDB 伺服器的自動啟動功能已開啟。如果您未啟用自動啟動功能、MetroCluster 且駐留的系統必須重新開機、則tiebreaker軟體會繼續執行、但無法重新啟動MariaDB服務、也無法進行組態變更。

步驟
  1. 啟用自動啟動服務:

    [root@mcctb ~]# systemctl enable mariadb.service`

  2. 確認已啟用MariaDB、以便在開機時自動啟動:

    [root@mcctb ~]# systemctl list-unit-filesmariadb.service`

    UNIT FILE          State
    ------------------ ----------
    mariadb.service    enabled