# -*- 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
#
[local-unreachable]
This process could not reach the socket of the PMIx server that started
it, on this host, and cannot continue. It does not fall back to another
way of connecting.

  Local host: %s
  Socket:     %s
  Reason:     %s

The socket is in the server's temporary directory. A process in a
container needs that directory mounted, and must run as a user the
socket lets in.
#
[local-uri-bad]
The variable through which the PMIx server that started this process
said where it listens could not be read:

  %s=%s

It should hold "<namespace>.<rank>;<address>;<uid>:<gid>".
#
[server-unidentified]
This process could not learn, from the kernel, which user runs the PMIx
server it connected to on host %s, and will not talk to it.
#
[server-not-local]
This process on %s will not connect to the PMIx server at

  %s:%d

because that address is not this host's. A process connects only to a
server on its own host.
#
[server-unnamed]
This process on %s will not connect to the PMIx server at

  %s:%d

The kernel here keeps no table of TCP connections that this process can
read, so it cannot tell which user runs that server.

It connects to a server the kernel cannot name only when the server's
address came from a source that answers for it: the environment the
server started this process with, a URI passed directly (PMIX_SERVER_URI
or PMIX_TCP_URI), or the server's rendezvous file named by the caller
("file:<path>" or PMIX_TOOL_ATTACHMENT_FILE) - a file only its owner can
write, owned by this process's user, root, or a user
pmix_ptl_base_server_access names. A server found by searching for its
file never qualifies. Name the server's file, or pass its URI.

A server of v7.0 or later also listens on a local socket, where the
kernel names its user: its rendezvous file names that socket.
#
[server-unmapped]
This process on %s will not connect to the PMIx server it reached: the
kernel reports that server's user as

  uid %lu

an id from outside this process's user namespace, so it cannot tell who
runs the server. This is usual in a rootless container whose server runs
on the host.

It connects to such a server only when the server's address came from a
source that answers for it: the environment the server started this
process with, a URI passed directly (PMIX_SERVER_URI or PMIX_TCP_URI),
or the server's rendezvous file named by the caller ("file:<path>" or
PMIX_TOOL_ATTACHMENT_FILE). A server found by searching for its file
never qualifies. Name the server's file, or pass its URI.
#
[server-identity]
The PMIx server this process connected to on host %s is not one it may
talk to: the kernel reports it runs as

  uid %lu, gid %lu

and it should be %s.
#
[server-identity-tcp]
The PMIx server this process connected to over TCP on host %s is not
one it may talk to: the kernel reports that its end of the connection
belongs to

  uid %lu

and it should be %s. The kernel records no group for a TCP connection,
so pmix_ptl_base_server_access can accept such a server by its user
alone.
#
[server-access-bad]
The value of pmix_ptl_base_server_access could not be used:

  %s

It names further servers a client or tool will talk to, as
"users=<list>,groups=<list>" - either may be left out - where each list
is user or group names or numbers separated by ':'. Every name must be
one this system knows, no list may be empty, and each directive may be
given once.
#
[usock-listener]
The PMIx server could not open the socket the processes on its host
connect to, and cannot run without it.

  Local host: %s
  Socket:     %s
  Reason:     %s

The socket is made in a directory of its own beneath the server's
temporary directory. If the path is too long - a socket's path is
limited to about 100 characters - pass the server a shorter temporary
directory.
#
[bad if_inexclude]
An invalid value was given for pmix_ptl_base_if_%s, so the listener
cannot be opened as asked.

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

Each entry must be an interface name or a subnet in CIDR notation
(e.g., "eth0,192.168.0.0/16").
#
[no-include-match]
None of the interfaces or subnets in pmix_ptl_base_if_include is on
this host, so the listener cannot be opened on any of them.

  Local host: %s
  Include:    %s

