CentOS 6.5上部署Heartbeat

简介:

环境说明:

主机名 角色 IP地址 VIP
heartbeat01.contoso.com Heartbeat节点1

eth0:192.168.49.133

eth1:172.16.49.133(心跳连接)

172.16.49.100
heartbeat02.contoso.com Heartbeat节点2

eth0:192.168.49.134

eth1:172.16.49.134(心跳连接)


一、准备工作

以下操作除非特别指明,否则均需在两台服务器上操作。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
# 关闭iptables防火墙并禁用SELinux
/etc/init .d /iptables  stop
chkconfig iptables off
sed  -i  '/^SELINUX/s/enforcing/disabled/'  /etc/selinux/config
setenforce 0
 
# 设置时间同步
crontab  -e   # 添加计划任务
0 * * * *  /usr/sbin/ntpdate    210.72.145.44 64.147.116.229  time .nist.gov
:wq
或者
echo  '0 * * * * /usr/sbin/ntpdate   210.72.145.44 64.147.116.229 time.nist.gov'  >> /var/spool/cron/root   # 添加计划任务
crontab  -l   # 检查计划任务是否存在
0 * * * *  /usr/sbin/ntpdate    210.72.145.44 64.147.116.229  time .nist.gov
 
# 设置主机名(以heartbeat01为例,heartbeat02同样的方法)
sed  -i  '/^HOSTNAME/s/^/#/'  /etc/sysconfig/network  
sed  -i  '/#HOSTNAME/aHOSTNAME=heartbeat01.contoso.com'  /etc/sysconfig/network
grep  HOSTNAME  /etc/sysconfig/network
hostname  heartbeat01.contoso.com
或者
sed  -i  '/^HOSTNAME/d'  /etc/sysconfig/network
echo  'HOSTNAME=heartbeat01.contoso.com'  >> /etc/sysconfig/network
grep  HOSTNAME  /etc/sysconfig/network
hostname  heartbeat01.contoso.com
 
# 编辑/etc/hosts文件
echo  -e  '192.168.49.133  heartbeat01.contoso.com\n192.168.49.134  heartbeat02.contoso.com'  >> /etc/hosts
tail  -2  /etc/hosts
 
# 添加一条主机路由
/sbin/route  add -host 172.16.49.134 dev eth1  # 在heartbeat01上配置
echo  '/sbin/route add -host 172.16.49.134 dev eth1'  >> /etc/rc . local  # 在heartbeat01上配置
/sbin/route  add -host 172.16.49.133 dev eth1  # 在heartbeat02上配置
echo  '/sbin/route add -host 172.16.49.133 dev eth1'  >> /etc/rc . local  # 在heartbeat02上配置
route -n  #添加之后分别在heartbeat01和heartbeat02上检查

二、安装heartbeat软件

1
2
rpm -ivh http: //dl .fedoraproject.org /pub/epel/6/x86_64/epel-release-6-8 .noarch.rpm
yum -y  install  heartbeat*

三、编辑heartbeat配置文件

1)拷贝配置文件

1
2
3
cp  /usr/share/doc/heartbeat-3 .0.4/{ha.cf,haresources,authkeys}  /etc/ha .d/
ll  /etc/ha .d/
cd  /etc/ha .d/

2)配置authkeys

[root@heartbeat01 ha.d]# egrep -v "#|^$" authkeys 

auth 2

2 sha1 c6091592594cd14c

[root@heartbeat02 ha.d]# egrep -v "#|^$" authkeys 

auth 2

2 sha1 c6091592594cd14c

# 两个节点的配置一致

3)配置ha.cf

下面以使用单播的方式为例,给出两个节点的配置:

[root@heartbeat01 ha.d]# egrep -v "#|^$" ha.cf 

debugfile /var/log/ha-debug  #设置debug文件位置

logfile /var/log/ha-log  #设置日志文件位置

logfacility local1  #设置记录日志的设备

keepalive 2  #设置发送心跳报文的时间间隔

deadtime 30  #设置确认对端死亡的时间间隔

warntime 10  #设置发出最后的心跳警告报文的间隔 

