Search Engine: Elastic

Article ID: 128676, created on Apr 15, 2016, last review on Apr 15, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5


NG Load Balancer experiences a complete outage, all routing rules stop serving requests.

The following sequence of messages appears in /var/log/messages:

Jan 19 22:54:58 loadbalancer2 nanny[8788]: [inactive] shutting down due to connection failure
Jan 19 22:54:58 loadbalancer2 nanny[8788]: /sbin/ipvsadm command failed!
Jan 19 22:54:58 loadbalancer2 lvs[8779]: nanny died! shutting down lvs
Jan 19 22:54:58 loadbalancer2 lvs[8779]: shutting down virtual service 32
Jan 19 22:54:58 loadbalancer2 nanny[8786]: Terminating due to signal 15

This may happen after removing an NG node from the load balancer using the following command:

~# ipvsadm -d -f 100 -r


In scope of Odin Service Automation platform, the issue is going to be addressed in scope of POA-100010, LVS configuration will allow removing a single routing entry without affecting all others.

Originally the issue derives from the following Red Hat behavior:
739223 Nanny crashes and shuts LVS down if a service is deleted using ipvsadm and then the corresponding real server goes down.


In case an outage occurs, LVS services should be restarted:

# service pulse start

In order to avoid the outage during maintenance for any NG node, follow these instructions:

  1. Stop the Apache service on the node. Load Balancer will not redirect any request to that node if the Apache service is not running.

    # service httpd stop
  2. Once the maintenance is done, start the Apache service.

    # service httpd start

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF