# -*- text -*-
#
# Copyright (c) 2004-2006 The Trustees of Indiana University and Indiana
#                         University Research and Technology
#                         Corporation.  All rights reserved.
# Copyright (c) 2004-2006 The University of Tennessee and The University
#                         of Tennessee Research Foundation.  All rights
#                         reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
#                         University of Stuttgart.  All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
#                         All rights reserved.
# Copyright (c) 2014-2020 Intel, Inc.  All rights reserved.
# Copyright (c) 2015-2020 Cisco Systems, Inc.  All rights reserved
# Copyright (c) 2021-2026 Nanook Consulting  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
#
[include-exclude]
Both TCP interface include and exclude lists were specified:

  Include: %s
  Exclude: %s

Only one of these can be given.
#
[not-parseable]
The specified network is not parseable. Since we cannot determine
your desired intent, we cannot establish a TCP socket for PMIx
communications and will therefore abort. Please correct the network
specification and retry.
#
[invalid if_inexclude]
WARNING: An invalid value was given for pmix_ptl_base_if_%s.  This
value will be ignored.

  Local host: %s
  Value:      %s
  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 job may hang until the failure reason is fixed
(e.g., more file descriptors and/or memory becomes available), and may
eventually timeout / abort.

  Local host:     %s
  Errno:          %d (%s)
  Probable cause: %s
#
[too-many-conns]
PMIx has found multiple possible servers to which it could
connect. Further guidance is required to ensure the connection
is made to a desirable server. Guidance can be in the form
of the namespace or PID of a specific server, a directive to
connect to a system server, a specific URI to use, or the name
of a rendezvous file.

Some connection handles have been read from files named pmix.*
in subdirectories of $TMPDIR; delete them if they are stale.
#
[file-not-found]
There was an error when attempting to access the specified server
rendezvous file:

  Filename:  %s
  Error:     %s

Please correct the error and try again.
#
[mismatch-id]
The %s ID of the client process does not match the ID registered
by the host runtime:

  Process:     %u
  Registered:  %u

This could be a security issue. Please check the situation and
try again.
#
[no-remote-interfaces]
You requested support for remote tool connections, but no non-loopback
interfaces were found after applying any include or exclude directives:

  Include:    %s
  Exclude:    %s
  Available:  %s

Please adjust your include or exclude to allow selection of a
non-loopback interface.
#
[no-loopback-interfaces]
You requested support for only local tool connections, but no loopback
interfaces were found after applying any include or exclude directives:

  Include:    %s
  Exclude:    %s
  Available:  %s

Please adjust your include or exclude to allow selection of a
loopback interface.
#
[no-available-interfaces]
You requested support for tool connections, but no available
interfaces were found after applying any include or exclude directives:

  Include:    %s
  Exclude:    %s
  Available:  %s

Please adjust your include or exclude to allow selection of an
available interface.
#
[rndz-file-in-use]
A PMIx server was unable to create the rendezvous file by which its
peers locate it because that file already exists and belongs to a
process that is still running:

  Role:   %s
  File:   %s
  Owner:  %s

Only one server can fill a given role on a node at a time. If the
indicated process is no longer serving in this role, then terminate
it (or remove the above file) and try again.
#
[rndz-file-stale]
A PMIx server found a stale rendezvous file left behind by an
instance that is no longer running, but was unable to remove it:

  Role:   %s
  File:   %s
  Error:  %s

Please remove the file and try again.
#
[unknown-attribute]
A PMIx tool asked to connect to its server using an ordered list of
connection targets, but one of the entries is not a connection target:

  Entry:      %s
  Given via:  %s

Each entry must name one of PMIX_CONNECT_SYSTEM_FIRST,
PMIX_CONNECT_TO_SYSTEM, PMIX_CONNECT_TO_SCHEDULER or
PMIX_CONNECT_TO_SYS_CONTROLLER, spelled exactly and with no spaces
around it.
#
[no-available-ports]
A PMIx server was unable to bind its listening socket to any of the
ports it was told to use:

  Node:  %s

Every port in the requested range is already in use. Either free one
of them, or widen (or clear) the "pmix_ptl_base_ipv4_ports" /
"pmix_ptl_base_ipv6_ports" MCA parameter so the kernel is allowed to
choose a port.
#
[unsupported-client-version]
A process attempted to connect to this PMIx server using a version of
the PMIx library that this server does not support:

  Peer version:  %s

This server supports peers using PMIx v2.1 or later. The connection
has been refused.
#
[unsupported-server-version]
This process attempted to connect to a PMIx server that is running a
version of the PMIx library this process does not support:

  Server version:  %d.%d

This version of PMIx can only connect to servers using PMIx v3.2 or
later. The connection has been refused.
#
[no-common-module]
This process cannot connect to the PMIx server at:

  Server:  %s

because the two have no %s in common:

  Server offers:     %s
  This process has:  %s

The connection was not attempted. Make at least one of the same %s
available to both - for example, by not excluding them with the
PMIX_MCA_%s parameter on either side.
#
[server-closed-no-reply]
The PMIx server at:

  %s

closed the connection without answering this process's request to
connect.

The usual reason is that the server runs a different PMIx release and
does not have the wire format or security mechanism this process
offered. This process was given only the server's address, which does
not say what the server accepts, so it offered its own newest.

Give this process the server's rendezvous or report-URI file instead of
its address, as:

  file:<path>

That file says which release the server runs and, from recent releases
on, exactly what it accepts - so this process can choose a match.
