小小的宝贝

corosync+drbd+mysql(实现mysql服务器的高可用性群集)

drbd+corosync+pacemaker

实现mysql服务器的高可用性群集

实验环境：

node1 node1.a.com 192.168.10.10

node2node2.a.com 192.168.10.20

vip:192.168.50.100

实验步骤：

修改群集中各节点的网络参数

node1

[root@node1 ~]# vim /etc/sysconfig/network

NETWORKING=yes

NETWORKING_IPV6=no

HOSTNAME=node2.a.com

[root@node1 ~]# vim /etc/hosts

127.0.0.1 localhost.localdomain localhost

::1 localhost6.localdomain6 localhost6

192.168.10.10 node1.a.com node1

192.168.10.20 node2.a.com node2

[root@node1 ~]# hostname

node1.a.com

同步群集中各节点的时间：

[root@node1 ~]# hwclock -s

node2

[root@node2 ~]# vim /etc/sysconfig/network

NETWORKING=yes

NETWORKING_IPV6=no

HOSTNAME=node2.a.com

[root@node2 ~]# vim /etc/hosts

127.0.0.1 localhost.localdomain localhost

::1 localhost6.localdomain6 localhost6

192.168.10.10 node1.a.com node1

192.168.10.20 node2.a.com node2

[root@node2 ~]# hostname

node2.a.com

[root@node2 ~]# hwclock -s

在各个节点上面产生密钥实现无密码的通讯

node1

产生一个rsa的非对称加密的私钥对：

[root@node1 ~]# ssh-keygen -t rsa

拷贝到node2节点：

[root@node1 ~]# ssh-copy-id -i .ssh/id_rsa.pub root@node2

The authenticity of host 'node2 (192.168.10.20)' can't be established.

RSA key fingerprint is f8:b2:a1:a2:27:51:b2:86:c9:d6:c9:74:a4:e3:e5:93.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'node2,192.168.10.20' (RSA) to the list of known hosts.

root@node2's password: 123456

Now try logging into the machine, with "ssh 'root@node2'", and check in:

.ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

node2

[root@node2 ~]# ssh-keygen -t rsa

Generating public/private rsa key pair.

Enter file in which to save the key (/root/.ssh/id_rsa):

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /root/.ssh/id_rsa.

Your public key has been saved in /root/.ssh/id_rsa.pub.

The key fingerprint is:

ea:25:f1:47:37:28:26:6a:75:57:1c:46:81:a8:41:6b [email protected]

[root@node2 ~]# ssh-copy-id -i .ssh/id_rsa.pub node1

The authenticity of host 'node1 (192.168.10.10)' can't be established.

RSA key fingerprint is f8:b2:a1:a2:27:51:b2:86:c9:d6:c9:74:a4:e3:e5:93.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'node1,192.168.10.10' (RSA) to the list of known hosts.

root@node1's password: 123456

Now try logging into the machine, with "ssh 'node1'", and check in:

.ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

在各个节点上面配置好yum客户端

node1

[root@node1 ~]# vim /etc/yum.repos.d/rhel-debuginfo.repo

[rhel-server]

name=Red Hat Enterprise Linux server

baseurl=file:///mnt/cdrom/Server

enabled=1

gpgcheck=1

gpgkey=file:///mnt/cdrom/RPM-GPG-KEY-redhat-release

[rhel-cluster]

name=Red Hat Enterprise Linux cluster

baseurl=file:///mnt/cdrom/Cluster

enabled=1

gpgcheck=1

gpgkey=file:///mnt/cdrom/RPM-GPG-KEY-redhat-release

[rhel-clusterstorage]

name=Red Hat Enterprise Linux clusterstorage

baseurl=file:///mnt/cdrom/ClusterStorage

enabled=1

gpgcheck=1

gpgkey=file:///mnt/cdrom/RPM-GPG-KEY-redhat-release

[root@node1 ~]# scp /etc/yum.repos.d/rhel-debuginfo.repo node2:/etc/yum.repos.d/