initdead 60  #设置初始化时间

ucast eth1 172.16.49.134  #设定侦听的心跳线的接口和对应的对端接口的IP地址

auto_failback on  #启用自动恢复模式,当拥有该资源的属主恢复之后,属主将回收该资源

node heartbeat01.contoso.com  #指定节点1,节点的名称一定要和uname -n的结果一致

node heartbeat02.contoso.com  #指定节点2

ping 172.16.49.1  #指定第三方仲裁节点

respawn hacluster /usr/lib64/heartbeat/ipfail  #使用这个脚本去侦听对方是否还活着(使用的是ICMP报文检测)

[root@heartbeat02 ha.d]# egrep -v "#|^$" ha.cf 

debugfile /var/log/ha-debug

logfile /var/log/ha-log

logfacility local1

keepalive 2

deadtime 30

warntime 10

initdead 60

ucast eth1 172.16.49.133

auto_failback on

node heartbeat01.contoso.com

node heartbeat02.contoso.com

ping 172.16.49.1

respawn hacluster /usr/lib64/heartbeat/ipfail

# 两个节点的差别只有单播的对端IP不一样,其他都一样

4)配置haresources

echo 'heartbeat01.contoso.com  IPaddr::172.16.49.100/24/eth1' >>/etc/ha.d/haresources

[root@heartbeat01 ha.d]# egrep -v "#|^$" haresources

heartbeat01.contoso.com  IPaddr::172.16.49.100/24/eth1

[root@heartbeat02 ha.d]# egrep -v "#|^$" haresources 

heartbeat01.contoso.com  IPaddr::172.16.49.100/24/eth1

# 两个节点的配置一致

四、启动heartbeat并测试

1
/etc/init .d /heartbeat  start   #分别在heartbeat01和heartbeat02上执行

到两个节点上分别查看VIP:

[root@heartbeat01 ha.d]# ip addr |grep 172.16.49

    inet 172.16.49.133/24 brd 172.16.49.255 scope global eth1

    inet 172.16.49.100/24 brd 172.16.49.255 scope global secondary eth1

[root@heartbeat02 ha.d]# ip addr |grep 172.16.49

    inet 172.16.49.134/24 brd 172.16.49.255 scope global eth1

然后,将heartbeat01上的heartbeat服务关闭,再进行查看:

[root@heartbeat01 ha.d]# /etc/init.d/heartbeat stop

Stopping High-Availability services: Done.


[root@heartbeat01 ha.d]# ip addr |grep 172.16.49

    inet 172.16.49.133/24 brd 172.16.49.255 scope global eth1

[root@heartbeat02 ha.d]# ip addr |grep 172.16.49

    inet 172.16.49.134/24 brd 172.16.49.255 scope global eth1

    inet 172.16.49.100/24 brd 172.16.49.255 scope global secondary eth1

可以看到,VIP已经从heartbeat01上转移到heartbeat02上了。

wKioL1fjpw3SPJiQAADdwlpRrZo948.png-wh_50

在VIP切换过程中,从另一台主机ping VIP地址,间断时间非常短暂。

五、检查日志

/var/log/ha-log

================================================

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Comm_now_up(): updating status to active

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Local status now set to: 'active'

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Starting child client "/usr/lib64/heartbeat/ipfail" (498,499)

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7312]: info: Starting "/usr/lib64/heartbeat/ipfail" as uid 498  gid 499 (pid 7312)

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Status update for node heartbeat02.contoso.com: status active

harc(default)[7315]: 2016/09/22_05:44:26 info: Running /etc/ha.d//rc.d/status status

Sep 22 05:44:33 heartbeat01.contoso.com ipfail: [7312]: info: Asking other side for ping node count.

Sep 22 05:44:36 heartbeat01.contoso.com ipfail: [7312]: info: No giveup timer to abort.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7284]: info: remote resource transition completed.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7284]: info: remote resource transition completed.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7284]: info: Initial resource acquisition complete (T_RESOURCES(us))

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7368]: 2016/09/22_05:44:37 INFO:  Resource is stopped

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7332]: info: Local Resource acquisition completed.

