7 More Discussions You Might Find Interesting
1. Programming
Hi,
I just install a library package in R.
However my friend (other users) don't have the right to use it :(
They have the right to issue "R" at their terminal.
However they can't execute and use whatever library package that I installed.
We all share the same server.
Is there any advice... (4 Replies)
Discussion started by: perl_beginner
4 Replies
2. Red Hat
Hello
I have Storage foundation 6.0 version to install in redhat 6.0, so while trying to install one of the application it say to install some dependencies packages so when i try to install the dependencies again it ask for the dependencies so its a lengthy process i say. so now can i get the... (1 Reply)
Discussion started by: cyrus.ranjith
1 Replies
3. Emergency UNIX and Linux Support
Hello,
i have installed a package by using the command
sudo rpm -i filepackage.rpm
package filepackage is already installed
when i try to remove it, i get an error saying "is not installed":
sudo rpm -e filepackage.rpm
error: package filepackage is not installed
How can... (4 Replies)
Discussion started by: g_p
4 Replies
4. UNIX for Dummies Questions & Answers
Hello,
i have downloaded an rpm package "hadoop-0.20.205.0-1.amd64.rpm"
in /usr/local/ directory.
I'm trying to install the rpm package in a new path/location (/usr/local/hadoop-0.20.205), but i can't.
I did:
1st try: Didn't work
sudo rpm -i --prefix=/usr/local/hadoop-0.20.205... (1 Reply)
Discussion started by: g_p
1 Replies
5. UNIX for Advanced & Expert Users
Friends,
Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ?
For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies
6. High Performance Computing
So I have been struggling for the past few days to install a simulation package lammps (http://lammps.sandia.gov/) on my Mac OS X. I am well aware that this is a Ubuntu forum, but you guys seem to know a lot of UNIX stuff, so I was hoping someone might have a solution to my problem...
To run... (1 Reply)
Discussion started by: oscar78
1 Replies
7. UNIX for Dummies Questions & Answers
What is the difference between device driver and board support package? (0 Replies)
Discussion started by: anupa
0 Replies
LEARN ABOUT CENTOS
sam_overview
SAM_OVERVIEW(8) Corosync Cluster Engine Programmer's Manual SAM_OVERVIEW(8)
NAME
sam_overview - Overview of the Simple Availability Manager
OVERVIEW
The SAM library provide a tool to check the health of an application. The main purpose of SAM is to restart a local process when it fails
to respond to a healthcheck request in a configured time interval.
During sam_initialize(3), a duplicate copy of the process is created using the fork(3) system call. This duplicate process copy contains
the logic for executing the SAM server. The SAM server is responsible for requesting healthchecks from the active process, and controlling
the lifecycle of the active process when it fails. If the active process fails to respond to the healthcheck request sent by the SAM
server, it will be sent a user configurable signal (default SIGTERM) to request shutdown of the application. After a configured time
interval, the process will be forcibly killed by being sent a SIGKILL signal. Once the active process terminates, the SAM server will cre-
ate a new active process.
The Simple Availability Manager is meant to be used in conjunction with the cpg service. Used together, it is possible to restart a cpg
process that fails healthchecking during operation.
The main features of SAM include:
o A configurable recovery policy.
o A configurable time interval for health check operations.
o A notification via signal before recovery action is taken.
o A mechanism to indicate to the application the number of times an active process has been created by the SAM server.
o Both application driven health checking and event driven health checking.
Initializing SAM
The SAM library is initialized by sam_initialize(3). sam_initalize(3) may only be called once per process. Calling it more then once has
undefined results and is not recommended or tested.
Setting warning callback
User configurable signal (default SIGTERM) is sent to the application when a recovery action is planned. The application can use the sig-
nal(3) system call to monitor for this signal.
There are no special constraints on what SAM apis may be called in a warning callback. After time_interval expires, a SIGKILL signal is
sent to the active process to force its termination.
Registering the active process
The active process is registered with SAM by calling sam_register(3). This function should only be called one time in a process. After a
recovery action is taken, the new active process will begin execution at the next line of code in a user process after sam_register(3).
Enabling event driven healthchecking
Two types of healthchecking are available to the user. The first model is one where the user application healthchecks during its normal
operation. It is never requested to healtcheck, and if the active process doesn't respond within the time interval, the process will be
restarted.
A more useful mechanism for healthchecking is event driven healthchecking. Because this model is directed by the SAM server, It isn't nec-
essary to guess or add timers to the active process to signal a healthcheck operation is successful. To use event driven healthchecking,
the sam_hc_callback_register(3) function should be executed.
Quorum integration
SAM has special policies (SAM_RECOVERY_POLICY_QUIT and SAM_RECOVERY_POLICY_RESTART) for integration with quorum service. This policies
changes SAM behaviour in two aspects.
o Call of sam_start(3) blocks until corosync becomes quorate
o User selected recovery action is taken immediately after lost of quorum.
Storing user data
Sometimes there is need to store some data, which survives between instances. One can in such case use files, databases, ... or much sim-
pler in memory solution presented by sam_data_store(3), sam_data_restore(3) and sam_data_getsize(3) functions.
Confdb integration
SAM has policy flag used for confdb system integration (SAM_RECOVERY_POLICY_CONFDB). If process is registered with this flag, new confdb
object PROCESS_NAME:PID is created with following keys:
o recovery - will be quit or restart depending on policy
o poll_period - period of health checking in milliseconds
o last_updated - Timestamp (in nanoseconds) of the last health check.
o state - state of process (can be one of registered, started, failed, waiting for quorum)
Object is automatically deleted if process exits with stopped health checking.
Confdb integration with corosync wathdog can be used in implicit and explicit way.
Implicit way is achieved by setting recovery policy to QUIT and let process exit with started health checking. If this happened, object is
not deleted and corosync watchdog will take required action.
Explicit way is usefull for situations, when developer can deal with some non-fatal fall of application. This mode is achieved by setting
policy to RESTART and using SAM same as without Confdb integration. If real fail is needed (like too many restarts at all, per/sec, ...),
it's possible to use sam_mark_failed(3) and let corosync watchdog take required action.
BUGS
SEE ALSO
sam_initialize(3), sam_data_getsize(3), sam_data_restore(3), sam_data_store(3), sam_finalize(3), sam_mark_failed(3), sam_start(3),
sam_stop(3), sam_register(3), sam_warn_signal_set(3), sam_hc_send(3), sam_hc_callback_register(3)
corosync Man Page 21/05/2010 SAM_OVERVIEW(8)
