南非蚂蚁，著名Linux专家，知名IT作家。毕业于西安电子科技大学通信工程专业，爱好计算机，毕业后从事计算机行业。曾就职于新浪网、阿里云（万网），任职系统架构师。曾出版畅销书《循序渐进Linux》、《高性能Linux服务器构建实战》作者。
发布时间：2016-01-22 15:49:36
我们的线上web服务器在访问量很大时，就会出现网络连接丢包的问题，通过dmesg命令查看日志，发现如下信息：kernel: ip_conntrack: table full, dropping packet.kernel: printk: 1 messages suppressed.kernel: ip_conntrack: table full, dropping packet.kernel: printk: 2 messages suppressed.kernel: ip_conntr.........【阅读全文】
exitgogo2016-02-03 15:17
saup007：双主MySQL配置Keepalived，2个角色都为BACKUP,
A节点：
vrrp_script chk_mysql_server {
#script "/opt/keepalived/script/chk_mysql_server.sh"
script "killall -0 mysqld"
interval 30 # 检测时间为30s
weight 21
}
vrrp_instance VI_1 {
state BACKUP
interface eth1
virtual_router_id 59
priority 100
advert_int 1
nopreempt
#mcas_src_ip 172.19.1.201
authentication {
auth_type PASS
auth_pass 1111
}
notify_master "/opt/keepalived/script/master.sh"
notify_backup "/opt/keepalived/script/backup.sh"
notify_fault "/opt/keepalived/script/fault.sh"
notify_stop "/opt/keepalived/script/stop.sh"
track_script {
chk_mysql_server
}
virtual_ipaddress {
172.19.1.249/24 dev eth1 scope global label eth1:0
}
}
B节点：
priority 90
#nopreempt
当停掉A的MySQL，正常切换到B，当把A MySQL启来后，vip依然在B，这个符合逻辑，但把A MySQL启来后，再去停掉B MySQL，VIP却没有飘移到A上，why？
vrrp_script chk_mysql_server {
#script "/opt/keepalived/script/chk_mysql_server.sh"
script "killall -0 mysqld"
interval 30 # 检测时间为30s
weight 21
}
这里面的权重设置有问题，修改weight值
saup0072015-08-27 15:16
双主MySQL配置Keepalived，2个角色都为BACKUP,
A节点：
vrrp_script chk_mysql_server {
#script "/opt/keepalived/script/chk_mysql_server.sh"
script "killall -0 mysqld"
interval 30 # 检测时间为30s
weight 21
}
vrrp_instance VI_1 {
state BACKUP
interface eth1
virtual_router_id 59
priority 100
advert_int 1
nopreempt
#mcas_src_ip 172.19.1.201
authentication {
auth_type PASS
auth_pass 1111
}
notify_master "/opt/keepalived/script/master.sh"
notify_backup "/opt/keepalived/script/backup.sh"
notify_fault "/opt/keepalived/script/fault.sh"
notify_stop "/opt/keepalived/script/stop.sh"
track_script {
chk_mysql_server
}
virtual_ipaddress {
172.19.1.249/24 dev eth1 scope global label eth1:0
}
}
B节点：
priority 90
#nopreempt
当停掉A的MySQL，正常切换到B，当把A MySQL启来后，vip依然在B，这个符合逻辑，但把A MySQL启来后，再去停掉B MySQL，VIP却没有飘移到A上，why？
