Search Engine: Elastic

Article ID: 129431, created on Sep 14, 2016, last review on Sep 14, 2016

  • Applies to:
  • Operations Automation 6.0


Customer performed NG load balancer restart during maintenance. After LB went online, all sites cannot load: despite 200 OK status is being returned, no content is displayed in browser.

In the load balancer's messages log the following entries could be found:

pulse: SIOCGIFADDR failed: Cannot assign requested address
pulse: SIOCGIFADDR failed: Cannot assign requested address
pulse[6988]: We are backup node and backup is marked inactive -- exiting pulse

Pulse service is not started:

# service pulse status
pulse dead but subsys locked


Internal (backnet) address of Load Balancer was lost after reboot. Pulse finds discrepancy between actual network configuration and one defined in config file /etc/sysconfig/ha/ and interrupts startup. Without pulse service, LB does not function at all as pulse is responsible for starting other LVS mechanisms: lvsd, nanny, ipvsadm.


Check the primary address defined in /etc/sysconfig/ha/ primary =

Configure this address on one of interfaces of LB or pass this task to local network administrator. Ensure that Web nodes of cluster are reachable via backnet. Then you may start pulse service:

# service pulse start

And check that load balancer started to route requests:

# ipvsadm -ln

IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
FWM  100 wlc persistent 20 mask
  ->             Route   320    110        48
  ->             Route   160    61         15
  ->             Route   320    108        52

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF