openmpi/opal/mca/btl/tcp/help-mpi-btl-tcp.txt

# -*- text -*-
#
# Copyright (c) 2009-2016 Cisco Systems, Inc.  All rights reserved.
# Copyright (c) 2015-2016 The University of Tennessee and The University
#                         of Tennessee Research Foundation.  All rights
#                         reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English help file for Open MPI's TCP support
# (the openib BTL).
#
[invalid if_inexclude]
WARNING: An invalid value was given for btl_tcp_if_%s.  This
value will be ignored.

  Local host: %s
  Value:      %s
  Message:    %s
#
[invalid minimum port]
WARNING: An invalid value was given for the btl_tcp_port_min_%s. Legal
values are in the range [1 .. 2^16-1]. This value will be ignored
(reset to the default value of 1024).

  Local host: %s
  Value:      %d
#
[client connect fail]
WARNING: Open MPI failed to TCP connect to a peer MPI process.  This
should not happen.

Your Open MPI job may now fail.

  Local host: %s
  PID:        %d
  Message:    %s
  Error:      %s (%d)
#
[client handshake fail]
WARNING: Open MPI failed to handshake with a connecting peer MPI
process over TCP.  This should not happen.

Your Open MPI job may now fail.

  Local host: %s
  PID:        %d
  Message:    %s
#
[accept failed]
WARNING: The accept(3) system call failed on a TCP socket.  While this
should generally never happen on a well-configured HPC system, the
most common causes when it does occur are:

  * The process ran out of file descriptors
  * The operating system ran out of file descriptors
  * The operating system ran out of memory

Your Open MPI job will likely hang (or crash) until the failure
resason is fixed (e.g., more file descriptors and/or memory becomes
available), and may eventually timeout / abort.

  Local host: %s
  PID:        %d
  Errno:      %d (%s)
#
[unsuported progress thread]
WARNING: Support for the TCP progress thread has not been compiled in.
Fall back to the normal progress.

  Local host: %s
  Value:      %s
  Message:    %s
Add the ability to btl_tcp_if_include and btl_tcp_if_exclude based on subnet specifications (in addition to interface names). These parameters now take a comma-delimited list of interfaces names and/or a.b.c.d/x specifications (only IPv4 currently supported for subnet specifications). For example: mpirun --mca btl_tcp_if_include 10.10.30.0/8,eth0 This commit was SVN r21189. 2009-05-07 22:53:33 +04:00			`# -- text --`
			`#`
btl/tcp: fix help message It looks like one help message was accidentally pasted in the middle of another. Disentangle the two messages from each other, and slightly tweak the one message to say that the job may also crash (in addition to hanging). Signed-off-by: Jeff Squyres <jsquyres@cisco.com> 2016-09-03 00:14:22 +03:00			`# Copyright (c) 2009-2016 Cisco Systems, Inc. All rights reserved.`
Update the copyright and cleanup the code. Per @jsquyres suggestion remove all trailing spaces. Credit to `sed -i.bak 's/ $//' /[ch]`. 2016-03-21 21:56:33 +03:00			`# Copyright (c) 2015-2016 The University of Tennessee and The University`
			`# of Tennessee Research Foundation. All rights`
			`# reserved.`
Add the ability to btl_tcp_if_include and btl_tcp_if_exclude based on subnet specifications (in addition to interface names). These parameters now take a comma-delimited list of interfaces names and/or a.b.c.d/x specifications (only IPv4 currently supported for subnet specifications). For example: mpirun --mca btl_tcp_if_include 10.10.30.0/8,eth0 This commit was SVN r21189. 2009-05-07 22:53:33 +04:00			`# $COPYRIGHT$`
Purge whitespace from the repo 2015-06-24 06:59:57 +03:00			`#`
Add the ability to btl_tcp_if_include and btl_tcp_if_exclude based on subnet specifications (in addition to interface names). These parameters now take a comma-delimited list of interfaces names and/or a.b.c.d/x specifications (only IPv4 currently supported for subnet specifications). For example: mpirun --mca btl_tcp_if_include 10.10.30.0/8,eth0 This commit was SVN r21189. 2009-05-07 22:53:33 +04:00			`# Additional copyrights may follow`
Purge whitespace from the repo 2015-06-24 06:59:57 +03:00			`#`
Add the ability to btl_tcp_if_include and btl_tcp_if_exclude based on subnet specifications (in addition to interface names). These parameters now take a comma-delimited list of interfaces names and/or a.b.c.d/x specifications (only IPv4 currently supported for subnet specifications). For example: mpirun --mca btl_tcp_if_include 10.10.30.0/8,eth0 This commit was SVN r21189. 2009-05-07 22:53:33 +04:00			`# $HEADER$`
			`#`
			`# This is the US/English help file for Open MPI's TCP support`
			`# (the openib BTL).`
			`#`
