app multiple times at once.
On 19 Mar 2021, at 13:32, Sendu Bala
mailto:s...@sanger.ac.uk>> wrote:
Hi,
Thanks for the explanation. I’m trying to restrict the port range, because if I
don’t, mpiexec doesn’t function reliably.
With 2 hosts it always works, then as you add hosts it is mo
he problem here is
that one or more of those ranks was unable to get a port in the range you
specified because they were all apparently occupied.
If you don't have firewalls, then why are you trying to restrict the port range?
On Mar 19, 2021, at 5:47 AM, Sendu Bala
mailto:s...@sanger.
..then you have something else going on. By default, OMPI will ask the
local OS for an available port and use it. You only need to specify ports when
working thru a firewall.
Do you have firewalls on this cluster?
On Mar 18, 2021, at 8:55 AM, Sendu Bala
mailto:s...@sanger.ac.uk>> wrote:
ave to experiment a bit as there is nothing to guarantee
that other processes aren't occupying those regions.
On Mar 18, 2021, at 2:13 AM, Sendu Bala
mailto:s...@sanger.ac.uk>> wrote:
Thanks, it made it work when I was running “true” as a test, but then my real
MPI app failed with:
[node-5
.open-mpi.org>> wrote:
On 09/03/2021 11:23, Sendu Bala via users wrote:
When using mpirun, how do you pick which ports are used?
I???ve tried:
mpirun --mca btl_tcp_port_min_v4 46207 --mca btl_tcp_port_range_v4 32 --mca
oob_tcp_keepalive_time 45 --mca oob_tcp_max_recon_attempts 20 --m
When using mpirun, how do you pick which ports are used?
I’ve tried:
mpirun --mca btl_tcp_port_min_v4 46207 --mca btl_tcp_port_range_v4 32 --mca
oob_tcp_keepalive_time 45 --mca oob_tcp_max_recon_attempts 20 --mca
oob_tcp_retry_delay 1 --mca oob_tcp_keepalive_probes 20 --mca
oob_tcp_keepalive
Hi,
Following requested info in https://www.open-mpi.org/community/help/ :
Version: v4.1
config.log: n/a
ompi_info —all: https://pastebin.com/69QKAbi5
$ bsub -q normal -o bsub.o -e bsub.e -R"span[ptile=1]" -n16 mpirun --bynode
--hostfile my_hostfile.txt --tag-output ompi_info -v ompi full --par
locked memory: cannot modify
limit: Operation not permitted
we are setting the ulimit in "/etc/init.d/sshd" file,
but not sure why we are getting this ulimit error
only in interactive jobs.
How do you set ulimit?? and how much??
pls advice.
thanks,
-bala-
--- Götz Waschk wrote:
&g
running in SGE
using this PE??
from my mpich PE I can see start/stop arguments as
show below
start_proc_args /opt/gridengine/mpi/startmpi.sh
-catch_rsh
$pe_hostfile
stop_proc_args/opt/gridengine/mpi/stopmpi.sh
tha
Thanks Tim, for the info and suggestion.
Bala.
--- Tim Prins wrote:
> Bala,
>
> This is a known problem with the 1.1 series. The bad
> news is that I
> know of no fix for this, though many people work
> around this problem
> by running a cleanup script after each un
Hi, due to no reply posting again, pls let
me know, any solution or work around available
for the below issue, or are we doing anything
wrong??
-bala-
> Hi All,
>we have installed 16 node Intel X86_64
> dual CPU and dual core cluster( blade servers)
> with OFED-1.1, t
;t know
which process is idle to kill.
regards,
Bala.
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265
12 matches
Mail list logo
