8 More Discussions You Might Find Interesting
1. HP-UX
I've just been on an HP Training Course for HPUXv11.31 and found out about the gui / web for SMH. I never did a course on HP11v23. On our two servers here in the UK that run 11.23 I'm pretty sure that when I typed in "sam" on the command line it went to a sort of smh. (There was a message saying... (2 Replies)
Discussion started by: markp1965
2 Replies
2. HP-UX
Hello everybody,
i need to check which users have resticted sam access..can anybody please let me know how to check this..?
Thanks in advance.. (4 Replies)
Discussion started by: laxmikant
4 Replies
3. HP-UX
Hi there,
I am building an HP UX 11 server (first time) and I'm trying to mount the CDROM with SAM. What am I supposed to enter in the "mount directory" box?
Also, I can't ftp to the server due to a logon failure. I used root id and password. I deleted the file in the /etc/ftpd directory but... (8 Replies)
Discussion started by: rbglo
8 Replies
4. HP-UX
Any ideas on why SAM would take so long to load and initialize? (4 Replies)
Discussion started by: csaunders
4 Replies
5. UNIX for Dummies Questions & Answers
I'm in the process of setting up two new HP-UX 11.23 i64 servers.
On my existing server (HP-UX B.11.0) we have several users defined to have restricted sam access.
I'm having trouble finding those definitions and copying them over to the new servers. Is this possible - to just copy over the... (1 Reply)
Discussion started by: LisaS
1 Replies
6. UNIX for Dummies Questions & Answers
On running ‘Disk Devices’ tools under ‘Disks and File Systems’ option of System Administration Manager (SAM) in our UNIX Server (HP 9000 running HPUX B.11.11 U) a warning message appeared. The message that appeared reads as follows
“The Logical Volume Manager shows this device file,... (3 Replies)
Discussion started by: mhbd
3 Replies
7. HP-UX
hi, any idea how to get more info on the usage, unix equivalent of sam in hp-ux? thanks (7 Replies)
Discussion started by: yls177
7 Replies
8. UNIX for Advanced & Expert Users
I am having a problem on an HP box, where I am being told that there are too many open files. I am also being told I need to change a SAM file. Could some help me understand what a SAM files is and what it is used for.
Thanks. (2 Replies)
Discussion started by: kristian
2 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)