[97] | 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-2005 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 (c) 2007 Cisco Systems, Inc. All rights reserved. |
---|
| 14 | # $COPYRIGHT$ |
---|
| 15 | # |
---|
| 16 | # Additional copyrights may follow |
---|
| 17 | # |
---|
| 18 | # $HEADER$ |
---|
| 19 | # |
---|
| 20 | # This is the US/English general help file for Open RTE's orterun. |
---|
| 21 | # |
---|
| 22 | [orterun:init-failure] |
---|
| 23 | Open RTE was unable to initialize properly. The error occured while |
---|
| 24 | attempting to %s. Returned value %d instead of ORTE_SUCCESS. |
---|
| 25 | [orterun:usage] |
---|
| 26 | %s (%s) %s |
---|
| 27 | |
---|
| 28 | Usage: %s [OPTION]... [PROGRAM]... |
---|
| 29 | Start the given program using Open RTE |
---|
| 30 | |
---|
| 31 | %s |
---|
| 32 | |
---|
| 33 | Report bugs to %s |
---|
| 34 | [orterun:version] |
---|
| 35 | %s (%s) %s |
---|
| 36 | |
---|
| 37 | Report bugs to %s |
---|
| 38 | [orterun:allocate-resources] |
---|
| 39 | %s was unable to allocate enough resources to start your application. |
---|
| 40 | This might be a transient error (too many nodes in the cluster were |
---|
| 41 | unavailable at the time of the request) or a permenant error (you |
---|
| 42 | requsted more nodes than exist in your cluster). |
---|
| 43 | |
---|
| 44 | While probably only useful to Open RTE developers, the error returned |
---|
| 45 | was %d. |
---|
| 46 | [orterun:error-spawning] |
---|
| 47 | %s was unable to start the specified application. An attempt has been |
---|
| 48 | made to clean up all processes that did start. The error returned was |
---|
| 49 | %d. |
---|
| 50 | [orterun:appfile-not-found] |
---|
| 51 | Unable to open the appfile: |
---|
| 52 | |
---|
| 53 | %s |
---|
| 54 | |
---|
| 55 | Double check that this file exists and is readable. |
---|
| 56 | [orterun:executable-not-specified] |
---|
| 57 | No executable was specified on the %s command line. |
---|
| 58 | |
---|
| 59 | Aborting. |
---|
| 60 | [orterun:multi-apps-and-zero-np] |
---|
| 61 | %s found multiple applications specified on the command line, with |
---|
| 62 | at least one that failed to specify the number of processes to execute. |
---|
| 63 | When specifying multiple applications, you must specify how many processes |
---|
| 64 | of each to launch via the -np argument. |
---|
| 65 | [orterun:nothing-to-do] |
---|
| 66 | %s could not find anything to do. |
---|
| 67 | |
---|
| 68 | It is possible that you forgot to specify how many processes to run |
---|
| 69 | via the "-np" argument. |
---|
| 70 | [orterun:call-failed] |
---|
| 71 | %s encountered a %s call failure. This should not happen, and |
---|
| 72 | usually indicates an error within the operating system itself. |
---|
| 73 | Specifically, the following error occurred: |
---|
| 74 | |
---|
| 75 | %s |
---|
| 76 | |
---|
| 77 | The only other available information that may be helpful is the errno |
---|
| 78 | that was returned: %d. |
---|
| 79 | [orterun:environ] |
---|
| 80 | %s was unable to set |
---|
| 81 | %s = %s |
---|
| 82 | in the environment. Returned value %d instead of ORTE_SUCCESS. |
---|
| 83 | [orterun:precondition] |
---|
| 84 | %s was unable to precondition transports |
---|
| 85 | Returned value %d instead of ORTE_SUCCESS. |
---|
| 86 | [orterun:attr-failed] |
---|
| 87 | %s was unable to define an attribute |
---|
| 88 | Returned value %d instead of ORTE_SUCCESS. |
---|
| 89 | # |
---|
| 90 | [orterun:proc-ordered-abort] |
---|
| 91 | %s has exited due to process rank %lu with PID %lu on |
---|
| 92 | node %s calling "abort". This may have caused other processes |
---|
| 93 | in the application to be terminated by signals sent by %s |
---|
| 94 | (as reported here). |
---|
| 95 | # |
---|
| 96 | [orterun:proc-exit-no-sync] |
---|
| 97 | %s has exited due to process rank %lu with PID %lu on |
---|
| 98 | node %s exiting without calling "finalize". This may |
---|
| 99 | have caused other processes in the application to be |
---|
| 100 | terminated by signals sent by %s (as reported here). |
---|
| 101 | # |
---|
| 102 | [orterun:proc-exit-no-sync-unknown] |
---|
| 103 | %s has exited due to a process exiting without calling "finalize", |
---|
| 104 | but has no info as to the process that caused that situation. This |
---|
| 105 | may have caused other processes in the application to be |
---|
| 106 | terminated by signals sent by %s (as reported here). |
---|
| 107 | # |
---|
| 108 | [orterun:proc-aborted] |
---|
| 109 | %s noticed that process rank %lu with PID %lu on node %s exited on signal %d. |
---|
| 110 | # |
---|
| 111 | [orterun:proc-aborted-unknown] |
---|
| 112 | %s noticed that the job aborted, but has no info as to the process |
---|
| 113 | that caused that situation. |
---|
| 114 | # |
---|
| 115 | [orterun:proc-aborted-signal-unknown] |
---|
| 116 | %s noticed that the job aborted by signal, but has no info as |
---|
| 117 | to the process that caused that situation. |
---|
| 118 | # |
---|
| 119 | [orterun:proc-aborted-strsignal] |
---|
| 120 | %s noticed that process rank %lu with PID %lu on node %s exited on signal %d (%s). |
---|
| 121 | # |
---|
| 122 | [orterun:abnormal-exit] |
---|
| 123 | WARNING: %s has exited before it received notification that all |
---|
| 124 | started processes had terminated. You should double check and ensure |
---|
| 125 | that there are no runaway processes still executing. |
---|
| 126 | # |
---|
| 127 | [orterun:sigint-while-processing] |
---|
| 128 | WARNING: %s is in the process of killing a job, but has detected an |
---|
| 129 | interruption (probably control-C). |
---|
| 130 | |
---|
| 131 | It is dangerous to interrupt %s while it is killing a job (proper |
---|
| 132 | termination may not be guaranteed). Hit control-C again within 1 |
---|
| 133 | second if you really want to kill %s immediately. |
---|
| 134 | # |
---|
| 135 | [orterun:empty-prefix] |
---|
| 136 | A prefix was supplied to %s that only contained slashes. |
---|
| 137 | |
---|
| 138 | This is a fatal error; %s will now abort. No processes were launched. |
---|
| 139 | # |
---|
| 140 | [debugger-mca-param-not-found] |
---|
| 141 | Internal error -- the orte_base_user_debugger MCA parameter was not able to |
---|
| 142 | be found. Please contact the Open RTE developers; this should not |
---|
| 143 | happen. |
---|
| 144 | # |
---|
| 145 | [debugger-orte_base_user_debugger-empty] |
---|
| 146 | The MCA parameter "orte_base_user_debugger" was empty, indicating that |
---|
| 147 | no user-level debuggers have been defined. Please set this MCA |
---|
| 148 | parameter to a value and try again. |
---|
| 149 | # |
---|
| 150 | [debugger-not-found] |
---|
| 151 | A suitable debugger could not be found in your PATH. Check the values |
---|
| 152 | specified in the orte_base_user_debugger MCA parameter for the list of |
---|
| 153 | debuggers that was searched. |
---|
| 154 | # |
---|
| 155 | [debugger-exec-failed] |
---|
| 156 | %s was unable to launch the specified debugger. This is what was |
---|
| 157 | launched: |
---|
| 158 | |
---|
| 159 | %s |
---|
| 160 | |
---|
| 161 | Things to check: |
---|
| 162 | |
---|
| 163 | - Ensure that the debugger is installed properly |
---|
| 164 | - Ensure that the "%s" executable is in your path |
---|
| 165 | - Ensure that any required licenses are available to run the debugger |
---|
| 166 | # |
---|
| 167 | [orterun:sys-limit-pipe] |
---|
| 168 | %s was unable to launch the specified application as it encountered an error: |
---|
| 169 | |
---|
| 170 | Error: system limit exceeded on number of pipes that can be open |
---|
| 171 | Node: %s |
---|
| 172 | |
---|
| 173 | when attempting to start process rank %lu. |
---|
| 174 | |
---|
| 175 | This can be resolved by setting the mca parameter opal_set_max_sys_limits to 1, |
---|
| 176 | increasing your limit descriptor setting (using limit or ulimit commands), |
---|
| 177 | asking the system administrator for that node to increase the system limit, or |
---|
| 178 | by rearranging your processes to place fewer of them on that node. |
---|
| 179 | # |
---|
| 180 | [orterun:sys-limit-sockets] |
---|
| 181 | Error: system limit exceeded on number of network connections that can be open |
---|
| 182 | |
---|
| 183 | This can be resolved by setting the mca parameter opal_set_max_sys_limits to 1, |
---|
| 184 | increasing your limit descriptor setting (using limit or ulimit commands), |
---|
| 185 | or asking the system administrator to increase the system limit. |
---|
| 186 | # |
---|
| 187 | [orterun:pipe-setup-failure] |
---|
| 188 | %s was unable to launch the specified application as it encountered an error: |
---|
| 189 | |
---|
| 190 | Error: pipe function call failed when setting up I/O forwarding subsystem |
---|
| 191 | Node: %s |
---|
| 192 | |
---|
| 193 | while attempting to start process rank %lu. |
---|
| 194 | # |
---|
| 195 | [orterun:sys-limit-children] |
---|
| 196 | %s was unable to launch the specified application as it encountered an error: |
---|
| 197 | |
---|
| 198 | Error: system limit exceeded on number of processes that can be started |
---|
| 199 | Node: %s |
---|
| 200 | |
---|
| 201 | when attempting to start process rank %lu. |
---|
| 202 | |
---|
| 203 | This can be resolved by either asking the system administrator for that node to |
---|
| 204 | increase the system limit, or by rearranging your processes to place fewer of them |
---|
| 205 | on that node. |
---|
| 206 | # |
---|
| 207 | [orterun:failed-term-attrs] |
---|
| 208 | %s was unable to launch the specified application as it encountered an error: |
---|
| 209 | |
---|
| 210 | Error: reading tty attributes function call failed while setting up I/O forwarding system |
---|
| 211 | Node: %s |
---|
| 212 | |
---|
| 213 | while attempting to start process rank %lu. |
---|
| 214 | # |
---|
| 215 | [orterun:wdir-not-found] |
---|
| 216 | %s was unable to launch the specified application as it could not change to the |
---|
| 217 | specified working directory: |
---|
| 218 | |
---|
| 219 | Working directory: %s |
---|
| 220 | Node: %s |
---|
| 221 | |
---|
| 222 | while attempting to start process rank %lu. |
---|
| 223 | # |
---|
| 224 | [orterun:exe-not-found] |
---|
| 225 | %s was unable to launch the specified application as it could not find an executable: |
---|
| 226 | |
---|
| 227 | Executable: %s |
---|
| 228 | Node: %s |
---|
| 229 | |
---|
| 230 | while attempting to start process rank %lu. |
---|
| 231 | # |
---|
| 232 | [orterun:exe-not-accessible] |
---|
| 233 | %s was unable to launch the specified application as it could not access |
---|
| 234 | or execute an executable: |
---|
| 235 | |
---|
| 236 | Executable: %s |
---|
| 237 | Node: %s |
---|
| 238 | |
---|
| 239 | while attempting to start process rank %lu. |
---|
| 240 | # |
---|
| 241 | [orterun:pipe-read-failure] |
---|
| 242 | %s was unable to launch the specified application as it encountered an error: |
---|
| 243 | |
---|
| 244 | Error: reading from a pipe function call failed while spawning a local process |
---|
| 245 | Node: %s |
---|
| 246 | |
---|
| 247 | while attempting to start process rank %lu. |
---|
| 248 | # |
---|
| 249 | [orterun:proc-failed-to-start] |
---|
| 250 | %s was unable to start the specified application as it encountered an error: |
---|
| 251 | |
---|
| 252 | Error name: %s |
---|
| 253 | Node: %s |
---|
| 254 | |
---|
| 255 | when attempting to start process rank %lu. |
---|
| 256 | # |
---|
| 257 | [orterun:proc-failed-to-start-no-status] |
---|
| 258 | %s was unable to start the specified application as it encountered an error |
---|
| 259 | on node %s. More information may be available above. |
---|
| 260 | # |
---|
| 261 | [orterun:proc-failed-to-start-no-status-no-node] |
---|
| 262 | %s was unable to start the specified application as it encountered an error. |
---|
| 263 | More information may be available above. |
---|
| 264 | # |
---|
| 265 | [debugger requires -np] |
---|
| 266 | The number of MPI processes to launch was not specified on the command |
---|
| 267 | line. |
---|
| 268 | |
---|
| 269 | The %s debugger requires that you specify a number of MPI processes to |
---|
| 270 | launch on the command line via the "-np" command line parameter. For |
---|
| 271 | example: |
---|
| 272 | |
---|
| 273 | %s -np 4 %s |
---|
| 274 | |
---|
| 275 | Skipping the %s debugger for now. |
---|
| 276 | # |
---|
| 277 | [debugger requires executable] |
---|
| 278 | The %s debugger requires that you specify an executable on the %s |
---|
| 279 | command line; you cannot specify application context files when |
---|
| 280 | launching this job in the %s debugger. For example: |
---|
| 281 | |
---|
| 282 | %s -np 4 my_mpi_executable |
---|
| 283 | |
---|
| 284 | Skipping the %s debugger for now. |
---|
| 285 | # |
---|
| 286 | [debugger only accepts single app] |
---|
| 287 | The %s debugger only accepts SPMD-style launching; specifying an |
---|
| 288 | MPMD-style launch (with multiple applications separated via ':') is |
---|
| 289 | not permitted. |
---|
| 290 | |
---|
| 291 | Skipping the %s debugger for now. |
---|
| 292 | # |
---|
| 293 | [orterun:daemon-died-during-execution] |
---|
| 294 | %s has detected that a required daemon terminated during execution |
---|
| 295 | of the application with a non-zero status. This is a fatal error. |
---|
| 296 | A best-effort attempt has been made to cleanup. However, it is |
---|
| 297 | -strongly- recommended that you execute the orte-clean utility |
---|
| 298 | to ensure full cleanup is accomplished. |
---|
| 299 | # |
---|
| 300 | [orterun:no-orted-object-exit] |
---|
| 301 | %s was unable to determine the status of the daemons used to |
---|
| 302 | launch this application. Additional manual cleanup may be required. |
---|
| 303 | Please refer to the "orte-clean" tool for assistance. |
---|
| 304 | # |
---|
| 305 | [orterun:unclean-exit] |
---|
| 306 | %s was unable to cleanly terminate the daemons on the nodes shown |
---|
| 307 | below. Additional manual cleanup may be required - please refer to |
---|
| 308 | the "orte-clean" tool for assistance. |
---|
| 309 | # |
---|
| 310 | [orterun:event-def-failed] |
---|
| 311 | %s was unable to define an event required for proper operation of |
---|
| 312 | the system. The reason for this error was: |
---|
| 313 | |
---|
| 314 | Error: %s |
---|
| 315 | |
---|
| 316 | Please report this to the Open MPI mailing list users@open-mpi.org. |
---|
| 317 | # |
---|
| 318 | [orterun:ompi-server-filename-bad] |
---|
| 319 | %s was unable to parse the filename where contact info for the |
---|
| 320 | ompi-server was to be found. The option we were given was: |
---|
| 321 | |
---|
| 322 | --ompi-server %s |
---|
| 323 | |
---|
| 324 | This appears to be missing the required ':' following the |
---|
| 325 | keyword "file". Please remember that the correct format for this |
---|
| 326 | command line option is: |
---|
| 327 | |
---|
| 328 | --ompi-server file:path-to-file |
---|
| 329 | |
---|
| 330 | where path-to-file can be either relative to the cwd or absolute. |
---|
| 331 | # |
---|
| 332 | [orterun:ompi-server-filename-missing] |
---|
| 333 | %s was unable to parse the filename where contact info for the |
---|
| 334 | ompi-server was to be found. The option we were given was: |
---|
| 335 | |
---|
| 336 | --ompi-server %s |
---|
| 337 | |
---|
| 338 | This appears to be missing a filename following the ':'. Please |
---|
| 339 | remember that the correct format for this command line option is: |
---|
| 340 | |
---|
| 341 | --ompi-server file:path-to-file |
---|
| 342 | |
---|
| 343 | where path-to-file can be either relative to the cwd or absolute. |
---|
| 344 | # |
---|
| 345 | [orterun:ompi-server-filename-access] |
---|
| 346 | %s was unable to access the filename where contact info for the |
---|
| 347 | ompi-server was to be found. The option we were given was: |
---|
| 348 | |
---|
| 349 | --ompi-server %s |
---|
| 350 | |
---|
| 351 | Please remember that the correct format for this command line option is: |
---|
| 352 | |
---|
| 353 | --ompi-server file:path-to-file |
---|
| 354 | |
---|
| 355 | where path-to-file can be either relative to the cwd or absolute, and that |
---|
| 356 | you must have read access permissions to that file. |
---|
| 357 | # |
---|
| 358 | [orterun:ompi-server-file-bad] |
---|
| 359 | %s was unable to read the ompi-server's contact info from the |
---|
| 360 | given filename. The filename we were given was: |
---|
| 361 | |
---|
| 362 | FILE: %s |
---|
| 363 | |
---|
| 364 | Please remember that the correct format for this command line option is: |
---|
| 365 | |
---|
| 366 | --ompi-server file:path-to-file |
---|
| 367 | |
---|
| 368 | where path-to-file can be either relative to the cwd or absolute, and that |
---|
| 369 | the file must have a single line in it that contains the Open MPI |
---|
| 370 | uri for the ompi-server. Note that this is *not* a standard uri, but |
---|
| 371 | a special format used internally by Open MPI for communications. It can |
---|
| 372 | best be generated by simply directing the ompi-server to put its |
---|
| 373 | uri in a file, and then giving %s that filename. |
---|
| 374 | [orterun:multiple-hostfiles] |
---|
| 375 | Error: More than one hostfile was passed for a single application context, which |
---|
| 376 | is not supported at this time. |
---|
| 377 | # |
---|
| 378 | [orterun:conflicting-params] |
---|
| 379 | %s has detected multiple instances of an MCA param being specified on |
---|
| 380 | the command line, with conflicting values: |
---|
| 381 | |
---|
| 382 | MCA param: %s |
---|
| 383 | Value 1: %s |
---|
| 384 | Value 2: %s |
---|
| 385 | |
---|
| 386 | This MCA param does not support multiple values, and the system is unable |
---|
| 387 | to identify which value was intended. If this was done in error, please |
---|
| 388 | re-issue the command with only one value. You may wish to review the |
---|
| 389 | output from ompi_info for guidance on accepted values for this param. |
---|
| 390 | |
---|
| 391 | [orterun:server-not-found] |
---|
| 392 | %s was instructed to wait for the requested ompi-server, but was unable to |
---|
| 393 | establish contact with the server during the specified wait time: |
---|
| 394 | |
---|
| 395 | Server uri: %s |
---|
| 396 | Timeout time: %ld |
---|
| 397 | |
---|
| 398 | Error received: %s |
---|
| 399 | |
---|
| 400 | Please check to ensure that the requested server matches the actual server |
---|
| 401 | information, and that the server is in operation. |
---|