# -*- text -*-
#
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
#                         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.
# Copyright (c) 2004-2024 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) 2019      Intel, Inc.  All rights reserved.
# Copyright (c) 2020      Cisco Systems, Inc.  All rights reserved
# Copyright (c) 2023-2026 Nanook Consulting  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English general help file for the RAS base.
#
[ras-base:no-allocation]
We were unable to find an allocation for this job as required by
setting the "allocation required" flag. Please ensure you have
the necessary allocation before executing again.

If you wish to execute without a provided allocation (e.g., by
providing a user-specified hostfile), please ensure that the "allocation
required" flag is not set. This flag can be set in several forms, so
please check that none of the following exist:

MCA param file: prte_allocation_required = 1
Environment: PRTE_MCA_prte_allocation_required=1
Cmd line: -prtemca prte_allocation_required 1
#
[ras-base:addhost-not-found]
A request was made to add hosts from a hostfile, but the
file could not be opened for reading:

  File: %s

Please check the filename and try again.
#
[ras-base:addhost-not-a-file]
A request was made to add hosts from a hostfile, but the
path given is not a regular file:

  File: %s

A directory, FIFO, device or socket cannot be read as a hostfile.
Please check the filename and try again.
#
[ras-base:addhost-bad-name]
A host in an add-hostfile is not a name a host can have:

  Host: %s
  File: %s

A host's name is made of letters, digits, ".", "-" and "_", and does
not begin with "-".
#
[ras-base:addhost-user-host]
A host in an add-hostfile names an account to reach it as:

  Host: %s
  File: %s

The DVM reaches every node as the user it runs as, and runs no daemon as
any other user, so a host may not be given as "user@host". Remove the
account and try again.
#
[negative-slots]
A host was provided in an add-hostfile that is unknown
to the DVM but was given a negative number of slots:

  Host:  %s
  Slots: %d

We cannot subtract slots from an unknown host. Please
correct the file or ensure that we are allocated the
host in advance.

[ras-base:bad-slots]
A host in an add-hostfile was given a slot count that is not a number:

  Host:  %s
  File:  %s
  Given: slots=%s

The value must be a whole number - "slots=4" to state a count, or
"slots=+2"/"slots=-2" to adjust the count of a host the DVM already holds.

A value that is not a number used to be read as zero, which is a meaningful
count here: the host would have joined the DVM able to run nothing, and
marked as having been given that count so its real size was never worked out
from its topology.

[ras-base:add-host-managed]
An add-host or add-hostfile directive was given, but this DVM's allocation
is owned by a resource manager.

Only the scheduler can decide which nodes this DVM holds. PRRTE cannot add
one on its own authority - a daemon launched on a node the scheduler has not
granted fails to start, and that failure takes the whole DVM down rather than
just the job that asked for it.

To obtain additional nodes, ask the scheduler for them: outside PRRTE before
starting the DVM, or through a PMIx allocation request that the resource
manager's component can serve.

If the node you named is one the scheduler already granted, and you only want
a daemon started on it, use "--activate" instead - it can name nothing the
allocation does not already contain, so it needs no authority PRRTE lacks.

[ras-base:dvm-not-elastic]
A request to change the size of the DVM was refused:

  Request: %s

This DVM was not started in elastic mode, so the set of nodes it runs daemons
on is fixed for its lifetime: nodes can be neither added to it nor released
from it.  Start the DVM with "--prtemca prte_elastic_mode 1" to allow this.

[ras-base:add-host-unsupported]
An add-host or add-hostfile directive was given, but no active component can
serve it.

The nodes this DVM holds were established by an allocator that does not
support adding to them after the fact - a bootstrapped DVM, for instance,
takes its membership from the configuration file every daemon reads.

[ras-base:activate-unknown]
An activation request named a host that is not part of this DVM's
allocation:

  Host: %s

Activation can only start a daemon on a node the allocation already
contains; it cannot add one. Check the name, or use "--add-host" if PRRTE
owns this allocation and you mean to enlarge it.

The request came either from the "--activate" command line option or from a
PMIX_ALLOC_ACTIVATE allocation request; both name their hosts the same way
and both are held to this rule.

[ras-base:activate-unavailable]
An activation request named a host that is not available for use:

  Host:     %s
  State:    %s
  Given as: %s

A node in this state has either been taken back by the scheduler, or has
been marked unusable. Starting a daemon on it would fail, and a daemon that
fails to start takes the whole DVM down with it.

[ras-base:activate-empty]
An activation request used the "empty node" syntax:

  Given as: %s

"+e" asks for nodes that have no application process running on them, which
says nothing about whether a node is in the DVM - most of the nodes it picks
are already in it. Honoring it here would start no daemon and report success.

If you meant "every node not currently in the DVM", that is "+all". You can
also name the nodes you want, use "+n<K>" to name one by its position in the
allocation, or use "file=<hostfile>" to read them from a file.

[ras-base:activate-nofile]
An activation request gave "file=" with no filename after it.

The form is "--activate file=<hostfile>", naming a file in the same format
"--hostfile" reads. A PMIX_ALLOC_ACTIVATE request may instead give the file
as its own PMIX_HOSTFILE attribute.

[ras-base:spawn-alloc-nodirective]
A spawn carried an allocation request (PMIX_SPAWN_ALLOC) that does not say
what it is asking for.

