Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- Serviceguard
- >
- Re: Start the Cluster in debug mode
Serviceguard
-
-
Forums
- Products
- Servers and Operating Systems
- Storage
- Software
- Services
- HPE GreenLake
- Company
- Events
- Webinars
- Partner Solutions and Certifications
- Local Language
- China - 简体中文
- Japan - 日本語
- Korea - 한국어
- Taiwan - 繁體中文
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Blog, Poland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Forums
-
Blogs
-
Information
-
English
Topic Options
- 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
- Email to a Friend
- Report Inappropriate Content
09-16-2010 11:50 AM
09-16-2010 11:50 AM
Start the Cluster in debug mode
Hi
Can any one say me how to start the service guard in hp-ux in debug mode.
Can any one say me how to start the service guard in hp-ux in debug mode.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-16-2010 12:04 PM
09-16-2010 12:04 PM
Re: Start the Cluster in debug mode
clarify what you mean by "debug mode"
are you looking to increase logging into syslog.log?
for the cluster as whole?
and why?
are you looking to increase logging into syslog.log?
for the cluster as whole?
and why?
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-16-2010 12:51 PM
09-16-2010 12:51 PM
Re: Start the Cluster in debug mode
If i want to start the cluster in debug mode for check what is the procedure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-16-2010 10:34 PM
09-16-2010 10:34 PM
Re: Start the Cluster in debug mode
Hello,
You did not specify which version of
Serviceguard is used.
The cmsetlog command (obsolete with SG A.11.19)
enables users to obtain a more verbose output
of cmcld. This is extremely useful if a
problem should be reproduced. cmsetlog allows
to set the log level and to restrict logging
to specific categories and modules.
From SG A.11.19 onwards you can start logging
for cmcld by adding the following lines in
the /etc/cmcluster.conf and do a
kill -SIGHUP.
CMCLD_LOG_FILE=/var/adm/cmcluster/cmcld.log
CMCLD_LOG_LEVEL=5
You can also enable debug logging for a
specific module only by setting in the same
file:
CMCLD_{module mnemonic}_LOG_LEVEL=5
where {module mnemonic} is one of the following:
ATN = Auto Trans
CDB = Configuration Database
CLM = Cluster Management
CMD = Commands
CML = SAF Distributed Lock Service
CMP = Config/Status Proxy
CMS = SAF Cluster Membership Service
CNF = Configuration
COM = Communication Server
CSV = Command Server
DFA = Disk File Access
DLK = Disk Lock
DLM = Distributed Lock Management
EVT = Cluster Management Event
GMD = Group Membership Server
GMS = Group Membership Service
LOC = Local Communication
LVM = Logical Volume Management
MDV = Module Version
MSG = Messaging
NET = Network Management
PKG = Package Management
PLE = Placement Engine
QSM = Quorum Service
REM = Remote Communication
RES = EMS Resources
SDB = Status Database
SEC = Security Service
SES = Sessions
SRV = Service Management
STA = Status Database API
SYN = Synchronization
UNK = Unknown
UTD = Utility Daemon
There is also debug logging of SG commands
using the '-D' option (SG A.11.18 and later)
If you want to change the logging for a
single command, you can specify -D {1-5} or
-O {filename) on the command line of any
commands. These command line options will
take precedence over the COMMAND_LOG_LEVEL/COMMAND_LOG_FILE values
specified in /etc/cmcluster.conf.
And so on.
As you can see, there are many ways to do it.
Cheers,
VK2COT
You did not specify which version of
Serviceguard is used.
The cmsetlog command (obsolete with SG A.11.19)
enables users to obtain a more verbose output
of cmcld. This is extremely useful if a
problem should be reproduced. cmsetlog allows
to set the log level and to restrict logging
to specific categories and modules.
From SG A.11.19 onwards you can start logging
for cmcld by adding the following lines in
the /etc/cmcluster.conf and do a
kill -SIGHUP
CMCLD_LOG_FILE=/var/adm/cmcluster/cmcld.log
CMCLD_LOG_LEVEL=5
You can also enable debug logging for a
specific module only by setting in the same
file:
CMCLD_{module mnemonic}_LOG_LEVEL=5
where {module mnemonic} is one of the following:
ATN = Auto Trans
CDB = Configuration Database
CLM = Cluster Management
CMD = Commands
CML = SAF Distributed Lock Service
CMP = Config/Status Proxy
CMS = SAF Cluster Membership Service
CNF = Configuration
COM = Communication Server
CSV = Command Server
DFA = Disk File Access
DLK = Disk Lock
DLM = Distributed Lock Management
EVT = Cluster Management Event
GMD = Group Membership Server
GMS = Group Membership Service
LOC = Local Communication
LVM = Logical Volume Management
MDV = Module Version
MSG = Messaging
NET = Network Management
PKG = Package Management
PLE = Placement Engine
QSM = Quorum Service
REM = Remote Communication
RES = EMS Resources
SDB = Status Database
SEC = Security Service
SES = Sessions
SRV = Service Management
STA = Status Database API
SYN = Synchronization
UNK = Unknown
UTD = Utility Daemon
There is also debug logging of SG commands
using the '-D' option (SG A.11.18 and later)
If you want to change the logging for a
single command, you can specify -D {1-5} or
-O {filename) on the command line of any
commands. These command line options will
take precedence over the COMMAND_LOG_LEVEL/COMMAND_LOG_FILE values
specified in /etc/cmcluster.conf.
And so on.
As you can see, there are many ways to do it.
Cheers,
VK2COT
VK2COT - Dusan Baljevic
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2022 Hewlett Packard Enterprise Development LP