piranha load balancer failover Post: 302576085

Sponsored Content

Top Forums UNIX for Advanced & Expert Users piranha load balancer failover Post 302576085 by robo on Wednesday 23rd of November 2011 02:54:01 PM

11-23-2011

Registered User

piranha load balancer failover

we use piranha load balancer with two nodes

even the primary node is running fine and up failover happend to secondary node
this happend quite few times ehy node2 cannot talk to node1

what logs are to be checked and investigate why failover occured

Code:

  pulse[7340]: partner dead: activating lvs
Nov 21 10:53:05 node2 pulse[7340]: partner active: deactivating lvs
Nov 21 10:53:11 node2 pulse[27219]: gratuitous lvs arps finished
Nov 21 16:25:53 node2 pulse[7340]: Terminating due to signal 15
Nov 21 16:25:53 node2 pulse: pulse shutdown succeeded
Nov 23 14:15:11 node2 pulse: pulse shutdown failed
Nov 23 14:15:11 node2 pulse: SIOCGIFADDR failed: Cannot assign requested address
Nov 23 14:15:11 node2 pulse[5552]: STARTING PULSE AS BACKUP
Nov 23 14:15:11 node2 pulse: pulse startup succeeded
Nov 13 20:07:17 node2 pulse[7340]: partner dead: activating lvs
Nov 13 20:07:20 node2 pulse[7340]: partner active: deactivating lvs
Nov 13 20:07:22 node2 pulse[2103]: gratuitous lvs arps finished
Oct 30 20:09:59 node2 pulse[7340]: partner dead: activating lvs
Oct 30 20:10:06 node2 pulse[24269]: gratuitous lvs arps finished
Oct 30 20:11:17 node2 pulse[7340]: partner active: deactivating lvs
Oct 30 20:39:47 node2 pulse[7340]: partner dead: activating lvs
Oct 30 20:39:48 node2 pulse[7340]: partner active: deactivating lvs
Oct 30 20:39:52 node2 pulse[25055]: gratuitous lvs arps finished
Nov  5 22:40:16 node2 pulse[7340]: partner dead: activating lvs
Nov  5 22:40:21 node2 pulse[26812]: gratuitous lvs arps finished

there failover occured whan node1 is aactive on the network

can some one help me to find why this happned

Last edited by robo; 11-23-2011 at 03:59 PM..

robo

View Public Profile for robo

Find all posts by robo

5 More Discussions You Might Find Interesting

1. Programming

Load Balancer

Halo mates, I m going to write a load balancer with C. Does anybody know some good reference on this? Cheers, Elton

2. AIX

hacmp ip load balancer failover

Hi All, How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive). Any idea, please. Thanks in advance.

3. Red Hat

What is the Best Load Balancer for Linux?

Hi, What's the best load balancer for Linux (CentOS, SuSE) according to your personal experience? Linux Virtual Server (LVS) is a famous one, but their download site has not been updated since 2007. Their web and mailing list are so quiet. Is the Ultra Monkey project including LVS...

4. Linux

Server Load balancer

Hello Guys, Hope you all doing well . :) I was checking load balance command (uptime)on VM server and got below output. # uptime 07:08:40 up 52 min, 2 users,a load average: 0.45, 0.11, 0.03 A :How we can calculate load average? Thank you in advance !! Cheers:) Dont forget...

5. Virtualization and Cloud Computing

A load balancer for Nomachine NX

Hello, in case somebody has a NoMachine NX cluster, and is suffering from its dumb round-robin dispatcher, here is a solution: nxpub (NX Pluggable User Balancer). It should run on all LUnix OS. Scripts for install/uninstall are supplied. While tested with NX 3 (NX 3.5 is the latest), it might...

LEARN ABOUT SUSE

pulse-client.conf

pulse-client.conf(5)						File Formats Manual					      pulse-client.conf(5)

NAME

       pulse-client.conf - PulseAudio client configuration file

SYNOPSIS

       ~/.pulse/client.conf

       /etc/pulse/client.conf

DESCRIPTION

       The  PulseAudio	client library reads configuration directives from a file ~/.pulse/client.conf on startup and when that file doesn't exist
       from /etc/pulse/client.conf.

       The configuration file is a simple collection of variable declarations. If the configuration file  parser  encounters  either  ;  or  #	it
       ignores the rest of the line until its end.

       For the settings that take a boolean argument the values true, yes, on and 1 are equivalent, resp. false, no, off, 0.

DIRECTIVES

       default-sink=  The default sink to connect to. If specified overwrites the setting in the daemon. The environment variable $PULSE_SINK how-
       ever takes precedence.

       default-source= The default source to connect to. If specified overwrites the setting in the daemon. The environment variable $PULSE_SOURCE
       however takes precedence.

       default-server= The default sever to connect to. The environment variable $PULSE_SERVER takes precedence.

       autospawn= Autospawn a PulseAudio daemon when needed. Takes a boolean value, defaults to "yes".

       daemon-binary= Path to the PulseAudio daemon to run when autospawning. Defaults to a path configured at compile time.

       extra-arguments= Extra arguments to pass to the PulseAudio daemon when autospawning. Defaults to --log-target=syslog

       cookie-file= Specify the path to the PulseAudio authentication cookie. Defaults to ~/.pulse-cookie.

       enable-shm= Enable data transfer via POSIX shared memory. Takes a boolean argument, defaults to yes.

       shm-size-bytes=	Sets the shared memory segment size for clients, in bytes. If left unspecified or is set to 0 it will default to some sys-
       tem-specific default, usually 64 MiB. Please note that usually there is no need to change this value, unless you are running an	OS  kernel
       that does not do memory overcommit.

AUTHORS

       The PulseAudio Developers <mzchyfrnhqvb (at) 0pointer (dot) net>; PulseAudio is available from http://pulseaudio.org/

SEE ALSO

       pulse-daemon.conf(5), pulseaudio(1)

Manuals 							       User						      pulse-client.conf(5)