- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NODE_TIMEOUT
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2005 11:49 PM
11-28-2005 11:49 PM
NODE_TIMEOUT
I am trying to run check script on two servers in cluster. This message is displayed
./check.txt
********************************
*** Script to check firmware ***
*** PDC etc. ***
** @(#) Type G 22/12/04 ***
********************************
Files will be created in : /tmp/roota16814
Available space : 318904 Kb
Logical volume : /dev/vg00/lvol4
This is a active Serviceguard cluster, checking NODE_TIMEOUT!
A value between 5 and 8 seconds is recommended for CPU intensive Apps.
Checking this using cmgetconf can take up to 10 minutes!
On process hang, check LVM patches, see wtec call 4000030515!
vgscan -p used in cmgetconf can be root cause!
No data from cmgetconf, looking for existing ascii-file(s)
No or too many files XXX.ascii found, cannot continue...
NODE_TIMEOUT variable not displayed during /usr/sbin/cmgetconf!
Possible a Serviceguard error situation!
Run /usr/sbin/cmgetconf which will display the error!
If help is needed, contact the nearest HP response center!
I need disable NODE_TIMEOUT, where is this variable?? Can you help me.. Thanks...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2005 12:00 AM
11-29-2005 12:00 AM
Re: NODE_TIMEOUT
Suggestion:
Check networking in general and see if there is a slowdown of any kind.
Check ping times and see if they are unreasonably high.
Check for SG patches and get them in.
State your version of both the OS, SG and latest quarterly update installed.
Check inetd.conf and make sure the latest changes for 11.16 SG are in if that applies to you.
I don't think changing the NODE_TIMEOUT to 10 minutes is going to do you any good. The underlying issue seems to be your Cluster is not working correctly and the root cause should be dealth with.
find /etc/cmcluster -exec grep -l NODE_TIMEOUT {} \;
# The find command will provide you a list of the configuration files containing the variable.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2005 12:41 AM
11-29-2005 12:41 AM
Re: NODE_TIMEOUT
Yes you can comment it out.
Just command the line out in the checkscript
when it checks for the mc-serviceguard.
vi the script and look for SERVICEGUARD.
If i'm correct you can put a 1 instead of a 0 in the beginning of the newest check file and mc-serviceguard wil not be checked.
grtz. Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2005 02:19 AM
11-29-2005 02:19 AM
Re: NODE_TIMEOUT
if you are running a new version of Serviceguard, you can run the command "cmscancl" which will create /tmp/scancl.out
grep -i timeout /tmp/scancl.out
will reveal the value.
Otherwise, check the /etc/cmcluster directory for your cluster ascii file and type:
grep -i timeout
Oz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2005 04:11 AM
11-30-2005 04:11 AM
Re: NODE_TIMEOUT
Today I will do this. Thanks...