Sponsored Content
Operating Systems Linux Rocks cluster 6.1 and MPICH2 problem?????? Post 302826269 by saeedbabaei on Wednesday 26th of June 2013 08:52:43 AM
Old 06-26-2013
hi,
any one wants answer this question?
i have this question too! Smilie
 

4 More Discussions You Might Find Interesting

1. Linux

Intermittent connectivity issues with ROCKS on a compute cluster

I have a cluster set up with a head node and compute nodes running TORQUE and MOAB. The distro is ROCKS 5.3. I've been having problems with the connectivity for the past couple weeks now. Every couple hours it seems like the network connectivity will just stop working: sometimes it'll start back up... (0 Replies)
Discussion started by: gandalf85
0 Replies

2. UNIX for Dummies Questions & Answers

MPICH2 version/Error

Guys, I have two questions: 1- What command do i have to use to know the version of MPICH2? 2- I am running a parallel computation on quantum espresso using a SLURM interface (INTEL) and I am getting the following error: however a colleague gave me another (rather more complicated) script... (1 Reply)
Discussion started by: lebphys78
1 Replies

3. Red Hat

Cluster Problem

Hi, I am facing issuing in setting up Linux cluster. Here is the issue that i am facing. I have 2 Linux desktop and have following ip's and name: hitesh12-192.168.1.23 saanvi12-192.168.1.30 i enabled ricci service and have setup passwod as well.Enabled luci service as well. When... (0 Replies)
Discussion started by: hitesh1907
0 Replies

4. UNIX for Advanced & Expert Users

CentOS 6.8 with Rocks Cluster: ldconfig is not a symbolic link errors

Any help appreciated just logging in to this server which is a front end for Rocks Cluster 6.1.1. Getting the below errors: ldconfig ldconfig: /usr/lib/libX11.so.6 is not a symbolic link ldconfig: /usr/lib/libjpeg.so.62 is not a symbolic link ldconfig: /usr/lib/libpng12.so.0 is not a symbolic... (3 Replies)
Discussion started by: RobbieTheK
3 Replies
CRM_MON(8)							  [FIXME: manual]							CRM_MON(8)

NAME
crm_mon - monitor the cluster's status SYNOPSIS
crm_mon [-V] -d -pfilename -h filename crm_mon [-V] [-1|-n|-r] -h filename crm_mon [-V] [-n|-r] -X filename crm_mon [-V] [-n|-r] -c|-1 crm_mon [-V] -i interval crm_mon -? DESCRIPTION
The crm_mon command allows you to monitor your cluster's status and configuration. Its output includes the number of nodes, uname, uuid, status, the resources configured in your cluster, and the current status of each. The output of crm_mon can be displayed at the console or printed into an HTML file. When provided with a cluster configuration file without the status section, crm_mon creates an overview of nodes and resources as specified in the file. OPTIONS
--help, -? Provide help. --verbose, -V Increase the debug output. --interval seconds, -i seconds Determine the update frequency. If -i is not specified, the default of 15 seconds is assumed. --group-by-node, -n Group resources by node. --inactive, -r Display inactive resources. --as-console, -c Display the cluster status on the console. --one-shot, -1 Display the cluster status once on the console then exit (does not use ncurses). --as-html filename, -h filename Write the cluster's status to the specified file. --daemonize, -d Run in the background as a daemon. --pid-file filename, -p filename Specify the daemon's pid file. --xml-file filename, -X filename Specify an XML file containing a cluster configuration and create an overview of the cluster's configuration. EXAMPLES
Display your cluster's status and get an updated listing every 15 seconds: crm_mon Display your cluster's status and get an updated listing after an interval specified by -i. If -i is not given, the default refresh interval of 15 seconds is assumed: crm_mon -i interval[s] Display your cluster's status on the console: crm_mon -c Display your cluster's status on the console just once then exit: crm_mon -1 Display your cluster's status and group resources by node: crm_mon -n Display your cluster's status, group resources by node, and include inactive resources in the list: crm_mon -n -r Write your cluster's status to an HTML file: crm_mon -h filename Run crm_mon as a daemon in the background, specify the daemon's pid file for easier control of the daemon process, and create HTML output. This option allows you to constantly create HTML output that can be easily processed by other monitoring applications: crm_mon -d -p filename -h filename Display the cluster configuration laid out in an existing cluster configuration file (filename), group the resources by node, and include inactive resources. This command can be used for dry-runs of a cluster configuration before rolling it out to a live cluster. crm_mon -r -n -X filename FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged. AUTHOR
crm_mon was written by Andrew Beekhof. [FIXME: source] 07/05/2010 CRM_MON(8)
All times are GMT -4. The time now is 12:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy