1 | # -*- text -*- |
---|
2 | # |
---|
3 | # Copyright (c) 2004-2006 The Trustees of Indiana University and Indiana |
---|
4 | # University Research and Technology |
---|
5 | # Corporation. All rights reserved. |
---|
6 | # Copyright (c) 2004-2006 The University of Tennessee and The University |
---|
7 | # of Tennessee Research Foundation. All rights |
---|
8 | # reserved. |
---|
9 | # Copyright (c) 2004-2005 High Performance Computing Center Stuttgart, |
---|
10 | # University of Stuttgart. All rights reserved. |
---|
11 | # Copyright (c) 2004-2005 The Regents of the University of California. |
---|
12 | # All rights reserved. |
---|
13 | # $COPYRIGHT$ |
---|
14 | # |
---|
15 | # Additional copyrights may follow |
---|
16 | # |
---|
17 | # $HEADER$ |
---|
18 | # |
---|
19 | [no-available-pls] |
---|
20 | No available launching agents were found. |
---|
21 | |
---|
22 | This is an unusual error; it means that Open RTE was unable to find |
---|
23 | any mechanism to launch proceses, and therefore is unable to start the |
---|
24 | process(es) required by your application. |
---|
25 | # |
---|
26 | [daemon-died-no-signal] |
---|
27 | A daemon (pid %s) died unexpectedly with status %d while attempting |
---|
28 | to launch so we are aborting. |
---|
29 | |
---|
30 | There may be more information reported by the environment (see above). |
---|
31 | |
---|
32 | This may be because the daemon was unable to find all the needed shared |
---|
33 | libraries on the remote node. You may set your LD_LIBRARY_PATH to have the |
---|
34 | location of the shared libraries on the remote nodes and this will |
---|
35 | automatically be forwarded to the remote nodes. |
---|
36 | # |
---|
37 | [daemon-died-signal-core] |
---|
38 | A daemon (pid %s) died unexpectedly on signal %d (with core) while |
---|
39 | attempting to launch so we are aborting. |
---|
40 | |
---|
41 | There may be more information reported by the environment (see above). |
---|
42 | |
---|
43 | This may be because the daemon was unable to find all the needed shared |
---|
44 | libraries on the remote node. You may set your LD_LIBRARY_PATH to have the |
---|
45 | location of the shared libraries on the remote nodes and this will |
---|
46 | automatically be forwarded to the remote nodes. |
---|
47 | # |
---|
48 | [daemon-died-signal] |
---|
49 | A daemon (pid %s) died unexpectedly on signal %d while attempting to |
---|
50 | launch so we are aborting. |
---|
51 | |
---|
52 | There may be more information reported by the environment (see above). |
---|
53 | |
---|
54 | This may be because the daemon was unable to find all the needed shared |
---|
55 | libraries on the remote node. You may set your LD_LIBRARY_PATH to have the |
---|
56 | location of the shared libraries on the remote nodes and this will |
---|
57 | automatically be forwarded to the remote nodes. |
---|
58 | # |
---|
59 | [incomplete-exit-cmd] |
---|
60 | One or more daemons could not be ordered to exit. This can be caused by a |
---|
61 | number of rather rare problems, but typically is caused by a daemon having |
---|
62 | died due to the failure of a node or its communications. This could result |
---|
63 | in an incomplete cleanup on the affected nodes. Please see below for a list |
---|
64 | of nodes which may require additional cleanup. |
---|
65 | |
---|
66 | We are truly sorry for the inconvenience. |
---|
67 | # |
---|
68 | [incomplete-kill-procs-cmd] |
---|
69 | One or more daemons could not be ordered to kill their local processes. |
---|
70 | This can be caused by a number of rather rare problems, but typically |
---|
71 | is caused by a daemon having died due to the failure of a node or its |
---|
72 | communications. This could result in an incomplete cleanup on the affected |
---|
73 | nodes. Additional information may be available below. |
---|
74 | |
---|
75 | We are truly sorry for the inconvenience. |
---|
76 | # |
---|
77 | [stdin-target-out-of-range] |
---|
78 | The requested stdin target is out of range for this job - it points |
---|
79 | to a process rank that is greater than the number of processes in the |
---|
80 | job. |
---|
81 | |
---|
82 | Specified target: %s |
---|
83 | Number of procs: %s |
---|
84 | |
---|
85 | This could be caused by specifying a negative number for the stdin |
---|
86 | target, or by mistyping the desired rank. Remember that MPI ranks begin |
---|
87 | with 0, not 1. |
---|
88 | |
---|
89 | Please correct the cmd line and try again. |
---|
90 | |
---|