* No need for warning aggregation here; orte_show_help() does that for us already. * Slightly clarify the error message strings; now they match the new error strings for btl_openib_ipaddr_in\|exclude This commit was SVN r21197. 2009-05-09 16:29:06 +04:00			`[invalid if_inexclude]`
Add the ability to btl_tcp_if_include and btl_tcp_if_exclude based on subnet specifications (in addition to interface names). These parameters now take a comma-delimited list of interfaces names and/or a.b.c.d/x specifications (only IPv4 currently supported for subnet specifications). For example: mpirun --mca btl_tcp_if_include 10.10.30.0/8,eth0 This commit was SVN r21189. 2009-05-07 22:53:33 +04:00			`WARNING: An invalid value was given for btl_tcp_if_%s. This`
			`value will be ignored.`

Note to self: test error messages before committing. This commit was SVN r21190. 2009-05-08 00:31:26 +04:00			`Local host: %s`
			`Value: %s`
			`Message: %s`
Fixes trac:2838: add a warning message and disqualify the TCP BTL if both btl_tcp_if_include and btl_tcp_if_exclude are specified. This commit was SVN r24976. The following Trac tickets were found above: Ticket 2838 --> https://svn.open-mpi.org/trac/ompi/ticket/2838 2011-08-02 03:30:33 +04:00			`#`
Pretty print an error message when the specified range of ports (for both IPv4 and IPv6) is outside the legal boundaries. This fixes trac:1869. This commit was SVN r21612. The following Trac tickets were found above: Ticket 1869 --> https://svn.open-mpi.org/trac/ompi/ticket/1869 2009-07-07 21:52:30 +04:00			`[invalid minimum port]`
			`WARNING: An invalid value was given for the btl_tcp_port_min_%s. Legal`
			`values are in the range [1 .. 2^16-1]. This value will be ignored`
			`(reset to the default value of 1024).`

			`Local host: %s`
			`Value: %d`
Add missing show_help message. Found via Cisco MTT (i.e., it complained of not being able to find this show_help message). cmr=v1.8:reviewer=dgoodell This commit was SVN r31144. 2014-03-19 18:09:19 +04:00			`#`
Fixes trac:3494: If we get 0 bytes back for the ACK, it doesn't necessarily mean an error -- it could (and usually does) mean that the peer realized that we both initiated a connect at the same time, and therefore it decided to hang up. I also added a friendly show_help error message for other cases where recv_blocking() fails (i.e., "Something went wrong. Kaboom! Your job will abort..."). This commit was SVN r28023. The following Trac tickets were found above: Ticket 3494 --> https://svn.open-mpi.org/trac/ompi/ticket/3494 2013-02-02 05:19:03 +04:00			`[client connect fail]`
			`WARNING: Open MPI failed to TCP connect to a peer MPI process. This`
			`should not happen.`

			`Your Open MPI job may now fail.`

			`Local host: %s`
			`PID: %d`
			`Message: %s`
			`Error: %s (%d)`
			`#`
Add missing show_help message. Found via Cisco MTT (i.e., it complained of not being able to find this show_help message). cmr=v1.8:reviewer=dgoodell This commit was SVN r31144. 2014-03-19 18:09:19 +04:00			`[client handshake fail]`
			`WARNING: Open MPI failed to handshake with a connecting peer MPI`
			`process over TCP. This should not happen.`

			`Your Open MPI job may now fail.`

			`Local host: %s`
			`PID: %d`
			`Message: %s`
			`#`
Per discussion with George and Ralph, change this BTL_ERROR message to an opal_show_help() so that its output is deduplicated. This commit was SVN r31590. 2014-05-02 00:15:33 +04:00			`[accept failed]`
			`WARNING: The accept(3) system call failed on a TCP socket. While this`
			`should generally never happen on a well-configured HPC system, the`
			`most common causes when it does occur are:`

			`* The process ran out of file descriptors`
			`* The operating system ran out of file descriptors`
			`* The operating system ran out of memory`

btl/tcp: fix help message It looks like one help message was accidentally pasted in the middle of another. Disentangle the two messages from each other, and slightly tweak the one message to say that the job may also crash (in addition to hanging). Signed-off-by: Jeff Squyres <jsquyres@cisco.com> 2016-09-03 00:14:22 +03:00			`Your Open MPI job will likely hang (or crash) until the failure`
			`resason is fixed (e.g., more file descriptors and/or memory becomes`
			`available), and may eventually timeout / abort.`

			`Local host: %s`
			`PID: %d`
			`Errno: %d (%s)`
			`#`
Enable Threading in the BTL TCP Added mca parameter to turn progress thread on/off Add a flag to check if we have btl progress thread. Added macro for ob1 matching lock. Update the AUTHORS file. 2016-01-22 23:41:44 +03:00			`[unsuported progress thread]`
			`WARNING: Support for the TCP progress thread has not been compiled in.`
			`Fall back to the normal progress.`

			`Local host: %s`
			`Value: %s`
			`Message: %s`