- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Monitor cmviewcl
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
08-09-2010 01:10 PM
08-09-2010 01:10 PM
Monitor cmviewcl
But in certain situation, the cluster command stopped responding.
commands are left hanging without showing output.
as I can monitor with a cron these commands?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2010 02:41 AM
08-10-2010 02:41 AM
Re: Monitor cmviewcl
Your question is not clear. BTW, you can check the below link: http://www.unix.com/man-page/all/1m/cmviewcl/
Rgds-Kranti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2010 03:04 AM
08-10-2010 03:04 AM
Re: Monitor cmviewcl
Please, put you HPUX and SGuard version.
Verify the latest patch for SGuard.
Verify network connections timeout.
Rgs,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2010 03:32 AM
08-10-2010 03:32 AM
Re: Monitor cmviewcl
This delay does not happen if a node leaves the cluster in a controlled fashion (using the "cmhaltnode" command).
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2010 03:55 AM
08-10-2010 03:55 AM
Re: Monitor cmviewcl
You should check syslog.log and cluster pkg log to know the root cause of problem occurance.however, you can check /etc/inetd.conf file to see hacl lines for udp/tcp is available or not?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2010 06:07 AM
08-10-2010 06:07 AM
Re: Monitor cmviewcl
I'am not shore what you need.
If the cmviewcl "block" you must have some problem with your configuration/SG.
Check the syslog and cluster logs and see you can find anything.
Best regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2010 07:22 AM
08-10-2010 07:22 AM
Re: Monitor cmviewcl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2010 03:51 PM
08-10-2010 03:51 PM
Re: Monitor cmviewcl
>I want to create a script to check every now commands the cluster if they are responding adequately .... and to report only when the cluster commands do not work.
For what is it good? You should rather check your services, which are the critical part in the business. I think you want to check if the packages are running, but there are many other ways to check this, like a remote ssh to the package IP, and checking with ps if the application behind it runs, and so on...
Unix operates with beer.