rhel-debuginfo.repo 100% 319 0.3KB/s 00:00

将下载好的rpm包上传到linux上的各个节点

[root@node1 ~]# ll

total 162332

drwxr-xr-x 2 root root 4096 Mar 19 23:34 Desktop

-rw------- 1 root root 1330 Feb 9 00:27 anaconda-ks.cfg

-rw-r--r-- 1 root root 271360 May 13 16:41 cluster-glue-1.0.6-1.6.el5.i386.rpm

-rw-r--r-- 1 root root 133254 May 13 16:41 cluster-glue-libs-1.0.6-1.6.el5.i386.rpm

-rw-r--r-- 1 root root 170052 May 13 16:41 corosync-1.2.7-1.1.el5.i386.rpm

-rw-r--r-- 1 root root 158502 May 13 16:41 corosynclib-1.2.7-1.1.el5.i386.rpm

-rw-r--r-- 1 root root 221868 May 13 16:41 drbd83-8.3.8-1.el5.centos.i386.rpm

-rw-r--r-- 1 root root 165591 May 13 16:41 heartbeat-3.0.3-2.3.el5.i386.rpm

-rw-r--r-- 1 root root 289600 May 13 16:41 heartbeat-libs-3.0.3-2.3.el5.i386.rpm

-rw-r--r-- 1 root root 35236 Feb 9 00:27 install.log

-rw-r--r-- 1 root root 3995 Feb 9 00:26 install.log.syslog

-rw-r--r-- 1 root root 125974 May 13 16:41 kmod-drbd83-8.3.8-1.el5.centos.i686.rpm

-rw-r--r-- 1 root root 60458 May 13 16:41 libesmtp-1.0.4-5.el5.i386.rpm

-rw-r--r-- 1 root root 162247449 May 13 16:41 mysql-5.5.15-linux2.6-i686.tar.gz

-rw-r--r-- 1 root root 207085 May 13 16:41 openais-1.1.3-1.6.el5.i386.rpm

-rw-r--r-- 1 root root 94614 May 13 16:41 openaislib-1.1.3-1.6.el5.i386.rpm

-rw-r--r-- 1 root root 796813 May 13 16:41 pacemaker-1.1.5-1.1.el5.i386.rpm

-rw-r--r-- 1 root root 207925 May 13 16:41 pacemaker-cts-1.1.5-1.1.el5.i386.rpm

-rw-r--r-- 1 root root 332026 May 13 16:41 pacemaker-libs-1.1.5-1.1.el5.i386.rpm

-rw-r--r-- 1 root root 32818 May 13 16:41 perl-TimeDate-1.16-5.el5.noarch.rpm

-rw-r--r-- 1 root root 388632 May 13 16:41 resource-agents-1.0.4-1.1.el5.i386.rpm

[root@node1 ~]# yum localinstall *.rpm -y --nogpgcheck

[root@node1 ~]# scp *.rpm node2:/root

[root@node2 ~]# yum localinstall *.rpm -y --nogpgcheck

在各节点上增加一个大小类型都相关的drbd设备（sdb1）

node1

需要添加一块小硬盘：

[root@node1 ~]# fdisk /dev/sdb

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

The number of cylinders for this disk is set to 1044.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n

Command action

e extended

p primary partition (1-4)

Partition number (1-4): 1

First cylinder (1-1044, default 1):

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-1044, default 1044): +1G

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.

[root@node1 ~]# partprobe /dev/sdb

[root@node1 ~]# cat /proc/partitions

major minor #blocks name

8 0 20971520 sda

8 1 104391 sda1

8 2 2096482 sda2

8 3 10482412 sda3

8 16 8388608 sdb

8 17 987966 sdb1

node2与node1一样

配置drbd

node1

复制样例配置文件为即将使用的配置文件:

[root@node1 ~]# cp /usr/share/doc/drbd83-8.3.8/drbd.conf /etc/

[root@node1 ~]# cd /etc/drbd.d/

将文件global_common.conf 备份:

[root@node1 drbd.d]# cp global_common.conf global_common.conf.bak