harc(default)[7451]: 2016/09/22_05:44:37 info: Running /etc/ha.d//rc.d/ip-request-resp ip-request-resp

ip-request-resp(default)[7451]: 2016/09/22_05:44:37 received ip-request-resp IPaddr::172.16.49.100/24/eth1 OK yes

ResourceManager(default)[7474]: 2016/09/22_05:44:37 info: Acquiring resource group: heartbeat01.contoso.com IPaddr::172.16.49.100/24/eth1

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7502]: 2016/09/22_05:44:37 INFO:  Resource is stopped

ResourceManager(default)[7474]: 2016/09/22_05:44:37 info: Running /etc/ha.d/resource.d/IPaddr 172.16.49.100/24/eth1 start

IPaddr(IPaddr_172.16.49.100)[7627]: 2016/09/22_05:44:38 INFO: Adding inet address 172.16.49.100/24 with broadcast address 172.16.49.255 to device eth1

IPaddr(IPaddr_172.16.49.100)[7627]: 2016/09/22_05:44:38 INFO: Bringing device eth1 up

IPaddr(IPaddr_172.16.49.100)[7627]: 2016/09/22_05:44:38 INFO: /usr/libexec/heartbeat/send_arp -i 200 -r 5 -p /var/run/resource-agents/send_arp-172.16.49.100 eth1 172.16.49.100 auto not_used not_used

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7601]: 2016/09/22_05:44:38 INFO:  Success

Sep 22 05:44:40 heartbeat01.contoso.com heartbeat: [7284]: info: Heartbeat shutdown in progress. (7284)

Sep 22 05:44:40 heartbeat01.contoso.com heartbeat: [7716]: info: Giving up all HA resources.

ResourceManager(default)[7729]: 2016/09/22_05:44:40 info: Releasing resource group: heartbeat01.contoso.com IPaddr::172.16.49.100/24/eth1

ResourceManager(default)[7729]: 2016/09/22_05:44:40 info: Running /etc/ha.d/resource.d/IPaddr 172.16.49.100/24/eth1 stop

IPaddr(IPaddr_172.16.49.100)[7792]: 2016/09/22_05:44:40 INFO: IP status = ok, IP_CIP=

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7766]: 2016/09/22_05:44:40 INFO:  Success

Sep 22 05:44:40 heartbeat01.contoso.com heartbeat: [7716]: info: All HA resources relinquished.

Sep 22 05:44:41 heartbeat01.contoso.com heartbeat: [7284]: WARN: 1 lost packet(s) for [heartbeat02.contoso.com] [20:22]

Sep 22 05:44:41 heartbeat01.contoso.com heartbeat: [7284]: info: No pkts missing from heartbeat02.contoso.com!

Sep 22 05:44:41 heartbeat01.contoso.com heartbeat: [7284]: info: killing /usr/lib64/heartbeat/ipfail process group 7312 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBFIFO process 7288 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBWRITE process 7289 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBREAD process 7290 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBWRITE process 7291 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBREAD process 7292 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7292 exited. 5 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7289 exited. 4 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7290 exited. 3 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7291 exited. 2 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7288 exited. 1 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: heartbeat01.contoso.com Heartbeat shutdown complete.


/var/log/ha-debug

================================================

Sep 22 05:44:14 heartbeat01.contoso.com heartbeat: [7283]: info: **************************

Sep 22 05:44:14 heartbeat01.contoso.com heartbeat: [7283]: info: Configuration validated. Starting heartbeat 3.0.4

Sep 22 05:44:14 heartbeat01.contoso.com heartbeat: [7284]: info: heartbeat: version 3.0.4

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: Heartbeat generation: 1474533038

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth1

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: glib: ucast: bound send socket to device: eth1

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: glib: ucast: set SO_REUSEPORT(w)

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: glib: ucast: bound receive socket to device: eth1

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: glib: ucast: set SO_REUSEPORT(w)

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: glib: ucast: started on port 694 interface eth1 to 172.16.49.134

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: glib: ping heartbeat started.

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: G_main_add_TriggerHandler: Added signal manual handler

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: G_main_add_TriggerHandler: Added signal manual handler

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: G_main_add_SignalHandler: Added signal handler for signal 17

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: Local status now set to: 'up'

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: Link 172.16.49.1:172.16.49.1 up.