The value is an array of pmix_info_t describing an allocation request, and
its first element must carry the request's directive as
PMIX_ALLOC_REQ_DIRECTIVE - PMIX_ALLOC_NEW, PMIX_ALLOC_EXTEND, and so on.
The allocation API takes that directive as a parameter; carried as data, it
has to be stated. There is no default: a request whose directive had to be
guessed would ask for something nobody asked for.

The spawn was refused. Nothing was allocated and no processes were started.

[ras-base:activate-nothing-named]
A PMIX_ALLOC_ACTIVATE allocation request named nothing to activate.

The request must carry PMIX_HOST, PMIX_HOSTFILE, or both, saying which of
the nodes this DVM already holds are to have a daemon started on them.
There is no default: activating everything the allocation holds is asked for
explicitly, with a host specification of "+all".

[ras-base:activate-unknown-in-file]
A hostfile given to an activation request names a host that is not part of
this DVM's allocation:

  Host: %s
  File: %s

Activation can only start a daemon on a node the allocation already
contains; it cannot add one. Check the file, or use "--add-hostfile" if PRRTE
owns this allocation and you mean to enlarge it.

[ras-base:activate-slots]
An activation request carried a slot count:

  Given as: %s

Activation cannot change what the allocation grants - it only starts a
daemon on a node the allocation already contains - so a slot count here
could not be honored and is refused rather than silently ignored. Drop the
":N" extension, or use "--add-host" where PRRTE owns the allocation and the
slot count really is PRRTE's to set.
#
[ras-base:node-in-session]
A request named a node that another session holds:

  Node:     %s
  Session:  %u

A session keeps its nodes until it ends or releases them, so they cannot
be given to another session or reservation. The request was refused.
#
[ras-base:user-host]
A request naming hosts was refused, because a host in it names an account
to reach it as ("user@host"):

  Request:  %s

The DVM reaches every node as the user it runs as, and runs no daemon as
any other user, so a host may not name an account. Remove it and try
again.
#
[ras-base:grow-not-permitted]
A request to bring hosts into the DVM was refused, because the user
who made it may not ask for what it named:

  Request:  %s
  Named:    %s

Bringing hosts into a DVM changes what it consists of, and is for root,
the user the DVM runs as, and the users and groups the DVM was started
with ("--rtos users=..." and "groups=..."). A file of hosts is read as
the user who named it, and its hosts are judged the same way. A session
control directive to instantiate
or extend a session is held to the same rules, including when it comes
from the session's owner: a user asks for more resources with an
allocation request, which the scheduler decides.
#
[ras-base:limit-not-permitted]
A request to change an allocation's time limit was refused:

  Allocation:  %s

The limit was set by the scheduler, or by a user who may change the DVM
(root, the user the DVM runs as, and the users and groups the DVM was
started with), and only they may change it. A limit the allocation's
owner set on its own request may be changed by the owner.
#
[ras-base:release-not-permitted]
A request to take nodes out of the DVM was refused, because the user who
made it may not release what it named:

  Named:  %s

An allocation, and a node of a reservation, may be released by the
reservation's owner, root and the user the DVM runs as - and by members of
its group, when that group was named for it. A node of the DVM's general pool, or a number of nodes the
DVM is to choose, may be released only by those who may change what the
DVM consists of: root, the user the DVM runs as, and the users and groups
the DVM was started with ("--rtos users=..." and "groups=...").
#
[ras-base:alloc-owner-missing]
An allocation request was answered without saying whom the allocation
belongs to:

  Request:  %s

The component that served the request must return the user and group the
allocation was granted for, as PMIX_ALLOC_UID and PMIX_ALLOC_GID. Without
them there is no owner to record for the allocation, so the request was
treated as failed.
#
[ras-base:alloc-id-requested]
A request for a new allocation carried an allocation id (PMIX_ALLOC_ID).

The id of an allocation is assigned by the scheduler that grants it, or by
the DVM when there is no scheduler, and is returned in the response. A
requester names its request with PMIX_ALLOC_REQ_ID instead. The request was
refused.
#
[ras-base:alloc-id-missing]
A new allocation was granted without an allocation id (PMIX_ALLOC_ID).

The component that served the request must return the id the allocation
was given: it is how the allocation is named from then on, and without it
nothing could extend or release the allocation. The request was treated as
failed.
#
[ras-base:req-id-ambiguous]
A request named an allocation by the request id it was made under
(PMIX_ALLOC_REQ_ID), but the job making the request made more than one
allocation request under that id:

  Request id:  %s

A request id need not be unique, so it cannot say which of them is meant.
Name the allocation by its allocation id (PMIX_ALLOC_ID) instead, which was
returned when the allocation was granted and which a query for
PMIX_QUERY_ALLOC_IDS lists. The request was refused.
#
[ras-base:alloc-id-in-use]
A new allocation was granted with an allocation id that already names
another allocation:

  Allocation id:  %s

Allocation ids must be unique, as each is how its allocation is named. The
request was treated as failed, and the existing allocation is unchanged.
#
[ras-base:alloc-owner-mismatch]
A scheduler answered an allocation request for a different user or group
than the one it was asked for:

  Request:   %s
  Asked for: uid %u, gid %u
  Answered:  %s

The allocation was refused and returned to the scheduler. A scheduler must
grant an allocation for the user and group named in the request
(PMIX_ALLOC_UID and PMIX_ALLOC_GID), and say so in its answer.
