Analysis of open source load balanced LVS random self-starting anomaly diagnosis case
In response to the country's call to advocate the IT information system hardware and software facilities of security, autonomy and controllability, our company is also committed to promoting it software and hardware localization and open source. Therefore, the open source load Balancer software LVS is introduced and several LVS systems are deployed in production. In the use of the process found a more strange problem, some LVS system after the configuration of random self-boot, the operating system restart can normally start with the server but there is a set of systems but not with the operating system self-booting services. To solve this problem, we have the following.
First, the problem phenomenon
The failure of this set of LVS is described as follows:
The LVS is configured as a system service normally and is set to 2345 boot-up, but after restarting the server The Discovery service did not start as expected. By viewing the system's diagnostic log tail–f/var/log/messages, you find that Ipvs frequently brushes logs to messages files.
The specific error message is as follows: Keepalived_healthcheckers:IPVS:Can ' t initialize ipvs:protocol not available. The service returns to normal after manually performing IPVSADM-LN.
Second, the analysis process:
1. The diagnostic log prompts us to confirm that the root cause of the problem is that the Ipvs module is not loaded properly when the system restarts
2. By executing the following command Lsmod|grep Ip_vs also further confirms that the module has not been loaded into the kernel
So what is the reason for the Ipvs module not being loaded into the Linux kernel?
Third, the specific idea of debug:
1. Test setup reboot does not start keepalived, only start Ipvsadm view can start, restart after the problem is still, stating that the problem is not on the keepalived;
2. Replace the higher version of the Ipvsadm, replaced by 1.25, the problem is still after testing;
3. Start to suspect is the cause of the installation sequence, so ipvsadm two versions are tested and keepalived different installation sequence, with the order of start, the problem remains;
4. By accident using the/etc/init.d/ipvsadm Start command to start the Ipvs service and restart the operating system again, Ipvsadm successfully pulled up the system, save the snapshot immediately.
5. Then check the Ipvsadm startup script, the script is cumbersome, involving a lot of files, found a configuration file/etc/sysconfig/ipvsadm. Suddenly came the inspiration, is not the configuration file has the problem. After searching the Ipvsadm file, found the problem, under/etc/sysconfig a configuration file;
6. Manually set up Ipvsadm profile Touch Ipvsadm, then restart the system, IPVSADM service successfully started
Iv. Optimal Solutions
Execute the Service ipvsadm Save command after you deploy and configure the completion LVS
V. Causes of the problem
The associated Deployer did not follow the deployment manual to implement the missing steps and the random self-boot of the Ipvs depends on the relevant configuration file.
http://www.bkjia.com/PHPjc/1090009.html www.bkjia.com true http://www.bkjia.com/PHPjc/1090009.html techarticle Open Source Load Balancing LVs random self-starting Anomaly diagnosis column analysis in response to the country's call, advocating it information system hardware and software facilities of security, autonomy and controllability, our company is also in the effort ...
