2005-10-05 17:56:35 +04:00
|
|
|
# -*- text -*-
|
|
|
|
|
#
|
2007-03-17 02:11:45 +03:00
|
|
|
# Copyright (c) 2004-2007 The Trustees of Indiana University and Indiana
|
2005-11-05 22:57:48 +03:00
|
|
|
# University Research and Technology
|
|
|
|
|
# Corporation. All rights reserved.
|
|
|
|
|
# Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
|
|
|
# of Tennessee Research Foundation. All rights
|
|
|
|
|
# reserved.
|
2015-06-24 06:59:57 +03:00
|
|
|
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
2005-10-05 17:56:35 +04:00
|
|
|
# University of Stuttgart. All rights reserved.
|
|
|
|
|
# Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
|
# All rights reserved.
|
2011-12-07 18:58:08 +04:00
|
|
|
# Copyright (c) 2011 Oak Ridge National Labs. All rights reserved.
|
2014-04-07 19:41:43 +04:00
|
|
|
# Copyright (c) 2014 Cisco Systems, Inc. All rights reserved.
|
2005-10-05 17:56:35 +04:00
|
|
|
# $COPYRIGHT$
|
2015-06-24 06:59:57 +03:00
|
|
|
#
|
2005-10-05 17:56:35 +04:00
|
|
|
# Additional copyrights may follow
|
2015-06-24 06:59:57 +03:00
|
|
|
#
|
2005-10-05 17:56:35 +04:00
|
|
|
# $HEADER$
|
|
|
|
|
#
|
|
|
|
|
# This is the US/English general help file for Open MPI.
|
|
|
|
|
#
|
|
|
|
|
[opal_init:startup:internal-failure]
|
|
|
|
|
It looks like opal_init failed for some reason; your parallel process is
|
|
|
|
|
likely to abort. There are many reasons that a parallel process can
|
|
|
|
|
fail during opal_init; some of which are due to configuration or
|
|
|
|
|
environment problems. This failure appears to be an internal failure;
|
|
|
|
|
here's some additional information (which may only be relevant to an
|
|
|
|
|
Open MPI developer):
|
|
|
|
|
|
|
|
|
|
%s failed
|
|
|
|
|
--> Returned value %d instead of OPAL_SUCCESS
|
2011-12-03 05:10:52 +04:00
|
|
|
#
|
2011-12-07 18:58:08 +04:00
|
|
|
[opal_cr_init:no-crs]
|
|
|
|
|
It looks like opal_cr_init failed. This usually means that the CRS component
|
|
|
|
|
could not be activated on this machine. Check the installation of your
|
|
|
|
|
checkpointer, MCA parameters, and configuration. If all of that seems
|
|
|
|
|
correct, then copy this error message with the additional information below
|
|
|
|
|
to the Open MPI users list.
|
|
|
|
|
Function: %s
|
|
|
|
|
Return value: %d
|
2013-04-04 20:00:17 +04:00
|
|
|
#
|
|
|
|
|
# Just want a clean printout for sys limit as the
|
|
|
|
|
# message was already generated by show-help
|
|
|
|
|
[opal_init:syslimit]
|
|
|
|
|
%s
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
#
|
|
|
|
|
[opal_init:warn-fork]
|
|
|
|
|
A process has executed an operation involving a call to the
|
|
|
|
|
"fork()" system call to create a child process. Open MPI is currently
|
|
|
|
|
operating in a condition that could result in memory corruption or
|
|
|
|
|
other system errors; your job may hang, crash, or produce silent
|
|
|
|
|
data corruption. The use of fork() (or system() or other calls that
|
2015-06-24 06:59:57 +03:00
|
|
|
create child processes) is strongly discouraged.
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
|
|
|
|
|
The process that invoked fork was:
|
|
|
|
|
|
|
|
|
|
Local host: %s (PID %d)
|
|
|
|
|
|
|
|
|
|
If you are *absolutely sure* that your application will successfully
|
|
|
|
|
and correctly survive a call to fork(), you may disable this warning
|
|
|
|
|
by setting the mpi_warn_on_fork MCA parameter to 0.
|
2014-08-16 15:54:41 +04:00
|
|
|
#
|
|
|
|
|
[mpi-params:leave-pinned-and-pipeline-selected]
|
|
|
|
|
WARNING: Cannot set both the MCA parameters opal_leave_pinned (a.k.a.,
|
|
|
|
|
mpi_leave_pinned) and opal_leave_pinned_pipeline (a.k.a.,
|
|
|
|
|
mpi_leave_pinned_pipeline) to "true". Defaulting to mpi_leave_pinned
|
|
|
|
|
ONLY.
|