小型架构实验模拟

一实验需求

二实验环境

22 机器：做nginx 反向代理做静态资源服务器

装 nginx keepalived filebeat

**44机器：**做22 机器的备胎

装nginx keepalived

99机器：做mysql的主

装mysqld 装node 装filebeat

77机器：做mysql从做tomcat动态资源服务器

装mysqld node tomcat

88机器：做mysql从做tomcat 动态资源服务器

装mysqld node1 tomcat

66 机器：做elk 节点服务器且做mha 的manager 节点

装logstash es es-head kibana manager

三实验步骤

1，先做nginx的反向代理和不同域名指向

1.1（22,44）nginx 配置文件如下：

bash 复制代码

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 4096;

    upstream tomcat {
      server 192.168.217.77:8080;
      server 192.168.217.88:8080;
    }
    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
    # for more information.
    include /etc/nginx/conf.d/*.conf;

    server {
        listen       80;
        listen       [::]:80;
        server_name  _;
        root         /usr/share/nginx/html;


          location ~*\.jsp$ {
        proxy_pass http://tomcat;
        }

        location ~* \.(jpg|jpeg|png|gif|bmp|html)$ {
        root  /usr/share/nginx/html/;
        }
}

  server {
        listen       80;



       server_name www.benet.com;
       root /data/benet;
       location / {
       proxy_pass http://192.168.217.77:8080;
       }
}

  server {
        listen       80;

       server_name www.kgc.com;
       root /data/kgc;
       location / {
       proxy_pass http://192.168.217.88:8080;
       }

}
        # Load configuration files for the default server block.
        include /etc/nginx/default.d/*.conf;

  server {
        listen       80;
        error_page 404 /404.html;
        location = /404.html {
        }

        error_page 500 502 503 504 /50x.html;
        location = /50x.html {
        }

}

1.2 解释

1.3 实验效果

访问nginx 以.jsp 结尾会以轮询方式访问后面的tomcat

访问 nginx 以.png 结尾会在本地找

访问 benet 域名会指向tomcat1 (记得本机做域名映射)

访问kgc 域名会指向 tomcat 2

以上答案错误！正确答案：

客户只知道域名根据域名做对应的动静分离

2，做nginx 的高可用

2.1 keepalive 配置文件如下 (这是主)

备改 router_id LVS_02 state BACKUP priority 80

bash 复制代码

! Configuration File for keepalived

global_defs {
   notification_email {
     acassen@firewall.loc
     failover@firewall.loc
     sysadmin@firewall.loc
   }
   notification_email_from Alexandre.Cassen@firewall.loc
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id LVS_01
   vrrp_skip_check_adv_addr
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script check_down {
        script "/etc/keepalived/ng.sh"
        interval 1
        weight -30
        fall 3
        rise 2
        timeout 2
}

vrrp_instance VI_1 {
    state MASTER
    interface ens33
    virtual_router_id 51
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }

    virtual_ipaddress {
        192.168.217.188
    }

    track_script {
        check_down
}

}

2.2 （22,44机器）写检测nginx 是否活着的脚本（注意路径）

2.3 实验效果

虚拟ip 188 会飘在 22 机器上（主）

当手动制造 22 机器故障 systemctl stop nginx 虚拟ip 会飘到44机器上

证明：若主出现故障从会顶上来

3，做mysql 主从复制与读写分离 mha做高可用

前篇已详细概述，本篇暂不赘述

4，做filebeat 收集nginx 的正确错误日志

4.1 （22机器）filebeat 的配置文件

bash 复制代码

#=========================== Filebeat inputs =============================

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

- type: log

  enabled: true

  paths:
    - /var/log/nginx/access.log
  tags: ["access"]

- type: log

  enabled: true

  paths:
    - /var/log/nginx/error.log
  tags: ["error"]

bash 复制代码

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["192.168.217.66:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

4.2 （66机器）logstash 配置文件

bash 复制代码

input {
    beats {
    port => "5044"
    }
}
output {
   if "access" in [tags] {
      elasticsearch {
        hosts => ["192.168.217.66:9200"]
        index => "nginx-access-%{+YYYY.MM.dd}"
        }
   }
   if "error" in [tags] {
      elasticsearch {
         hosts => ["192.168.217.66:9200"]
         index => "nginx-error-%{+YYYY.MM.dd}"
        }
   }
   stdout {
       codec => rubydebug
   }
}

4.3 （66机器）elasticsearch主配置文件

bash 复制代码

[root@node ~]#grep -v "^#" /etc/elasticsearch/elasticsearch.yml
cluster.name: my-elk-cluster
node.name: node
path.data: /data/elk_data
path.logs: /var/log/elasticsearch/
bootstrap.memory_lock: false
network.host: 0.0.0.0
http.port: 9200
discovery.zen.ping.unicast.hosts: ["node"]

http.cors.enabled: true                         #开启跨域访问支持，默认为 false
http.cors.allow-origin: "*"                     #指定跨域访问允许的域名地址为所

4.4 （66机器）kibana 配置文件

bash 复制代码

[root@node ~]#grep -v "^#" /etc/kibana/kibana.yml 
server.port: 5601

server.host: "0.0.0.0"

elasticsearch.url: "http://192.168.217.66:9200"

kibana.index: ".kibana"

4.5 实验效果

5， filebeat 收集mysql 的错误日志

5.1 （99机器）mysql 配置文件添加错误日志路径

bash 复制代码

[client]
port = 3306
#default-character-set=utf8
socket = /usr/local/mysql/mysql.sock

[mysql]
port = 3306
default-character-set=utf8
socket = /usr/local/mysql/mysql.sock

[mysqld]
#log-error = /var/log/mysqld/error.log
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
log_error=/usr/local/mysql/error.log
character_set_server=utf8
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock
server-id = 1

log_bin = master-bin
log-slave-updates = true

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,PIPES_AS_CONCAT,ANSI_QUOTES
~                                                                                                   
~

5.2 （99机器） filebeat 的配置文件

bash 复制代码

#=========================== Filebeat inputs =============================

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

- type: log

  # Change to true to enable this input configuration.
  enabled: true

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /usr/local/mysql/error.log
  tags: ["error"]


 fields:           #可以使用 fields 配置选项设置一些参数字段添加到 output 中
    service_name: filebeat
    log_type: log
    service_id: 192.168.217.99

bash 复制代码

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["192.168.217.66:5044"]

5.3 （66 机器）写logstash 配置文件

bash 复制代码

input {
    beats {
        port => "5044"
    }
}
output {
    elasticsearch {
        hosts => ["192.168.217.66:9200"]
        index => "%{[fields][service_name]}-%{+YYYY.MM.dd}"
    }
    stdout {
        codec => rubydebug
    }
}

5.4 实验结果

四报错总结

1，logstash 配置文件占用报错

bash 复制代码

[root@node logstash]#/usr/share/logstash/bin/logstash -f /etc/logstash/conf.d/mysql.conf 

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
WARNING: Could not find logstash.yml which is typically located in $LS_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults
Could not find log4j2 configuration at path //usr/share/logstash/config/log4j2.properties. Using default config which logs to console
07:40:53.541 [LogStash::Runner] FATAL logstash.runner - Logstash could not be started because there is already another instance using the configured data directory.  If you wish to run multiple instances, you must change the "path.data" setting.

解决方法：

找到主进程 kill-9 93968

2，filebeat 起不来，配置文件报错

软件启动不来看 /var/log/messages

filebeat 的配置文件确保所有键值对的值正确缩进，遵循YAML的缩进规则（通常使用空格，且同一层级的元素应保持相同数量的空格）。说人话就是注意空格

3，manager 节点上测试 mysql 主从连接情况 MySQL Replication Health is not OK

masterha_check_repl -conf=/etc/masterha/app1.cnf

解决方法：

4， mysql 配置文件加不了错误日志路径

解决方法：编译安装的mysql 环境变量如下

所以日志也要放在该路径下

echo 'PATH=/usr/local/mysql/bin:/usr/local/mysql/lib:$PATH' >> /etc/profile

echo 'export PATH' >> /etc/profile

source /etc/profile

5，做mha 时 manager 节点报错

manager 节点也要先装node

6，做mysql 的elfk 时一直出不来

注意数据流向 ip 是否写错

7 mha 故障恢复

7.1 故障恢复步骤

bash 复制代码

故障修复步骤：
1．修复mysql
systemctl restart mysqld

2．修复主从
#在现主库服务器 Mysql2 查看二进制文件和同步点
show master status;

#在原主库服务器 mysql1 执行同步操作
change master to master_host='192.168.217.77',master_user='myslave',master_password='123456',master_log_file='master-bin.000002',master_log_pos=1745;

start slave;


3．在 manager 节点上修改配置文件app1.cnf（再把这个记录添加进去，因为它检测掉失效时候会自动消失）
vi /etc/masterha/app1.cnf
......
secondary_check_script=/usr/local/bin/masterha_secondary_check -s 192.168.10.14 -s 192.168.10.15
......
[server1]
hostname=192.168.217.77
port=3306

[server2]
candidate_master=1
check_repl_delay=0
hostname=192.168.217.88
port=3306

[server3]
hostname=192.168.217.99
port=3306

4．在 manager 节点上启动 MHA
nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/masterha/app1/manager.log 2>&1 &

7.2 报错

报错1 app1 is stopped(2:NOT_RUNNING).

bash 复制代码

[root@node ~]#masterha_check_status --conf=/etc/masterha/app1.cnf

这是查看 mha  主状态

app1 is stopped(2:NOT_RUNNING).

报错2 MySQL Replication Health is NOT OK!

bash 复制代码

[root@node ~]#masterha_check_repl -conf=/etc/masterha/app1.cnf

这是检测mha   主从复制情况


Mon Apr 22 01:13:23 2024 - [warning] Global configuration file /etc/masterha_default.cnf not found. 
Mon Apr 22 01:13:23 2024 - [info] Reading application default configuration from /etc/masterha/app1.
Mon Apr 22 01:13:23 2024 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Mon Apr 22 01:13:23 2024 - [info] MHA::MasterMonitor version 0.57.
Mon Apr 22 01:13:24 2024 - [error][/usr/local/share/perl5/MHA/ServerManager.pm, ln781] Multi-master configurations for details. Master configurations are as below: 
Master 192.168.217.77(192.168.217.77:3306), replicating from 192.168.217.99(192.168.217.99:3306)
Master 192.168.217.99(192.168.217.99:3306), replicating from 192.168.217.77(192.168.217.77:3306)

Mon Apr 22 01:13:24 2024 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln427] Error happene
Mon Apr 22 01:13:24 2024 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525] Error happene
Mon Apr 22 01:13:24 2024 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!
[1]+  Exit 1                  nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_m

7.3 解决办法

先看报错日志：

$root@node \~\]#masterha_check_repl -conf=/etc/masterha/app1.cnf Mon Apr 22 01:13:23 2024 - \[warning\] Global configuration file /etc/masterha_default.cnf not found. Skipping. Mon Apr 22 01:13:23 2024 - \[info\] Reading application default configuration from /etc/masterha/app1.cnf.. Mon Apr 22 01:13:23 2024 - \[info\] Reading server configuration from /etc/masterha/app1.cnf.. Mon Apr 22 01:13:23 2024 - \[info\] MHA::MasterMonitor version 0.57. Mon Apr 22 01:13:24 2024 - \[error\]\[/usr/local/share/perl5/MHA/ServerManager.pm, ln781\] Multi-master configuration is detected, but two or more masters are either writable (read-only is not set) or dead! Check configurations for details. Master configurations are as below: Master 192.168.217.77(192.168.217.77:3306), replicating from 192.168.217.99(192.168.217.99:3306) Master 192.168.217.99(192.168.217.99:3306), replicating from 192.168.217.77(192.168.217.77:3306) Mon Apr 22 01:13:24 2024 - \[error\]\[/usr/local/share/perl5/MHA/MasterMonitor.pm, ln427\] Error happened on checking configurations. at /usr/local/share/perl5/MHA/MasterMonitor.pm line 329. Mon Apr 22 01:13:24 2024 - \[error\]\[/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525\] Error happened on monitoring servers. Mon Apr 22 01:13:24 2024 - \[info\] Got exit code 1 (Not master dead). MySQL Replication Health is NOT OK! \[1\]+ Exit 1 nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover \< /dev/null \> /var/log/masterha/app1/manager.log 2\>\&1 \[root@node \~\]#masterha_check_status --conf=/etc/masterha/app1.cnf app1 is stopped(2:NOT_RUNNING).$

您提供的最新输出显示，在运行masterha_check_repl和masterha_check_status命令时，MySQL复制健康状况依然不正常，并且MHA（Master High Availability Manager）应用app1的状态为停止（stopped(2:NOT_RUNNING)）。以下是针对输出中关键信息的中文解释：

警告：Global configuration file /etc/masterha_default.cnf not found. Skipping. 表示系统未能找到全局配置文件 /etc/masterha_default.cnf。虽然跳过了该文件的读取，但建议检查文件是否存在，以及路径是否正确，确保所有必要的配置项已正确设置。
信息：Reading application default configuration from /etc/masterha/app1.cnf.. 和 Reading server configuration from /etc/masterha/app1.cnf.. 表明正在从 /etc/masterha/app1.cnf 文件中读取应用默认配置和服务器配置。
信息：MHA::MasterMonitor version 0.57. 显示当前使用的 MHA Master Monitor 版本为 0.57。
错误：Multi-master configuration is detected, but two or more masters are either writable (read-only is not set) or dead! Check configurations for details. 提示检测到存在多主（multi-master）配置，且有两个或更多主服务器处于可写状态（未设置为只读）或已经失效。这是一个严重问题，因为在一个典型的主从复制环境中，应该只有一个主服务器是可写的，其他服务器作为从服务器接收主服务器的数据复制。建议仔细检查以下两台主机的配置：
- Master 192.168.217.77(192.168.217.77:3306), replicating from 192.168.217.99(192.168.217.99:3306)
- Master 192.168.217.99(192.168.217.99:3306), replicating from 192.168.217.77(192.168.217.77:3306)
确保每个服务器的角色（主/从）正确设定，并且仅有一个主服务器处于可写状态。如果需要，可以检查并调整 read_only 系统变量，确保从服务器设置为只读。
错误：Error happened on checking configurations. at /usr/local/share/perl5/MHA/ServerManager.pm line 329. 和 Error happened on monitoring servers. 表示在检查配置和监控服务器时发生了错误。这些错误可能与上述多主配置问题直接相关。
信息：Got exit code 1 (Not master dead). 说明命令执行以退出码 1 结束，表示主服务器并未失效，但鉴于前面的错误信息，实际上是由于检测到了不正常的多主配置导致的。
MHA状态 ：app1 is stopped(2:NOT_RUNNING). 表明MHA应用app1当前处于停止状态，无法正常监控和管理MySQL复制环境的高可用性。

综上所述，您需要首先解决多主配置问题，确保只有单一主服务器处于可写状态，其余服务器作为从服务器正确地从主服务器接收复制。修复配置问题后，重启MHA应用app1，然后再次运行 masterha_check_repl 和 masterha_check_status 命令，以确认复制健康状况已恢复正常，并且MHA应用能够成功运行并监控您的MySQL复制环境。如果问题仍未解决，请进一步检查MHA配置文件和日志，以获取更详细的故障信息。

在原来的主上做只读

成功！

8 mha 故障恢复从节点顶不上来

每个mysql 上都有加这个因为每个mysql 都有可能成为从和主

bash 复制代码

[client]
port = 3306
#default-character-set=utf8
socket = /usr/local/mysql/mysql.sock

[mysql]
port = 3306
default-character-set=utf8
socket = /usr/local/mysql/mysql.sock

[mysqld]
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
character_set_server=utf8
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock
server-id = 2

log_bin = master-bin

relay-log = relay-log-bin

relay-log-index = slave-relay-bin.index

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,PIPES_AS_CONCAT,ANSI_QUOTES

小型架构实验模拟

一 实验需求

二 实验环境

三 实验步骤

1，先做nginx的反向代理 和不同域名指向

1.1（22,44）nginx 配置文件如下：

1.2 解释

1.3 实验效果

2， 做nginx 的高可用

2.1 keepalive 配置文件如下 (这是主)

2.2 （22,44机器）写检测nginx 是否活着的脚本（注意路径）

2.3 实验效果

3， 做mysql 主从复制与读写分离 mha做高可用

4，做filebeat 收集nginx 的正确错误日志

4.1 （22机器）filebeat 的配置文件

4.2 （66机器）logstash 配置文件

4.3 （66机器）elasticsearch主配置文件

4.4 （66机器）kibana 配置文件

4.5 实验效果

5， filebeat 收集mysql 的错误日志

5.1 （99机器）mysql 配置文件添加 错误日志路径

5.2 （99机器） filebeat 的配置文件

5.3 （66 机器）写logstash 配置文件

5.4 实验结果

四 报错总结

1，logstash 配置文件占用报错

2，filebeat 起不来， 配置文件报错

3，manager 节点上测试 mysql 主从连接情况 MySQL Replication Health is not OK

4， mysql 配置文件 加不了错误日志路径

5， 做mha 时 manager 节点报错

6，做mysql 的elfk 时一直出不来

7 mha 故障恢复

7.1 故障恢复步骤

7.2 报错

7.3 解决办法

8 mha 故障恢复 从节点顶不上来

一实验需求

二实验环境

三实验步骤

1，先做nginx的反向代理和不同域名指向

2，做nginx 的高可用

3，做mysql 主从复制与读写分离 mha做高可用

5.1 （99机器）mysql 配置文件添加错误日志路径

四报错总结

2，filebeat 起不来，配置文件报错

4， mysql 配置文件加不了错误日志路径

5，做mha 时 manager 节点报错

8 mha 故障恢复从节点顶不上来