[root@node1 drbd.d]# vim global_common.conf

global {

usage-count no;

}

common {

protocol C;

handlers {

}

startup {

wfc-timeout 120;

degr-wfc-timeout 120;

}

disk {

on-io-error detach;

}

net {

cram-hmac-alg "sha1";

shared-secret "mydrbdlab";

}

syncer {

rate 100M;

}

定义mysql的资源:

[root@node1 drbd.d]# vim mysql.res

resource mysql {

on node1.a.com {

device /dev/drbd0;

disk /dev/sdb1;

address 192.168.10.10:7789;

meta-disk internal;

}

on node2.a.com {

device /dev/drbd0;

disk /dev/sdb1;

address 192.168.10.20:7789;

meta-disk internal;

}

将以上的drbd.*文件都拷贝到node2上面:

[root@node1 drbd.d]# scp -r /etc/drbd.* node2:/etc/

drbd.conf 100% 133 0.1KB/s 00:00

global_common.conf.bak 100% 1418 1.4KB/s 00:00

global_common.conf 100% 1548 1.5KB/s 00:00

mysql.res 100% 241 0.2KB/s 00:00

node1初始化定义的mysql的资源并启动相应的服务:

[root@node1 drbd.d]# drbdadm create-md mysql

Writing meta data...

initializing activity log

NOT initialized bitmap

New drbd meta data block successfully created.

[root@node1 drbd.d]# service drbd start

Starting DRBD resources: [ n(mysql) ]..........

***************************************************************

DRBD's startup script waits for the peer node(s) to appear.

- In case this node was already a degraded cluster before the

reboot the timeout is 120 seconds. [degr-wfc-timeout]

- If the peer was available before the reboot the timeout will

expire after 120 seconds. [wfc-timeout]

(These values are for resource 'mysql'; 0 sec -> wait forever)

To abort waiting enter 'yes' [ 25]:

使用drbd-overview命令来查看启动状态:

[root@node1 drbd.d]# drbd-overview

0:mysql Connected Secondary/Secondary Inconsistent/Inconsistent C r----

node2

[root@node2 ~]# drbdadm create-md mysql

Writing meta data...

initializing activity log

NOT initialized bitmap

New drbd meta data block successfully created.

[root@node2 ~]# service drbd start

[root@node2 drbd.d]# drbd-overview

0:mysql Connected Secondary/Secondary Inconsistent/Inconsistent C r----

从上面的信息中可以看出此时两个节点均处于Secondary状态。于是，我们接下来需要将其中一个节点设置为Primary，这里将node1设置为主节点

[root@node1 drbd.d]# drbdadm -- --overwrite-data-of-peer primary mysql

[root@node1 drbd.d]# drbd-overview

0:mysql SyncSource Primary/Secondary UpToDate/Inconsistent C r----

[=======>............] sync'ed: 40.5% (592824/987896)K delay_probe: 24

[root@node2 ~]# drbd-overview

0:mysql Connected Secondary/Primary UpToDate/UpToDate C r----

[root@node2 ~]# cat /proc/drbd

version: 8.3.8 (api:88/proto:86-94)

GIT-hash: d78846e52224fd00562f7c225bcc25b2d422321d build by [email protected], 2010-06-04 08:04:16

0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate C r----

ns:0 nr:987896 dw:987896 dr:0 al:0 bm:61 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0

查看同步过程：

[root@node1 drbd.d]# watch -n 1 'cat /proc/drbd' (Ctrl+c退出)

创建文件系统（只可以在primary节点上进行）：

[root@node1 drbd.d]# mkfs -t ext3 /dev/drbd0 格式化

mke2fs 1.39 (29-May-2006)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

123648 inodes, 246974 blocks

12348 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=255852544

8 block groups

32768 blocks per group, 32768 fragments per group

15456 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376

Writing inode tables: done

Creating journal (4096 blocks): mkdir done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

[root@node1 drbd.d]# mkdir /mysqldata

[root@node1 drbd.d]# mount /dev/drbd0 /mysqldata/

[root@node1 drbd.d]# cd /mysqldata/

[root@node1 mysqldata]# touch f1 f2

[root@node1 mysqldata]# ll /mysqldata/

total 16

-rw-r--r-- 1 root root 0 May 13 18:24 f1

-rw-r--r-- 1 root root 0 May 13 18:24 f2

drwx------ 2 root root 16384 May 13 18:23 lost+found

[root@node1 mysqldata]# cd

[root@node1 ~]# umount /mysqldata/

将node1设置为secondary节点：

[root@node1 ~]# drbdadm secondary mysql

[root@node1 ~]# drbd-overview

0:mysql Connected Secondary/Secondary UpToDate/UpToDate C r----

将node2设置为primary节点：

[root@node2 ~]# drbdadm primary mysql

[root@node2 ~]# drbd-overview

0:mysql Connected Primary/Secondary UpToDate/UpToDate C r----

[root@node2 ~]# mkdir /mysqldata

[root@node2 ~]# mount /dev/drbd0 /mysqldata/

[root@node2 ~]# ll /mysqldata/

total 16

-rw-r--r-- 1 root root 0 May 13 18:24 f1

-rw-r--r-- 1 root root 0 May 13 18:24 f2

drwx------ 2 root root 16384 May 13 18:23 lost+found

[root@node2 ~]# umount /mysqldata/

mysql的安装和配置

添加用户和组：

[root@node1 ~]# groupadd -r mysql

You have new mail in /var/spool/mail/root

[root@node1 ~]# useradd -g mysql -r mysql

由于主设备才能读写，挂载，故我们还要设置node1为主设备，node2为从设备：[root@node2 ~]# drbdadm secondary mysql

You have new mail in /var/spool/mail/root

node1

[root@node1 ~]# drbdadm primary mysql

[root@node1 ~]# drbd-overview

0:mysql Connected Primary/Secondary UpToDate/UpToDate C r----

挂载drbd设备：

[root@node1 ~]# mount /dev/drbd0 /mysqldata/

[root@node1 ~]# mkdir /mysqldata/data

data目录要用存放mysql的数据，故改变其属主属组：

[root@node1 ~]# chown -R mysql.mysql /mysqldata/data/

查看：

[root@node1 ~]# ll /mysqldata/

total 20

drwxr-xr-x 2 mysql mysql 4096 May 13 18:52 data

-rw-r--r--1 root root 0 May 13 18:35 f1

-rw-r--r--1 root root 0 May 13 18:35 f2

drwx------2 root root 16384 May 13 18:34 lost+found

安装mysql

[root@node1 ~]# tarzxvf mysql-5.5.15-linux2.6-i686.tar.gz -C /usr/local/

[root@node1 ~]# cd /usr/local/

[root@node1 local]# ln -sv mysql-5.5.15-linux2.6-i686/ mysql

create symbolic link `mysql' to `mysql-5.5.15-linux2.6-i686/'

[root@node1 local]# cd mysql

[root@node1 mysql]# chown -R mysql.mysql .

初始化mysql数据库：

[root@node1 mysql]# scripts/mysql_install_db --user=mysql --datadir=/mysqldata/data

[root@node1 mysql]# chown -R root .

为mysql提供主配置文件：

[root@node1 mysql]# cp support-files/my-large.cnf /etc/my.cnf

并修改此文件中thread_concurrency的值为你的CPU个数乘以2，比如这里使用如下行：

[root@node1 mysql]# vim /etc/my.cnf

thread_concurrency = 2

另外还需要添加如下行指定mysql数据文件的存放位置

datadir = /mysqldata/data

为mysql提供sysv服务脚本，使其能使用service命令：

[root@node1 mysql]# cp support-files/mysql.server /etc/rc.d/init.d/mysqld

node2上的配置文件，sysv服务脚本和此相同，故直接复制过去：

[root@node1 mysql]# scp /etc/my.cnf node2:/etc/

my.cnf 100% 4691 4.6KB/s 00:00

[root@node1 mysql]# scp /etc/rc.d/init.d/mysqld node2:/etc/rc.d/init.d/

mysqld 100% 10KB 10.4KB/s 00:00

添加至服务列表：

[root@node1 mysql]# chkconfig --add mysqld

确保开机不能自动启动，我们要用CRM控制：

[root@node1 mysql]# chkconfig mysqld off

而后就可以启动服务测试使用了：

[root@node1 mysql]# service mysqld start

Starting MySQL...... [ OK ]

测试之后关闭服务：

[root@node1 mysql]# service mysqld stop

Shutting down MySQL.. [ OK ]

[root@node1 mysql]# ls /mysqldata/data/

ib_logfile0 ib_logfile1 ibdata1 mysql mysql-bin.000001 mysql-bin.index node1.a.com.err performance_schema test

为了使用mysql的安装符合系统使用规范，并将其开发组件导出给系统使用，这里还需要进行如下步骤：

输出mysql的man手册至man命令的查找路径

[root@node1 mysql]# vim /etc/man.config

添加如下行即可

MANPATH /usr/local/mysql/man

输出mysql的头文件至系统头文件路径/usr/include，，这可以通过简单的创建链接实现：

[root@node1 mysql]# ln -sv /usr/local/mysql/include /usr/include/mysql

create symbolic link `/usr/include/mysql' to `/usr/local/mysql/include'

输出mysql的库文件给系统库查找路径：（文件只要是在/etc/ld.so.conf.d/下并且后缀是.conf就可以）：

[root@node1 mysql]# echo '/usr/local/mysql/lib/'> /etc/ld.so.conf.d/mysql.conf

让系统重新载入系统库：

[root@node1 mysql]# ldconfig

修改PATH环境变量，让系统所有用户可以直接使用mysql的相关命令：

PATH=$PATH:/usr/local/mysql/bin

重新读取环境变量：

[root@node1 mysql]# vim /etc/profile

[root@node1 mysql]# . /etc/profile

[root@node1 mysql]# echo $PATH

/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/mysql/bin

[root@node1 mysql]# umount /mysqldata/

node2

[root@node2 ~]# groupadd -r mysql

[root@node2 ~]# useradd -g mysql -r mysql

由于主设备才能读写，挂载，故我们还要设置node2为主设备，node1为从设备：

[root@node1 mysql]# drbdadm secondary mysql

[root@node2 ~]# drbdadm primary mysql

[root@node2 ~]# mount /dev/drbd0 /mysqldata/

[root@node2 ~]# ls /mysqldata/

data f1 f2 lost+found

[root@node2 ~]# tar -zxvf mysql-5.5.15-linux2.6-i686.tar.gz -C /usr/local/

[root@node2 ~]# cd /usr/local/

[root@node2 local]# ln -sv mysql-5.5.15-linux2.6-i686/ mysql

create symbolic link `mysql' to `mysql-5.5.15-linux2.6-i686/'

[root@node2 local]# cd mysql

[root@node2 mysql]# chown -R root:mysql .

[root@node2 mysql]# cp support-files/my-large.cnf /etc/my.cnf

cp: overwrite `/etc/my.cnf'? n

[root@node2 mysql]# cp support-files/mysql.server /etc/rc.d/init.d/mysqld

cp: overwrite `/etc/rc.d/init.d/mysqld'? n

[root@node2 mysql]# chkconfig --add mysqld

[root@node2 mysql]# chkconfig mysqld off

[root@node2 mysql]# service mysqld start

Starting MySQL...... [ OK ]

[root@node2 mysql]# ls /mysqldata/data/

ib_logfile0 ibdata1 mysql-bin.000001 mysql-bin.index node2.a.com.err performance_schema

ib_logfile1 mysql mysql-bin.000002 node1.a.com.err node2.a.com.pid test

[root@node2 mysql]# service mysqld stop

Shutting down MySQL.. [ OK ]

为了使用mysql的安装符合系统使用规范，并将其开发组件导出给系统使用，

这里还需要进行一些类似node1上的操作，由于方法完全相同，不再阐述！

卸载设备：

[root@node2 mysql]# umount /dev/drbd0

corosync+pacemaker的安装和配置

node1

[root@node1 ~]# cd /etc/corosync/

[root@node1 corosync]# cp corosync.conf.example corosync.conf

[root@node1 corosync]# vim corosync.conf

compatibility: whitetank

totem { //这是用来传递心跳时的相关协议的信息

version: 2

secauth: off

threads: 0

interface {

ringnumber: 0

bindnetaddr: 192.168.2.0 //我们只改动这里就行啦

mcastaddr: 226.94.1.1

mcastport: 5405

}

logging {

fileline: off

to_stderr: no //是否发送标准出错

to_logfile: yes //日志

to_syslog: yes //系统日志（建议关掉一个），会降低性能

logfile: /var/log/cluster/corosync.log //需要手动创建目录cluster

debug: off // 排除时可以起来

timestamp: on //日志中是否记录时间

//******以下是openais的东西，可以不用代开*****//

logger_subsys {

subsys: AMF

debug: off

}

amf {

mode: disabled

}

//*********补充一些东西，前面只是底层的东西，因为要用pacemaker ******//

service {

ver: 0

name: pacemaker

use_mgmtd: yes

}

//******虽然用不到openais ，但是会用到一些子选项********//

aisexec {

user: root

group: root

}

创建cluster目录：

[root@node1 corosync]# mkdir /var/log/cluster

为了便面其他主机加入该集群，需要认证，生成一authkey：

[root@node1 corosync]# corosync-keygen

Corosync Cluster Engine Authentication key generator.

Gathering 1024 bits for key from /dev/random.

Press keys on your keyboard to generate entropy.

Press keys on your keyboard to generate entropy (bits = 888).

Press keys on your keyboard to generate entropy (bits = 952).

Press keys on your keyboard to generate entropy (bits = 1016).

Writing corosync key to /etc/corosync/authkey.

[root@node1 corosync]# ll

total 28

-rw-r--r-- 1 root root 5384 Jul 28 2010 amf.conf.example

-r-------- 1 root root 128 May 13 20:50 authkey

-rw-r--r-- 1 root root 556 May 13 20:49 corosync.conf

-rw-r--r-- 1 root root 436 Jul 28 2010 corosync.conf.example

drwxr-xr-x 2 root root 4096 Jul 28 2010 service.d

drwxr-xr-x 2 root root 4096 Jul 28 2010 uidgid.d

将node1节点上的文件拷贝到节点node2上面（记住要带-p）

[root@node1 corosync]# scp -p authkey corosync.conf node2:/etc/corosync/

authkey 100% 128 0.1KB/s 00:00

corosync.conf 100% 556 0.5KB/s 00:00

[root@node1 corosync]# ssh node2 'mkdir /var/log/cluster'

在node1和node2节点上面启动corosync 的服务：

[root@node1 corosync]# service corosync start

Starting Corosync Cluster Engine (corosync): [ OK ]

[root@node2 ~]# service corosync start

Starting Corosync Cluster Engine (corosync): [ OK ]

验证corosync引擎是否正常启动了

[root@node1 corosync]# grep -i -e "corosync cluster engine" -e "configuration file" /var/log/messages

Feb 8 16:33:15 localhost smartd[2928]: Opened configuration file /etc/smartd.conf

Feb 8 16:33:15 localhost smartd[2928]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

Feb 8 16:45:09 localhost smartd[3395]: Opened configuration file /etc/smartd.conf

Feb 8 16:45:09 localhost smartd[3395]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

Feb 8 17:13:11 localhost smartd[3386]: Opened configuration file /etc/smartd.conf

Feb 8 17:13:11 localhost smartd[3386]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

Mar 19 23:33:34 localhost smartd[3385]: Opened configuration file /etc/smartd.conf

Mar 19 23:33:34 localhost smartd[3385]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

May 6 09:12:46 localhost smartd[3377]: Opened configuration file /etc/smartd.conf

May 6 09:12:46 localhost smartd[3377]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

May 6 15:37:51 localhost smartd[3408]: Opened configuration file /etc/smartd.conf

May 6 15:37:51 localhost smartd[3408]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

May 8 09:31:06 localhost smartd[3416]: Opened configuration file /etc/smartd.conf

May 8 09:31:06 localhost smartd[3416]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

May 8 09:47:42 node1 smartd[3353]: Opened configuration file /etc/smartd.conf

May 8 09:47:42 node1 smartd[3353]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices

May 8 12:10:18 node1 corosync[7838]: [MAIN ] Corosync Cluster Engine ('1.2.7'): started and ready to provide service.

May 8 12:10:18 node1 corosync[7838]: [MAIN ] Successfully read main configuration file '/etc/corosync/corosync.conf'.

查看初始化成员节点通知是否发出

[root@node1 corosync]# grep -i totem /var/log/messages

May 8 12:10:18 node1 corosync[7838]: [TOTEM ] Initializing transport (UDP/IP).

May 8 12:10:18 node1 corosync[7838]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).

May 8 12:10:19 node1 corosync[7838]: [TOTEM ] The network interface [192.168.10.10] is now up.

May 8 12:10:24 node1 corosync[7838]: [TOTEM ] Process pause detected for 899 ms, flushing membership messages.

May 8 12:10:24 node1 corosync[7838]: [TOTEM ] A processor joined or left the membership and a new membership was formed.

May 8 12:10:24 node1 corosync[7838]: [TOTEM ] A processor failed, forming new configuration.

May 8 12:10:24 node1 corosync[7838]: [TOTEM ] A processor joined or left the membership and a new membership was formed.

May 8 12:10:32 node1 corosync[7838]: [TOTEM ] A processor failed, forming new configuration.

May 8 12:10:32 node1 corosync[7838]: [TOTEM ] A processor joined or left the membership and a new membership was formed.

May 8 12:12:03 node1 corosync[7838]: [TOTEM ] A processor failed, forming new configuration.

May 8 12:12:03 node1 corosync[7838]: [TOTEM ] A processor joined or left the membership and a new membership was formed.

May 8 12:12:15 node1 corosync[7838]: [TOTEM ] A processor joined or left the membership and a new membership was formed.

检查过程中是否有错误产生

[root@node1 corosync]# grep -i error: /var/log/messages |grep -v unpack_resources

Feb 8 17:03:46 localhost kernel: sd 1:0:0:0: SCSI error: return code = 0x00010000

检查pacemaker时候已经启动了

[root@node1 corosync]# grep -i pcmk_startup /var/log/messages

May 8 12:10:23 node1 corosync[7838]: [pcmk ] info: pcmk_startup: CRM: Initialized

May 8 12:10:23 node1 corosync[7838]: [pcmk ] Logging: Initialized pcmk_startup

May 8 12:10:23 node1 corosync[7838]: [pcmk ] info: pcmk_startup: Maximum core file size is: 4294967295

May 8 12:10:23 node1 corosync[7838]: [pcmk ] info: pcmk_startup: Service: 9

May 8 12:10:23 node1 corosync[7838]: [pcmk ] info: pcmk_startup: Local hostname: node1.a.com

node2

查看初始化成员节点通知是否发出：

[root@node2 ~]# grep -i totem /var/log/messages

May 8 12:12:16 node2 corosync[7817]: [TOTEM ] Initializing transport (UDP/IP).

May 8 12:12:16 node2 corosync[7817]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).

May 8 12:12:16 node2 corosync[7817]: [TOTEM ] The network interface [192.168.10.20] is now up.

May 8 12:12:18 node2 corosync[7817]: [TOTEM ] A processor joined or left the membership and a new membership was formed.

查看corosync的状态：

[root@node2 ~]# service corosync status

corosync (pid 7817) is running...

验证corosync引擎是否正常启动了：

[root@node2 ~]# grep -i -e "corosync cluster engine" -e "configuration file" /var/log/messages