# -*- text -*-
#
# Copyright (c) 2025      Nanook Consulting  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English general help file for PRTE's runtime.
#
[prte_init:startup:internal-failure]

It looks like "prte_init()" failed for some reason. There are many
reasons that can cause PRRTE to fail during "prte_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 a PRRTE developer):

   %s failed
   --> Returned value %s (%d) instead of PRTE_SUCCESS
#
[prte:session:dir:prohibited]

The specified location for the temporary directories required by PRTE
is on the list of prohibited locations:

   Location given: %s
   Prohibited locations: %s

If you believe this is in error, please contact your system
administrator to have the list of prohibited locations changed.
Otherwise, please identify a different location to be used (use "-h"
to see the cmd line option), or simply let the system pick a default
location.
#
[failed-to-uncompress]

A compressed message was received that could not be decompressed. This
is most likely due to a missing libz library on the receiving node:

   node:  %s

Please ensure that the "libz" library is present on all compute nodes.
#
[bootstrap-not-found]

Bootstrap startup was requested, but the required configuration file
was not found on at least one node:

   node: %s
   file: %s

Please ensure the file has been installed in the correct location on
every node included in this PRRTE DVM.
#
[bootstrap-missing-field-name]

Bootstrap startup was requested, but the required configuration file
on at least one node is missing the field name on an entry:

   node: %s
   file: %s
   line: %s

Please correct the line.
#
[bootstrap-missing-value]

Bootstrap startup was requested, but the required configuration file
on at least one node is missing a value on an entry:

   node: %s
   file: %s
   line: %s

Please correct the line.
#
[bootstrap-missing-entry]

Bootstrap startup was requested, but the required configuration file
on at least one node is missing a required entry:

   node:   %s
   file:   %s
   entry:  %s

Please provide the missing information.
#
[bootstrap-duplicate-node]

Bootstrap startup was requested, but the configuration file lists the
same host more than once in DVMNodes:

   file:   %s
   host:   %s

A host's position in DVMNodes determines its rank in the DVM, and every
daemon computes its own rank from this same file. A repeated entry
therefore leaves a rank that no daemon will ever claim, and the DVM can
never finish forming.

Please list each host exactly once and try again.
#
[bootstrap-bad-nodelist]

Bootstrap startup was requested, but we were unable to parse the regex
of participating nodes on at least one node:

   node:   %s
   file:   %s
   regex:  %s
   error:  %s

Please fix the error and try again.
#
[bootstrap-bad-entry]

Bootstrap startup was requested, but a line in the configuration file
on at least one node could not be parsed as a "Key=Value" entry:

   node:   %s
   file:   %s
   line:   %s

Please correct the configuration file and try again.
#
[bootstrap-node-not-member]

Bootstrap startup was requested, but this node is neither the configured
DVM controller host nor a member of the configured list of DVM nodes, so
it cannot determine its identity within the DVM:

   node:        %s
   controller:  %s

Please ensure this node is included in the DVMNodes list (or is the
DVMControllerHost) in the configuration file.
#
[bootstrap-ipv6-unavailable]

Bootstrap startup was requested with DVMIPVersion=6, but this PRRTE was
built without IPv6 support:

   node:  %s

Please rebuild PRRTE with IPv6 enabled, or configure the DVM to use IPv4.
#
[bootstrap-unresolved-host]

Bootstrap startup was unable to resolve a DVM member host to an address
of the configured family:

   node:  %s
   host:  %s

Please verify the DVMControllerHost/DVMNodes and DVMIPVersion settings
and that name resolution is available on this node.
#
[bootstrap-ambiguous-address]

Bootstrap startup could not unambiguously determine which address to use
to reach a DVM member: the host resolves to multiple addresses and the
configured networks did not narrow the choice to exactly one.

   node:      %s
   host:      %s
   networks:  %s

Set DVMNetworks to the CIDR (e.g. 10.0.0.0/16) of the interconnect the
DVM should use, so a single address on that network can be selected.
#
[bootstrap-no-matching-address]

Bootstrap startup resolved a DVM member host, but none of its addresses
fall within the configured DVMNetworks:

   node:      %s
   host:      %s
   networks:  %s

Please verify that DVMNetworks names the CIDR of the interconnect these
hosts are reachable on.
#
[prte:session:dir:shared]

PRTE has detected that the head of the session directory tree (where
scratch files and shared memory backing storage will be placed)
resides on a shared file system:

   Directory: %s
   File system type: %s

For performance reasons, it is strongly recommended that the session
directory be located on a local file system. This can be controlled by
setting the system temporary directory to be used by PRTE using either
the TMPDIR envar or the "prte_tmpdir_base" MCA param.

If you need the temporary directory to be different on remote nodes
from the local one where %s is running (e.g., when a login node is
being employed), then you can set the local temporary directory using
the "prte_local_tmpdir_base" MCA param and the one to be used on all
other nodes using the "prte_remote_tmpdir_base" param.

This is only a warning advisory and your job will continue. You can
disable this warning in the future by setting the
"prte_silence_shared_fs" MCA param to "1".
#
[bad-final-order]
A PMIx group construct operation was provided with a final order
directive that caused some group members to be dropped - i.e., the
provided final order does not cover some of the final group members.
Please revise your final order directive so that all final group
members can be included in the returned final membership.