Sep 22 05:44:15 heartbeat01.contoso.com heartbeat: [7284]: info: Status update for node 172.16.49.1: status ping

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Link heartbeat02.contoso.com:eth1 up.

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Status update for node heartbeat02.contoso.com: status up

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7294]: debug: notify_world: setting SIGCHLD Handler to SIG_DFL

harc(default)[7294]: 2016/09/22_05:44:26 info: Running /etc/ha.d//rc.d/status status

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Comm_now_up(): updating status to active

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Local status now set to: 'active'

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Starting child client "/usr/lib64/heartbeat/ipfail" (498,499)

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: debug: get_delnodelist: delnodelist= 

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7312]: info: Starting "/usr/lib64/heartbeat/ipfail" as uid 498  gid 499 (pid 7312)

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7284]: info: Status update for node heartbeat02.contoso.com: status active

Sep 22 05:44:26 heartbeat01.contoso.com heartbeat: [7315]: debug: notify_world: setting SIGCHLD Handler to SIG_DFL

harc(default)[7315]: 2016/09/22_05:44:26 info: Running /etc/ha.d//rc.d/status status

Sep 22 05:44:26 heartbeat01.contoso.com ipfail: [7312]: debug: PID=7312

Sep 22 05:44:26 heartbeat01.contoso.com ipfail: [7312]: debug: Signing in with heartbeat

Sep 22 05:44:27 heartbeat01.contoso.com ipfail: [7312]: debug: [We are heartbeat01.contoso.com]

Sep 22 05:44:27 heartbeat01.contoso.com ipfail: [7312]: debug: auto_failback -> 1 (on)

Sep 22 05:44:27 heartbeat01.contoso.com ipfail: [7312]: debug: Setting message filter mode

Sep 22 05:44:28 heartbeat01.contoso.com ipfail: [7312]: debug: Starting node walk

Sep 22 05:44:29 heartbeat01.contoso.com ipfail: [7312]: debug: Cluster node: 172.16.49.1: status: ping

Sep 22 05:44:29 heartbeat01.contoso.com ipfail: [7312]: debug: Cluster node: heartbeat02.contoso.com: status: active

Sep 22 05:44:30 heartbeat01.contoso.com ipfail: [7312]: debug: [They are heartbeat02.contoso.com]

Sep 22 05:44:30 heartbeat01.contoso.com ipfail: [7312]: debug: Cluster node: heartbeat01.contoso.com: status: active

Sep 22 05:44:31 heartbeat01.contoso.com ipfail: [7312]: debug: Setting message signal

Sep 22 05:44:31 heartbeat01.contoso.com ipfail: [7312]: debug: Waiting for messages...

Sep 22 05:44:32 heartbeat01.contoso.com ipfail: [7312]: debug: Got join message from another ipfail client. (heartbeat02.contoso.com)

Sep 22 05:44:33 heartbeat01.contoso.com ipfail: [7312]: debug: Found ping node 172.16.49.1!

Sep 22 05:44:33 heartbeat01.contoso.com ipfail: [7312]: info: Asking other side for ping node count.

Sep 22 05:44:33 heartbeat01.contoso.com ipfail: [7312]: debug: Message [num_ping] sent.

Sep 22 05:44:36 heartbeat01.contoso.com ipfail: [7312]: info: No giveup timer to abort.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7284]: info: remote resource transition completed.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7284]: info: remote resource transition completed.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7284]: info: Initial resource acquisition complete (T_RESOURCES(us))

Sep 22 05:44:37 heartbeat01.contoso.com ipfail: [7312]: debug: Other side is now stable.

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7368]: 2016/09/22_05:44:37 INFO:  Resource is stopped

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7332]: info: Local Resource acquisition completed.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7284]: debug: StartNextRemoteRscReq(): child count 1

