- 论坛徽章:
- 0
|
InfoPartner Document 1-1-4220253-1 Document Audience: SPECTRUM
Document ID: 4220253
Title: pnmrtop failed with exit code 5
Update Date: Fri Apr 30 17:44:00 MDT 1999
--------------------------------------------------------------------------------
Bug ID: 4220253
Synopsis: pnmrtop failed with exit code 5
Category: library
Subcategory: libthread
State: integrated
Priority:
Responsible Manager:
Responsible Engineer:
Description:
Our customer has two nodes cluster running SC2.1 under Solaris
2.6/UE45000 and have a problem that is netfmd got errors with
following error messages.
Feb 27 03:06:08 CHAOZ netfmd[7881]: Public network is unhealthy for logical
host CHUN on this
node. Invoking: /opt/SUNWcluster/bin/hactl -g -s mail -l CHUN -L soft
Feb 27 03:09:09 CHAOZ ID[SUNWcluster.ha.hads.3019]: pnmrtop failed - exit code
is 5 - Refer to
pnmrtop(1m) man page for details.
Feb 27 03:09:09 CHAOZ ID[SUNWcluster.ha.hactl.3041]: error during network
checks on CHAOZ
Feb 27 03:09:09 CHAOZ ID[SUNWcluster.ha.hactl.3042]: This host is not alone in
the
cluster, but no other physical host was found capable of mastering CHUN
Feb 27 04:04:55 CHAOZ netfmd[7881]: Public network is unhealthy for logical
host CHUN on this
node. Invoking: /opt/SUNWcluster/bin/hactl -g -s mail -l CHUN -L soft
Feb 27 04:07:56 CHAOZ ID[SUNWcluster.ha.hads.3019]: pnmrtop failed - exit code
is 5 - Refer to
pnmrtop(1m) man page for details.
Feb 27 04:07:56 CHAOZ ID[SUNWcluster.ha.hactl.3041]: error during network
checks on CHAOZ
Feb 27 04:07:56 CHAOZ ID[SUNWcluster.ha.hactl.3042]: This host is not alone in
the
cluster, but no other physical host was found capable of mastering CHUN
We tried to run pnmrtop command manualy when failure happened and got
following rpc error.
HAOZ# pnmstat -l
bkggrp r_adp status fo_time live_adp
nafo_status: clnt_create(localhost) failed: : RPC: Miscellaneous tli error - An
event requires attention
PNM rpc svc failed
nafo0 hme0:qfe0 CHAOZ#
CHAOZ#
This failure happened every days and if failure happened, they cannot
control the cluster system any more.
We tried to restart "netfmd" process when failure happened but could
not recover the problem however restart both "pnmd" and "netfmd"
processes we could recover the problem so it looks like root cause is
in the "pnmd" process.
The explore data located at ftp://hibiscus.japan/tmp/5163515.tar
Work Around:
restart "pnmd" process.
Integrated in releases: s28_22,
Duplicate of:
Patch ID: ,
See Also: 4226377, 4286188, 4303473, 4361737,
Summary:
The attachment 5163515_pnmd_info.tar.Z has core files of "pnmd" process, pnmd
binary, pstack outputs, message file, pnmd.log file (taken with pnmd -d option).
--------------------------------------------------------------------------------
This collection hosted on The Sun Partner Exchange Portal
Copyright (c) 1997 - 2006 Sun Microsystems, Inc |
|