keepalived日志报错

sjzwyb

各位，安装了keepalived做主备双机，安装完成后，在日志中有如下报错：

May 16 14:30:25 Probe1 Keepalived_vrrp[27929]: Process [28014] didn't respond to SIGTERM

不知道是什么原因，请高手指点！

下面是keepalived.conf配置：

服务器A：

[root@somcA keepalived]# cat keepalived.conf
! Configuration File for keepalived

global_defs {
   notification_email {
     root@localhost
   }
   notification_email_from root@localhost
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id MY_KEEPALIVED
}
vrrp_script chk_alive {
   script "/usr/local/keepalived/etc/keepalived/chk_alive.sh"
   interval 1
   }
vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 55
    priority 100
    advert_int 1
#    preempt
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    track_interface {
        eth0
        eth1
    }
    virtual_ipaddress {
        10.215.54.31
    }
    track_script {
        chk_alive
    }  
#notify_master "/usr/local/keepalived/etc/keepalived/notify.sh master"
#notify_backup "/usr/local/keepalived/etc/keepalived/notify.sh backup"
#notify_fault  "/usr/local/keepalived/etc/keepalived/notify.sh fault"
}
[root@somcA keepalived]#

服务器B:

[root@somcA keepalived]# cat keepalived.conf
! Configuration File for keepalived

global_defs {
   notification_email {
     root@localhost
   }
   notification_email_from root@localhost
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id MY_KEEPALIVED
}
vrrp_script chk_alive {
   script "/usr/local/keepalived/etc/keepalived/chk_alive.sh"
   interval 1
   }
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 55
    priority 99
    advert_int 1
#    preempt
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    track_interface {
        eth0
        eth1
    }
    virtual_ipaddress {
        10.215.54.31
    }
    track_script {
        chk_alive
    }  
#notify_master "/usr/local/keepalived/etc/keepalived/notify.sh master"
#notify_backup "/usr/local/keepalived/etc/keepalived/notify.sh backup"
#notify_fault  "/usr/local/keepalived/etc/keepalived/notify.sh fault"
}
[root@somcA keepalived]#

laoadiy

确保一下master和backup对外的网卡都是eth0

sjzwyb

这个已经确认过了，均为eth0

hncscwc

chk_alive.sh 或者 notify.sh 执行是不是比较耗时?

liwei6998

sjzwyb，你这个错误怎么解决的？我现在也有这个错误。

ecitdasuonan

/usr/local/keepalived/etc/keepalived/chk_alive.sh脚本内容，是不是脚本在interval 1内执行不完，然后下一秒又要去执行脚本，造成重复运行，然后keepalived内置的子线程检查函数报的错呢？我的就是这个原因。

  255 int
  256 misc_check_child_timeout_thread(thread_t * thread)
  257 {
  258         pid_t pid;
  259
  260         if (thread->type != THREAD_CHILD_TIMEOUT)
  261                 return 0;
  262
  263         /* OK, it still hasn't exited. Now really kill it off. */
  264         pid = THREAD_CHILD_PID(thread);
  265         if (kill(pid, SIGKILL) < 0) {
  266                 /* Its possible it finished while we're handing this */
  267                 if (errno != ESRCH)
  268                         DBG("kill error: %s", strerror(errno));
  269                 return 0;
  270         }
  271
  272         log_message(LOG_WARNING, "Process [%d] didn't respond to SIGTERM", pid);
  273         waitpid(pid, NULL, 0);
  274
  275         return 0;
  276 }

mgunix

回复 5# liwei6998


    把interval  时间改长一点

wq4113

嗯，学习了