Well, I did some digging around, and this PR looks like the right solution.
First, the security issue is fine so long as we use the highest level of
security that is available. If someone configures the system with munge, then
we default to it - if not, we use the next highest one available.
Se
On 2015/03/26 13:00, Ralph Castain wrote:
> Well, I did some digging around, and this PR looks like the right solution.
ok then :-)
following stuff is not directly related to ompi, but you might want to
comment on that anyway ...
> Second, the running of munge on the IO nodes is not only okay but
Hi guys,
Thanks for the follow-up.
It appears that you are ruling out that Munge is required because the system
runs TORQUE, but as far as I can see Munge is/can be used by both SLURM and
TORQUE.
(http://docs.adaptivecomputing.com/torque/4-0-2/Content/topics/1-installConfig/serverConfig.htm#usi
Hi Ralph,
> On 25 Mar 2015, at 21:59 , Mark Santcroos wrote:
>> Anyway, see if this fixes the problem.
>>
>> https://github.com/open-mpi/ompi/pull/497
Can confirm the fallback works now without setting explicitly to basic (with
the merged changes).
Thanks!
Mark
***
* EuroMPI 2015 Call for Papers *
* The 22nd European MPI Users' Group Meeting *
* Bordeaux, France*
* 21st - 24th September, 2015 *
* https://eurompi2015.bordeaux.inria.fr *
Hi Jason:
The issue is that Open MPI is (presumably) a 64 bit application and it is
trying to load up a 64-bit libcuda.so.1 but not finding one. Making the link
as you did will not fix the problem (as you saw). In all my installations, I
also have a 64-bit driver installed in /usr/lib64/libcud
> On Mar 26, 2015, at 1:33 AM, Mark Santcroos
> wrote:
>
> Hi guys,
>
> Thanks for the follow-up.
>
> It appears that you are ruling out that Munge is required because the system
> runs TORQUE, but as far as I can see Munge is/can be used by both SLURM and
> TORQUE.
> (http://docs.adaptivec
> On Mar 25, 2015, at 9:38 PM, Gilles Gouaillardet
> wrote:
>
> On 2015/03/26 13:00, Ralph Castain wrote:
>> Well, I did some digging around, and this PR looks like the right solution.
> ok then :-)
>
> following stuff is not directly related to ompi, but you might want to
> comment on that an
> On 26 Mar 2015, at 16:01 , Ralph Castain wrote:
>
>>
>> On Mar 26, 2015, at 1:33 AM, Mark Santcroos
>> wrote:
>>
>> Hi guys,
>>
>> Thanks for the follow-up.
>>
>> It appears that you are ruling out that Munge is required because the system
>> runs TORQUE, but as far as I can see Munge i
Hi everyone,
We are trying to compile custom installs of OpenMPI 1.8.4 on our POWER8 Ubuntu
system. We can configure and build correctly but when running ompi_info we see
many errors like those listed below. It appears that all of the libraries in
the ./lib are static (.a) files. It appears tha
Hi, Rolf,
Thanks a lot for the reply. You are right that the libcuda.so I found in the
/user/local/cuda/lib64/stubs is not correct. I am still not sure why there is a
libcuda.so here though.
I have linked the correct version of libcuda, and now the error is gone.
My linux is Red Hat Enterprise L
Mark,
thanks for the link.
i tried to read between the lines, and "found" that in the case of
torque+munge,
munge might be required only on admin nodes and submission hosts (which
could be restricted
to login nodes on most systems)
on the other hand, slurm does require munge on compute nodes, ev
Could you please send us your configure line?
> On Mar 26, 2015, at 4:47 PM, Hammond, Simon David (-EXP)
> wrote:
>
> Hi everyone,
>
> We are trying to compile custom installs of OpenMPI 1.8.4 on our POWER8
> Ubuntu system. We can configure and build correctly but when running
> ompi_info we
13 matches
Mail list logo
