Hmmm...well, a few thoughts to hopefully help with the debugging. One
initial comment, though - 1.1.2 is quite old. You might want to upgrade to
1.2 (releasing momentarily - you can use the last release candidate in the
interim as it is identical).
Meantime, looking at this output, there appear to
I'm using OpenMPI version 1.1.2. I installed it using gentoo portage,
so I think it has the right permissions... I tried doing 'equery f
openmpi | xargs ls -dl' and inspecting the permissions of each file,
and I don't see much out of the ordinary; it is all owned by
root:root, but every file has r
It isn't a /dev issue. The problem is likely that the system lacks
sufficient permissions to either:
1. create the Open MPI session directory tree. We create a hierarchy of
subdirectories for temporary storage used for things like your shared memory
file - the location of the head of that tree can
On Mar 15, 2007, at 12:18 PM, Michael wrote:
I'm having trouble with the portability of executables compiled with
OpenMPI. I suspect the sysadms on the HPC system I'm using changed
something because I think it worked previously.
Apparently there was a misconfiguration, i.e. missing libraries
Ok, now that I've figured out what the signal means, I'm wondering
exactly what is running into permission problems... the program I'm
running doesn't use any functions except printf, sprintf, and MPI_*...
I was thinking that possibly changes to permissions on certain /dev
entries in newer distros
sebastien.he...@external.thalesgroup.com wrote:
Hi,
Is there any mean to reduce the shared RAM used by MPI?
For a very simple application, I have about 500Mo of shared RAM.
Try
mpirun --mca mpool_sm_size -np ./a.out
^^
--
Ed[mund] [Sumbar]]
Research Suppor
Hi,
If the perror command is available on your system it will tell
you what the message is associated with the signal value. On my system
RHEL4U3, it is permission denied.
HTH,
mac mccalla
-Original Message-
From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] O
I've been having similar issues with brand new FC5/6 and RHEL5 machines,
but our FC4/RHEL4 machines are just fine. On the FC5/6 RHEL5 machines,
I can get things to run as root. There must be some ACL or security
setting issue that's enabled by default on the newer distros. If I
figure it out
I've been trying to get OpenMPI working on two of the computers at a
lab I help administer, and I'm running into a rather large issue. When
running anything using mpirun as a normal user, I get the following
output:
$ mpirun --no-daemonize --host
localhost,localhost,localhost,localhost,localhost
Hi,
Is there any mean to reduce the shared RAM used by MPI?
For a very simple application, I have about 500Mo of shared RAM.
Thanks,
Sébastien.
I'm having trouble with the portability of executables compiled with
OpenMPI. I suspect the sysadms on the HPC system I'm using changed
something because I think it worked previously.
Situation: I'm compiling my code locally on a machine with just
ethernet interfaces and OpenMPI 1.1.2 that
I don¹t immediately see anything in your configuration that would cause the
problem you describe. We haven¹t seen any problems running non-mpi apps as
I mentioned in another posting, we do it regularly, both threaded and
non-threaded. My best guess is that there is something preventing openmpi
fr
I can't speak to the MPI problems mentioned in here as my area of focus is
solely on the RTE. With that caveat, I can say that - despite the fact there
is little thread safety testing in the system - I haven't heard of any
trouble launching non-MPI apps. We do it regularly, in both threaded and
non
Apologies if you received multiple copies of this posting.
Please feel free to distribute it to those who might be interested.
Hot In
14 matches
Mail list logo