Please name an interface or subnet this host has.
#
[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.
#
[no-loopback-interfaces]
This PMIx server takes TCP connections on a loopback interface only,
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.
#
[remote-connections-not-supported]
The host asked the PMIx server on %s to take connections from tools on
other hosts (PMIX_SERVER_REMOTE_CONNECTIONS). A PMIx server takes
connections from its own host only: do not ask for remote connections.
#
[legacy-clients-not-built]
The PMIx server on %s was asked, by %s, to take
connections from clients and tools of PMIx releases before v7.0, but
this PMIx was built without support for them.

Rebuild PMIx configured --enable-legacy-clients, or do not ask for them.
#
[legacy-servers-not-built]
A process on %s was to connect to a PMIx server of release
%d.%d, but this PMIx was built without support for servers of releases
before v7.0. The connection has been refused.

Run the process under a server of PMIx v7.0 or later, or rebuild PMIx
configured --enable-legacy-servers.
#
[legacy-servers-param-not-built]
A process on %s was asked, by ptl_base_legacy_servers, to
look for PMIx servers of releases before v7.0, but this PMIx was built
without support for them.

Rebuild PMIx configured --enable-legacy-servers, or do not ask for them.
#
[legacy-servers-tcp]
A process on %s was given a PMIx server's TCP address to
connect to:

  %s

Only a server of a PMIx release before v7.0 is reached over TCP, and
this PMIx was built without support for those (it was not configured
--enable-legacy-servers). A server of v7.0
or later is reached on its local socket, which its report or rendezvous
file names on its "local:" line.
#
[rndz-name-held]
A PMIx server was unable to take the name of the rendezvous file by
which its peers locate it, because another server holds it:

  Role:   %s
  File:   %s
  Held:   %s

Only one server can fill a given role on a node at a time. The lock is
held by a running process - the server in that role, or, if it has gone,
a process it started without exec'ing another program, which holds the
lock until it exits. Removing the file does not free the name.
#
[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.
#
[local-uri-required-uri]
The PMIx server would not take this process at the address it was
given:

  %s

That is the server's TCP address, which a server of PMIx v7.0 or later
offers only to clients and tools of earlier releases. A client or tool
of v7.0 or later connects on the server's local socket: pass the
"usock://" URI the server reports, or name the server's report file
("file:<path>"), whose "local:" line gives that socket.
#
[tcp-uri-alone]
This process was given a PMIx server's TCP address to connect to:

  %s

A client or tool of PMIx v7.0 or later does not connect to a server at
a TCP address alone:

  - a server of v7.0 or later takes it on its local socket: pass the
    "usock://" URI the server reports, or name the server's report file
    ("file:<path>"), whose "local:" line gives that socket;

  - a server of an earlier release is reached only through its
    rendezvous file: name it ("file:<path>").
#
[local-uri-required-file]
The PMIx server would not take this process at the TCP address the file

  %s

gave for it. A server of PMIx v7.0 or later offers TCP only to clients
and tools of earlier releases; a client or tool of v7.0 or later
connects on the server's local socket, which the server's own report
or rendezvous file names on its "local:" line. This file names only the
TCP address - it was written by hand, or is read on a host other than
the server's. Use the server's own file, on the server's host.
#
[report-tcp-no-listener]
The PMIx server was asked to report its TCP URI:

  %s

but it has no TCP listener: it opens one only to take clients and tools
of releases before v7.0, when legacy clients are on (the
ptl_base_legacy_clients parameter, or PMIX_SERVER_LEGACY_PEERS, in a
PMIx built with --enable-legacy-clients). A reader of an earlier release
could not connect to this server in any case.

To report the URI a client or tool of v7.0 or later uses, give "-"
(stdout) or "+" (stderr).
#
[rndz-dir-not-ours]
This PMIx server writes the files tools find it by in a directory that
only its own user can write:

  %s

but %s. So it does not write those files there, and runs on: its clients
reach it by the address they are given, but %s.

The directory must be a directory of this server's user, not a link,
that no other user can write. Another user made it first, or it was left
with the wrong owner or mode. Removing it - its owner or an
administrator can - lets the server make it again.

The server writes them in $XDG_RUNTIME_DIR/pmix instead when
XDG_RUNTIME_DIR names a directory of this user's that no other user can
write; it did not here. Or name a system tmpdir of this user's own, by
the PMIX_SYSTEM_TMPDIR environment variable or the host's
PMIX_SYSTEM_TMPDIR attribute: the directory is then made below it. Its
tools must be given the same PMIX_SYSTEM_TMPDIR to find the server.
#
[rndz-dir-elsewhere]
This PMIx server writes the files tools find it by in a directory that
only its own user can write:

  %s

but %s. So it writes those files in

  %s

instead. Tools of this user look there too; tools of other users this
server takes cannot reach that directory, and cannot find this server by
its files.

The directory must be a directory of this server's user, not a link,
that no other user can write. Another user made it first, or it was left
with the wrong owner or mode. Removing it - its owner or an
administrator can - lets the server make it again. Or name a system
tmpdir of this user's own, by the PMIX_SYSTEM_TMPDIR environment
variable or the host's PMIX_SYSTEM_TMPDIR attribute: the directory is
then made below it.
#
[server-not-file-owner]
This process on %s will not talk to the PMIx server it reached: the
kernel reports it runs as

  uid %lu

but the rendezvous file that gave its address is owned by uid %lu. A
server writes its own file, so the process answering at that address
is not the one that wrote it.
#
[server-not-file-pid]
This process on %s will not talk to the PMIx server it reached: the
kernel reports it is

  pid %lu

but it was looked for, and its rendezvous file found, as pid %lu. The
process answering at that address is not the one asked for.
#
[rndz-file-foreign]
This PMIx server did not write its %s rendezvous file

  %s

because a file of another user's (uid %lu) is at that name. A server
never takes over, or removes, another user's file, and does not count
it as another server of its own. It runs on: its clients reach it by
the address they are given, but tools cannot find it by that file.

The file's owner, or an administrator, can remove it.
#
[tmpdir-unsafe]
This PMIx server's %s tmpdir

  %s

lies below a directory another user could change:

  Directory:  %s
  Owner:      uid %lu
  Mode:       %04o
  Why:        %s

That user could move this server's directories aside and put others at
their names, and the server's clients would fail to connect. So the
server will not start.

Every directory above a tmpdir must be owned by root or by this
server's user, and writable by nobody else - unless it has the sticky
bit, as /tmp does, or its group's only member is its owner. The tmpdir
itself may be any user's, if nobody else can write it.

Where no other user shares the directory - a container's own volume,
such as a Kubernetes emptyDir mounted at /tmp - set the MCA parameter
ptl_base_tmpdir_check to "warn" to start anyway and say so, or to
"silent" not to check. Or give the directory the sticky bit.
#
[tmpdir-unsafe-warn]
This PMIx server's %s tmpdir

  %s

lies below a directory another user could change:

  Directory:  %s
  Owner:      uid %lu
  Mode:       %04o
  Why:        %s

That user could move this server's directories aside and put others at
their names, and the server's clients would fail to connect. The server
runs on, as ptl_base_tmpdir_check=warn says; "silent" would not check.
#
[tmpdir-check-bad]
The value of ptl_base_tmpdir_check could not be used:

  %s

It must be "refuse" (the default), "warn", or "silent".
#
[report-file-not-ours]
This PMIx server was asked to report its URI in the file

  %s

but a file of another user's (uid %lu) is at that name. The server
does not write into another user's file: it would stay theirs, and they
could rewrite it afterwards to send its readers elsewhere. The server
will not start.

Name a file in a directory of your own, or have the file's owner remove
it.
#
[role-needs-tool-support]
The PMIx server on %s was asked to be
%s, and also told not to support tools
(PMIX_SERVER_TOOL_SUPPORT set false).

Everything that connects to that role connects as a tool, so a server
that refuses tools can serve nothing. The server will not start: leave
PMIX_SERVER_TOOL_SUPPORT out, set it true, or do not ask for the role.
#
[session-server-no-id]
The PMIx server on %s was asked to be a session-level server
(PMIX_SERVER_SESSION_SUPPORT) but was not given the ID that names its
rendezvous file (PMIX_SESSION_RNDZ_ID), nor the session's ID
(PMIX_SESSION_ID) to name it by instead.

A session-level server's rendezvous file is named by that ID, so that
servers of different sessions can share a node and a tool can ask for
the one it wants. The server will not start: give it one of the two, or
do not ask it to be a session-level server.
#
[session-rndz-id-bad]
The PMIx server on %s was given a %s it could not use to name its
session-level rendezvous file: a value of type %s, where a uint32_t is
expected.

The server will not start.
#
[too-many-sessions]
This tool was not told which PMIx server to connect to, and more than
one session-level server of yours runs on this node:

%s
Name the one you want: by its rendezvous ID (PMIX_SESSION_RNDZ_ID), its
namespace (PMIX_SERVER_NSPACE) or its pid (PMIX_SERVER_PIDINFO) - for
PRRTE's tools, --namespace or --pid - or by its URI or rendezvous file.
#
[client-uri-not-local]
This process was given a PMIx server to connect to by its name and
address alone:

  %s

A client connects to a server given that way only on the server's
local socket ("usock://"), whose handshake says what the server speaks.
For any other address, put the server's URI variables first:
"<variable>[:<variable>...];<namespace>.<rank>;<address>".
#
[client-namespace-no-uri]
This process on %s was given a namespace by the PMIx server that
started it:

  PMIX_NAMESPACE=%s

but no variable saying how to reach that server. It cannot run as a
member of that namespace without its server, and will not start.
#
[singleton-refused]
This process on %s started without a PMIx server and found the
system server on this host, %s, which did not accept it:

  %s

A system server accepts a process it was not told of only if that
process's namespace has been registered with it. The process runs as
a singleton, without a server.
