Sponsored Content
Top Forums Shell Programming and Scripting High availability of a process between two Linux servers Post 302978733 by Mahesh_RPM on Wednesday 3rd of August 2016 06:19:56 AM
Old 08-03-2016
High availability of a process between two Linux servers

Hello,

I would like to create a script that will maintain HA/failover of a process between two servers.

I wanted to send a continuous heartbeat message through a script to another server when everything is working fine, if a process has gone down then the same message should be sent another server then the slave server should bring up the process.

I have got no clue how to achieve this, please advice!

Thanks.
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

High availability/Load balancing

Hi folks, (Sorry I don't know what its technology is termed exactly. High Availability OR load balancing) What I'm going to explore is as follows:- For example, on Physical Servers; Server-1 - LAMP, a working server Server-2 - LAMP, for redundancy While Server-1 is working all... (3 Replies)
Discussion started by: satimis
3 Replies

2. UNIX for Dummies Questions & Answers

iscsi high availability

Hi, I want to set up a iscsi high availability with sheepdog distributed storage. Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies

3. AIX

AIX high availability 1-3/69

Hi, Can someone help and give the answer for the following questions: 1. When PowerHA SystemMirror 7.1 is installed on AIX 7.1, what RSCT component does Cluster Aware AIX (CAA) replace? A. Group Services B. Resource Manager C. Topology Services D. Resource Monitoring and Control... (2 Replies)
Discussion started by: walterchang100
2 Replies

4. Solaris

High availability

hi guys I posted problem last time I didn't find answer to my issue. my problem is as below: I have two servers which work as an actif/standby in high availability system. but when i use command HASTAT -a i have the following message: couldn' find actif node. the servers are sun... (1 Reply)
Discussion started by: zineb06
1 Replies

5. Red Hat

Redhat: High Availability

Hi, I want to create gfs storage. But getting error as below: --> Finished Dependency Resolution Error: Package: pacemaker-1.1.12-22.el7_1.2.x86_64 (rhel-ha-for-rhel-7-server-eus-rpms) Requires: sbd You could try using --skip-broken to work around the problem You could try... (1 Reply)
Discussion started by: mzainal
1 Replies

6. UNIX for Advanced & Expert Users

Email Server High Availability

Hello, We are planning to setup a Email server with High Availability for email services so that if SMTP/POP/IMAP goes down on one server, the services switch to second server. We are planning to use a Linux machines from a hosting provider and will do it using DNS with multiple MX records with... (0 Replies)
Discussion started by: sunnysthakur
0 Replies
HEARTBEAT(8)						  System administration utilitie					      HEARTBEAT(8)

NAME
heartbeat - Heartbeat subsystem for High-Availability Linux DESCRIPTION
heartbeat is a basic heartbeat subsystem for Linux-HA. It will run scripts at initialisation, and when machines go up or down. This version will also perform IP address takeover using gratuitous ARPs. It works correctly for a 2-node configuration, and is extensible to larger configurations. It implements the following kinds of heartbeats: o UDP/IP broadcast; o UDP/IP multicast; o UDP/IP unicast; o Bidirectional Serial Rings ("raw" serial ports) -- this type is deprecated and should no longer be used; o special "ping" heartbeats for routers, etc. -- this type has been superseded by functionality in pacemaker() and should no longer be used. Comprehensive documentation on heartbeat is available in the Heartbeat User's Guide. If this documentation is not installed on your system, it can be found at http://linux-ha.org/. OPTIONS
The following options are supported by heartbeat: -d Increment debugging level. Higher levels are more verbose. -r Reload heartbeat. This option is functionally identical to sending a running heartbeat process a HUP signal. If the configuration has not changed, then this option is essentially a no-op. If ha.cf(5) or authkeys(5) has changed, then heartbeat will re-read these files and update its configuration. This option may not be used together with -R. -k Kill (stop) heartbeat. -s Report heartbeat status. -R Heartbeat restart exec flag (internal use only). May not be used with -r. -C Heartbeat current resource state for restart (internal use only). Only valid with -R. -V Print out heartbeat version. Note that most of these options are used for supporting the heartbeat init script, which provides the conventional start, stop, status and restart options (among others). It is recommended to use this rather than invoking the heartbeat command directly. SEE ALSO
ha.cf(5), authkeys(5) AUTHORS
Alan Robertson <alanr@unix.sh> heartbeat Juan Pedro Paredes Caballero <juampe@retemail.es> man page Simon Horman <horms@verge.net.au> man page Florian Haas <florian.haas@linbit.com> man page Heartbeat 3.0.5 24 Nov 2009 HEARTBEAT(8)
All times are GMT -4. The time now is 03:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy