Rocks cluster 6.1 and MPICH2 problem?????? Post: 302826269

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...

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...

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...

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...

LEARN ABOUT DEBIAN

4s-backend-setup

4S-BACKEND_SETUP(1J)						      4store						      4S-BACKEND_SETUP(1J)

NAME

     4s-backend-setup -- Create a new 4store KB

SYNOPSIS

     4s-backend-setup kbname [--node node-number] [--cluster cluster-size] [--segments segment-count] kb-name

		      --node  Number of this node in the cluster, values range from 0 to cluster-size - 1.  The default is 0.

		      --cluster
			      The number of nodes in the cluster.  The default is 1.

		      --segments
			      The number of segments in the cluster. The default is 2. We recommend one for each CPU core in the cluster as a good
			      starting point. Higher numbers tend to consume more resources, but may result in increased performance.

NOTES

     Once crated with 4s-backend-setup KBs should be started with 4s-backend(1)

SEE ALSO

     4s-query(1), 4s-size(1), 4s-httpd(1), 4s-backend(1), 4s-delete-model(1)

EXAMPLES

     $ 4s-backend-setup --node 0 --cluster 1 --segments 4 demo

     Creates the indexes for a single-machine KB with four segments, named "demo".

4store								   May 31, 2019 							    4store