Sep 22 05:44:37 heartbeat01.contoso.com ipfail: [7312]: debug: Other side is now stable.

Sep 22 05:44:37 heartbeat01.contoso.com heartbeat: [7451]: debug: notify_world: setting SIGCHLD Handler to SIG_DFL

harc(default)[7451]: 2016/09/22_05:44:37 info: Running /etc/ha.d//rc.d/ip-request-resp ip-request-resp

ip-request-resp(default)[7451]: 2016/09/22_05:44:37 received ip-request-resp IPaddr::172.16.49.100/24/eth1 OK yes

ResourceManager(default)[7474]: 2016/09/22_05:44:37 info: Acquiring resource group: heartbeat01.contoso.com IPaddr::172.16.49.100/24/eth1

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7502]: 2016/09/22_05:44:37 INFO:  Resource is stopped

ResourceManager(default)[7474]: 2016/09/22_05:44:37 info: Running /etc/ha.d/resource.d/IPaddr 172.16.49.100/24/eth1 start

IPaddr(IPaddr_172.16.49.100)[7627]: 2016/09/22_05:44:38 INFO: Adding inet address 172.16.49.100/24 with broadcast address 172.16.49.255 to device eth1

IPaddr(IPaddr_172.16.49.100)[7627]: 2016/09/22_05:44:38 INFO: Bringing device eth1 up

IPaddr(IPaddr_172.16.49.100)[7627]: 2016/09/22_05:44:38 INFO: /usr/libexec/heartbeat/send_arp -i 200 -r 5 -p /var/run/resource-agents/send_arp-172.16.49.100 eth1 172.16.49.100 auto not_used not_used

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7601]: 2016/09/22_05:44:38 INFO:  Success

INFO:  Success

Sep 22 05:44:40 heartbeat01.contoso.com heartbeat: [7284]: info: Heartbeat shutdown in progress. (7284)

Sep 22 05:44:40 heartbeat01.contoso.com heartbeat: [7716]: info: Giving up all HA resources.

ResourceManager(default)[7729]: 2016/09/22_05:44:40 info: Releasing resource group: heartbeat01.contoso.com IPaddr::172.16.49.100/24/eth1

ResourceManager(default)[7729]: 2016/09/22_05:44:40 info: Running /etc/ha.d/resource.d/IPaddr 172.16.49.100/24/eth1 stop

IPaddr(IPaddr_172.16.49.100)[7792]: 2016/09/22_05:44:40 INFO: IP status = ok, IP_CIP=

/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_172.16.49.100)[7766]: 2016/09/22_05:44:40 INFO:  Success

INFO:  Success

Sep 22 05:44:40 heartbeat01.contoso.com heartbeat: [7716]: info: All HA resources relinquished.

Sep 22 05:44:41 heartbeat01.contoso.com heartbeat: [7284]: WARN: 1 lost packet(s) for [heartbeat02.contoso.com] [20:22]

Sep 22 05:44:41 heartbeat01.contoso.com ipfail: [7312]: debug: Other side is now stable.

Sep 22 05:44:41 heartbeat01.contoso.com heartbeat: [7284]: info: No pkts missing from heartbeat02.contoso.com!

Sep 22 05:44:41 heartbeat01.contoso.com heartbeat: [7284]: info: killing /usr/lib64/heartbeat/ipfail process group 7312 with signal 15

ARPING 172.16.49.100 from 172.16.49.100 eth1

Sent 5 probes (5 broadcast(s))

Received 0 response(s)

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBFIFO process 7288 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBWRITE process 7289 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBREAD process 7290 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBWRITE process 7291 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: killing HBREAD process 7292 with signal 15

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7292 exited. 5 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7289 exited. 4 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7290 exited. 3 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7291 exited. 2 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: Core process 7288 exited. 1 remaining

Sep 22 05:44:43 heartbeat01.contoso.com heartbeat: [7284]: info: heartbeat01.contoso.com Heartbeat shutdown complete.




本文转自 jerry1111111 51CTO博客,原文链接:http://blog.51cto.com/jerry12356/1855553,如需转载请自行联系原作者
相关文章
|
2月前
|
监控 前端开发 Linux
centos7系统安装部署zabbix5.0
【9月更文挑战第23天】在CentOS 7系统上部署Zabbix 5.0的步骤包括:安装MariaDB数据库及必要软件包,配置Zabbix仓库,设置数据库并导入Zabbix数据库架构,配置Zabbix服务器与前端参数,启动相关服务,并通过浏览器访问Web界面完成安装向导。
161 0
|
2月前
|
Oracle Java 关系型数据库
CentOS 7.6操作系统部署JDK实战案例
这篇文章介绍了在CentOS 7.6操作系统上通过多种方式部署JDK的详细步骤,包括使用yum安装openjdk、基于rpm包和二进制包安装Oracle JDK,并提供了配置环境变量的方法。
282 80
|
4月前
|
Linux 虚拟化 数据安全/隐私保护
部署05-VMwareWorkstation中安装CentOS7 Linux操作系统, VMware部署CentOS系统第一步,下载Linux系统,/不要忘, CentOS -7-x86_64-DVD
部署05-VMwareWorkstation中安装CentOS7 Linux操作系统, VMware部署CentOS系统第一步,下载Linux系统,/不要忘, CentOS -7-x86_64-DVD
|
1月前
|
存储 Linux 开发者
虚拟机centos7.9一键部署docker
本文介绍了如何在 CentOS 7.9 虚拟机上安装 Docker 社区版 (Docker-ce-20.10.20)。通过使用阿里云镜像源,利用 `wget` 下载并配置 Docker-ce 的 YUM 仓库文件,然后通过 `yum` 命令完成安装。安装后,通过 `systemctl` 设置 Docker 开机自启并启动 Docker 服务。最后,使用 `docker version` 验证安装成功,并展示了客户端与服务器的版本信息。文中还提供了列出所有可用 Docker-ce 版本的命令。
195 0
虚拟机centos7.9一键部署docker
|
2月前
|
存储 Kubernetes 负载均衡
CentOS 7.9二进制部署K8S 1.28.3+集群实战
本文详细介绍了在CentOS 7.9上通过二进制方式部署Kubernetes 1.28.3+集群的全过程,包括环境准备、组件安装、证书生成、高可用配置以及网络插件部署等关键步骤。
462 3
CentOS 7.9二进制部署K8S 1.28.3+集群实战
|
2月前
|
Linux pouch 容器
CentOS7部署阿里巴巴开源的pouch容器管理工具实战
关于如何在CentOS 7.6操作系统上安装和使用阿里巴巴开源的Pouch容器管理工具的实战教程。
126 2
CentOS7部署阿里巴巴开源的pouch容器管理工具实战
|
3月前
|
机器学习/深度学习 文字识别 Linux
百度飞桨(PaddlePaddle) - PP-OCRv3 文字检测识别系统 基于 Paddle Serving快速使用(服务化部署 - CentOS 7)
百度飞桨(PaddlePaddle) - PP-OCRv3 文字检测识别系统 基于 Paddle Serving快速使用(服务化部署 - CentOS 7)
92 1
百度飞桨(PaddlePaddle) - PP-OCRv3 文字检测识别系统 基于 Paddle Serving快速使用(服务化部署 - CentOS 7)
|
2月前
|
Kubernetes Linux API
CentOS 7.6使用kubeadm部署k8s 1.17.2测试集群实战篇
该博客文章详细介绍了在CentOS 7.6操作系统上使用kubeadm工具部署kubernetes 1.17.2版本的测试集群的过程,包括主机环境准备、安装Docker、配置kubelet、初始化集群、添加节点、部署网络插件以及配置k8s node节点管理api server服务器。
126 0
CentOS 7.6使用kubeadm部署k8s 1.17.2测试集群实战篇
|
3月前
|
Linux 数据安全/隐私保护 虚拟化
centos7部署openVPN
centos7部署openVPN
|
3月前
|
Linux 数据安全/隐私保护 网络虚拟化
centos7部署Pritunl
centos7部署Pritunl
下一篇
无影云桌面