Sponsored Content
Operating Systems HP-UX HP-UX 11.11 SAM no longer displaying configurable parameters Post 29686 by saabir on Thursday 10th of October 2002 09:09:22 AM
Old 10-10-2002
SAM executes a number of commands on the kernel (/stand/vmunix) to produce the output for the "Configurable Parameters" window. One of these steps may be failing on your server.

The best way to see what SAM is doing is to execute /usr/sam/bin/samlog_viewer -l C /var/sam/log/samlog. This will open a window which extracts the commands executed by SAM. Scroll to the bottom to see what it was doing when it attempted to list the "configurable Parameters" and hopefully it will give you clue as to where it is failing.

SAM does run a number of executables such as kmadmin, kmsystem, kmtune and get_sysfile - some of these on temporary files it creates. One of these may be failing, or it may be failing to generate a temporary file.
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SAM file

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

2. HP-UX

help on sam

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

3. UNIX for Advanced & Expert Users

HP-UX Restricted SAM

I am having trouble getting restricted SAM to work by allocating Privileges to a "group". I can make it work by allocaing to the userid's, but would preferre to use the "group" option. Running B.11.11 Tried the following.... 1) Created a user group in /etc/group first 2) Used the... (1 Reply)
Discussion started by: Andrek
1 Replies

4. AIX

tuning network parameters : parameters not persist after reboot

Hello, On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command. tunrestore -R is present in inittab in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log ... (0 Replies)
Discussion started by: dantares
0 Replies

5. UNIX for Dummies Questions & Answers

Trouble displaying parameters passed into a for loop

#!/bin/bash function check_num_args() { if ; then echo "Please provide a file name" else treat_as_file $* fi } function treat_as_file() { numFiles=$# for((i=1;i<=$numFiles;i++));do echo $i ... (3 Replies)
Discussion started by: kikilahooch
3 Replies

6. Programming

C++ problem displaying parameters using dOxygen

I have written some C++ code with documentation code for dOxygen as below. However the parameters are not showing up. /// \file /// /// #ifndef __VECT2_HH__ #define __VECT2_HH__ #include <iostream> #include <assert.h> #include <cmath> #include "common.hh" ... (0 Replies)
Discussion started by: kristinu
0 Replies

7. HP-UX

HPUX 11.23 - Sam and Smh.

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
SAM_INITIALIZE(3)				    Corosync Cluster Engine Programmer's Manual 				 SAM_INITIALIZE(3)

NAME
sam_initialize - Initialize health checking SYNOPSIS
#include <corosync/sam.h> cs_error_t sam_initialize (int time_interval, sam_recovery_policy_t recovery_policy); DESCRIPTION
The sam_initialize function is used to initialize health checking of a process. Application can have only one instance of SAM. This function must be called before any other of SAM functions. It is recommended to ini- tialize before the process begins any process initialization. The time_interval parameter is a timeout in milliseconds before taking recovery action after having not received a healthcheck. If time_interval parameter is zero, there is no time limit and no healthcheck must be sent by the process. In this operational mode, a process failure will continue to execute the recovery policy. The recovery_policy is defined as type: typedef enum { SAM_RECOVERY_POLICY_QUIT = 1, SAM_RECOVERY_POLICY_RESTART = 2, SAM_RECOVERY_POLICY_QUORUM = 0x08, SAM_RECOVERY_POLICY_QUORUM_QUIT = SAM_RECOVERY_POLICY_QUORUM | SAM_RECOVERY_POLICY_QUIT, SAM_RECOVERY_POLICY_QUORUM_RESTART = SAM_RECOVERY_POLICY_QUORUM | SAM_RECOVERY_POLICY_RESTART, SAM_RECOVERY_POLICY_CMAP = 0x10, SAM_RECOVERY_POLICY_CONFDB = 0x10, } sam_recovery_policy_t; where SAM_RECOVERY_POLICY_QUIT on failure, the process will terminate. SAM_RECOVERY_POLICY_RESTART on failure, the process will restart. SAM_RECOVERY_POLICY_QUORUM is not policy. Used only as flag meaning quorum integration SAM_RECOVERY_POLICY_QUORUM_QUIT same as SAM_RECOVERY_POLICY_QUIT but sam_start (3) will block until corosync becomes quorate and process will be terminated if quo- rum is lost. SAM_RECOVERY_POLICY_QUORUM_RESTART same as SAM_RECOVERY_POLICY_RESTART but sam_start (3) will block until corosync becomes quorate and process will be restarted if quorum is lost. SAM_RECOVERY_POLICY_CMAP is not policy. Used only as flag meaning cmap integration. It can be used with all previous policies. For backward compatibility, SAM_RECOVERY_POLICY_CONFDB with same meaning as SAM_RECOVERY_POLICY_CMAP is also provided. To perform event driven healthchecking, sam_register(3) and sam_start(3) functions must called. Event driven healthchecking causes the duplicate standby process running the SAM serve rto periodically request healthchecks from the active process. RETURN VALUE
This call return CS_OK value if successful, otherwise and error is returned. ERRORS
CS_ERR_BAD_HANDLE can happened in case of double initialization. CS_ERR_INVALID_PARAM recovery_policy has invalid value. SEE ALSO
sam_register(3), sam_start(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 21/05/2010 SAM_INITIALIZE(3)
All times are GMT -4. The time now is 10:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy