09-20-2007
SAM running slow
Any ideas on why SAM would take so long to load and initialize?
8 More Discussions You Might Find Interesting
1. Solaris
Hi all,
Solaris is working very slow as login to solaris takes time say after 10 to 15 mins we get the login prompt back after logging in as oracle account/other account.
This causes most Batch run delays(DWHouse jobs) scheduled through cronjobs.
Where should one look for such issues to... (3 Replies)
Discussion started by: a1_win
3 Replies
2. SCO
Hi,
Wonder is someone can help.
I've got a server SCO_SV 3.2v5.0.7 PentIII that is located at a different site and is running slow and has been for a week. I've been speaking to a third party who say nothing is wrong with it but its still running slow.
The 3rd party advise it could be a... (2 Replies)
Discussion started by: tez
2 Replies
3. UNIX for Dummies Questions & Answers
All, This is my interview questions. Let me explain the question. Some one is asking me that, the unix server is running very slow. As a unix unix admin, what are the steps we should follow?? What/which process we should check?? What is the way to find the root cause ? Please let me know.... (8 Replies)
Discussion started by: govindts
8 Replies
4. Red Hat
Hi All,
I'm new here.
i was wondering if anyone could shed a light on the problem i am having.
I use a system for distributing broadband amongst users of for example a hotel, the system was designed by someone in the US and it is based on redhat 2.4 (i know its old) and the system uses... (3 Replies)
Discussion started by: clive306
3 Replies
5. Solaris
I am facing a performance problem on a Solaris 10 Sparc V890 server, it is an old one I know. The first time we realized there is a problem with the server, is the time when ftp transfers are made. There were 4 other identical servers doing much better. Network drivers are checked and there... (3 Replies)
Discussion started by: royalliege
3 Replies
6. UNIX for Dummies Questions & Answers
Hello,
My PC seems running slow: OS32 system, Pentium(R)4---2.40Ghz, 1GB RAM, 80GB HDI am running Ubuntu 11.10 (Oneiric Ocelot) alone in this box, which seems very slow to me. Is this normal?
Compared with my other PC (Running XP) with 1.99GHz AMD Athlon 3200+, 2GB RAM,500GB HD, XP and Mint... (11 Replies)
Discussion started by: yifangt
11 Replies
7. Shell Programming and Scripting
Slow runnin script. The problem seems to be the sed calls.
In summary the script reads list of users in file1. For each
username search two files (file 1 & file2) for the username
and get the value in the next line after "=". Compare these
values with each other.
If the same then output... (9 Replies)
Discussion started by: u20sr
9 Replies
8. AIX
Hello,
All the commands on AIX are running very slow.
Below is few stats but I didn't find any issue in cpu or memory reosurces
vmstat
System configuration: lcpu=4 mem=6144MB ent=1.00
kthr memory page faults cpu
----- -----------... (2 Replies)
Discussion started by: Vishal_dba
2 Replies
LEARN ABOUT CENTOS
sam_start
SAM_START(3) Corosync Cluster Engine Programmer's Manual SAM_START(3)
NAME
sam_start - Start health checking
SYNOPSIS
#include <corosync/sam.h>
cs_error_t sam_start (void);
DESCRIPTION
The sam_start function is used to start health checking of application. After calling this function, the active process needs to send
healthchecks within the registered time interval by calling sam_hc_send(3). If event driven healthchecking is configured by calling
sam_register(3), an internal thread will be created and send health check confirmations four times per time_interval.
Application must be registered by calling sam_register(3) before this function can be called.
An application can always stop health checking by calling the sam_stop(3) function.
If SAM is initialized with quorum policy SAM_RECOVERY_POLICY_QUIT or SAM_RECOVERY_POLICY_RESTART sam_start will block until corosync
becomes quorate.
RETURN VALUE
This call return CS_OK value if successful, otherwise and error is returned. If SAM is initialized with quorum policy, returned error can
also be quorum error.
ERRORS
CS_ERR_BAD_HANDLE
component was not registered by calling sam_register(3) function.
SEE ALSO
sam_hc_send(3), sam_stop(3), sam_register(3), sam_hc_callback_register(3)
CS_ERR_TRY_AGAIN Resource temporarily unavailable
CS_ERR_INVALID_PARAM Invalid argument
CS_ERR_ACCESS Permission denied
CS_ERR_LIBRARY The connection failed
CS_ERR_INTERRUPT System call inturrupted by a signal
CS_ERR_NOT_SUPPORTED The requested protocol/functuality not supported
CS_ERR_MESSAGE_ERROR Incorrect auth message received
CS_ERR_NO_MEMORY Not enough memory to completed the requested task
corosync Man Page 30/04/2010 SAM_START(3)