2005-03-14 23:57:21 +03:00
|
|
|
/*
|
2007-03-17 02:11:45 +03:00
|
|
|
* Copyright (c) 2004-2007 The Trustees of Indiana University and Indiana
|
2005-11-05 22:57:48 +03:00
|
|
|
* University Research and Technology
|
|
|
|
* Corporation. All rights reserved.
|
2007-06-07 00:24:42 +04:00
|
|
|
* Copyright (c) 2004-2007 The University of Tennessee and The University
|
2005-11-05 22:57:48 +03:00
|
|
|
* of Tennessee Research Foundation. All rights
|
|
|
|
* reserved.
|
2006-11-09 13:16:45 +03:00
|
|
|
* Copyright (c) 2004-2006 High Performance Computing Center Stuttgart,
|
2005-03-14 23:57:21 +03:00
|
|
|
* University of Stuttgart. All rights reserved.
|
2005-03-24 15:43:37 +03:00
|
|
|
* Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
* All rights reserved.
|
2007-04-21 04:15:05 +04:00
|
|
|
* Copyright (c) 2006-2007 Cisco Systems, Inc. All rights reserved.
|
2007-06-05 07:03:59 +04:00
|
|
|
* Copyright (c) 2007 Los Alamos National Security, LLC. All rights
|
|
|
|
* reserved.
|
2005-03-14 23:57:21 +03:00
|
|
|
* $COPYRIGHT$
|
2006-06-08 22:27:17 +04:00
|
|
|
*
|
2005-03-14 23:57:21 +03:00
|
|
|
* Additional copyrights may follow
|
2006-06-08 22:27:17 +04:00
|
|
|
*
|
2005-03-14 23:57:21 +03:00
|
|
|
* $HEADER$
|
|
|
|
*
|
|
|
|
* These symbols are in a file by themselves to provide nice linker
|
|
|
|
* semantics. Since linkers generally pull in symbols by object
|
|
|
|
* files, keeping these symbols as the only symbols in this file
|
|
|
|
* prevents utility programs such as "ompi_info" from having to import
|
|
|
|
* entire components just to query their version and parameters.
|
|
|
|
*/
|
|
|
|
|
2005-05-06 21:00:06 +04:00
|
|
|
#include "orte_config.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "orte/orte_constants.h"
|
2005-09-29 16:35:43 +04:00
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
#include <stdlib.h>
|
2005-06-22 02:48:57 +04:00
|
|
|
#ifdef HAVE_UNISTD_H
|
2005-03-14 23:57:21 +03:00
|
|
|
#include <unistd.h>
|
2005-06-22 02:48:57 +04:00
|
|
|
#endif
|
2005-03-14 23:57:21 +03:00
|
|
|
#include <errno.h>
|
2005-03-29 17:50:15 +04:00
|
|
|
#include <string.h>
|
2007-01-10 21:44:08 +03:00
|
|
|
#ifdef HAVE_STRINGS_H
|
|
|
|
#include <strings.h>
|
|
|
|
#endif
|
2005-09-06 20:10:05 +04:00
|
|
|
#ifdef HAVE_SYS_SELECT_H
|
|
|
|
#include <sys/select.h>
|
|
|
|
#endif
|
|
|
|
#ifdef HAVE_SYS_TIME_H
|
|
|
|
#include <sys/time.h>
|
|
|
|
#endif
|
|
|
|
#ifdef HAVE_SYS_TYPES_H
|
2005-03-14 23:57:21 +03:00
|
|
|
#include <sys/types.h>
|
2005-09-06 20:10:05 +04:00
|
|
|
#endif
|
|
|
|
#ifdef HAVE_SYS_STAT_H
|
2005-03-14 23:57:21 +03:00
|
|
|
#include <sys/stat.h>
|
2005-09-06 20:10:05 +04:00
|
|
|
#endif
|
2005-06-22 02:48:57 +04:00
|
|
|
#ifdef HAVE_SYS_WAIT_H
|
2005-03-14 23:57:21 +03:00
|
|
|
#include <sys/wait.h>
|
2005-06-22 02:48:57 +04:00
|
|
|
#endif
|
2005-03-14 23:57:21 +03:00
|
|
|
#include <fcntl.h>
|
2005-05-19 17:33:28 +04:00
|
|
|
#include <signal.h>
|
2005-08-04 19:09:02 +04:00
|
|
|
#ifdef HAVE_PWD_H
|
|
|
|
#include <pwd.h>
|
|
|
|
#endif
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2007-04-21 04:15:05 +04:00
|
|
|
#include "opal/mca/installdirs/installdirs.h"
|
2005-09-29 16:35:43 +04:00
|
|
|
#include "opal/mca/base/mca_base_param.h"
|
|
|
|
#include "opal/util/if.h"
|
2006-08-23 07:32:36 +04:00
|
|
|
#include "opal/util/os_path.h"
|
2005-09-29 16:35:43 +04:00
|
|
|
#include "opal/util/path.h"
|
|
|
|
#include "opal/event/event.h"
|
|
|
|
#include "opal/util/show_help.h"
|
|
|
|
#include "opal/util/argv.h"
|
|
|
|
#include "opal/util/opal_environ.h"
|
|
|
|
#include "opal/util/output.h"
|
2006-10-02 22:29:15 +04:00
|
|
|
#include "opal/util/trace.h"
|
2006-05-16 18:14:12 +04:00
|
|
|
#include "opal/util/basename.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
|
|
|
|
#include "orte/util/sys_info.h"
|
2005-07-28 17:00:32 +04:00
|
|
|
#include "orte/util/univ_info.h"
|
|
|
|
#include "orte/util/session_dir.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2005-07-28 17:00:32 +04:00
|
|
|
#include "orte/runtime/orte_wait.h"
|
2007-04-26 19:07:40 +04:00
|
|
|
#include "orte/runtime/orte_wakeup.h"
|
Bring in the generalized xcast communication system along with the correspondingly revised orted launch. I will send a message out to developers explaining the basic changes. In brief:
1. generalize orte_rml.xcast to become a general broadcast-like messaging system. Messages can now be sent to any tag on the daemons or processes. Note that any message sent via xcast will be delivered to ALL processes in the specified job - you don't get to pick and choose. At a later date, we will introduce an augmented capability that will use the daemons as relays, but will allow you to send to a specified array of process names.
2. extended orte_rml.xcast so it supports more scalable message routing methodologies. At the moment, we support three: (a) direct, which sends the message directly to all recipients; (b) linear, which sends the message to the local daemon on each node, which then relays it to its own local procs; and (b) binomial, which sends the message via a binomial algo across all the daemons, each of which then relays to its own local procs. The crossover points between the algos are adjustable via MCA param, or you can simply demand that a specific algo be used.
3. orteds no longer exhibit two types of behavior: bootproxy or VM. Orteds now always behave like they are part of a virtual machine - they simply launch a job if mpirun tells them to do so. This is another step towards creating an "orteboot" functionality, but also provided a clean system for supporting message relaying.
Note one major impact of this commit: multiple daemons on a node cannot be supported any longer! Only a single daemon/node is now allowed.
This commit is known to break support for the following environments: POE, Xgrid, Xcpu, Windows. It has been tested on rsh, SLURM, and Bproc. Modifications for TM support have been made but could not be verified due to machine problems at LANL. Modifications for SGE have been made but could not be verified. The developers for the non-verified environments will be separately notified along with suggestions on how to fix the problems.
This commit was SVN r15007.
2007-06-12 17:28:54 +04:00
|
|
|
#include "orte/runtime/params.h"
|
2006-10-03 21:40:00 +04:00
|
|
|
#include "orte/dss/dss.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2005-07-28 17:00:32 +04:00
|
|
|
#include "orte/mca/ns/ns.h"
|
|
|
|
#include "orte/mca/rml/rml.h"
|
|
|
|
#include "orte/mca/gpr/gpr.h"
|
|
|
|
#include "orte/mca/errmgr/errmgr.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "orte/mca/ras/ras_types.h"
|
2006-10-07 19:45:24 +04:00
|
|
|
#include "orte/mca/rmaps/rmaps.h"
|
2006-08-16 20:35:09 +04:00
|
|
|
#include "orte/mca/smr/smr.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
|
|
|
|
#include "orte/mca/pls/pls.h"
|
2006-11-16 00:12:27 +03:00
|
|
|
#include "orte/mca/pls/base/base.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "orte/mca/pls/base/pls_private.h"
|
2005-07-28 17:00:32 +04:00
|
|
|
#include "orte/mca/pls/rsh/pls_rsh.h"
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2005-03-24 18:45:44 +03:00
|
|
|
#if OMPI_HAVE_POSIX_THREADS && OMPI_THREADS_HAVE_DIFFERENT_PIDS && OMPI_ENABLE_PROGRESS_THREADS
|
2005-03-14 23:57:21 +03:00
|
|
|
static int orte_pls_rsh_launch_threaded(orte_jobid_t jobid);
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
orte_pls_base_module_t orte_pls_rsh_module = {
|
2005-03-24 18:45:44 +03:00
|
|
|
#if OMPI_HAVE_POSIX_THREADS && OMPI_THREADS_HAVE_DIFFERENT_PIDS && OMPI_ENABLE_PROGRESS_THREADS
|
2005-03-14 23:57:21 +03:00
|
|
|
orte_pls_rsh_launch_threaded,
|
|
|
|
#else
|
|
|
|
orte_pls_rsh_launch,
|
|
|
|
#endif
|
|
|
|
orte_pls_rsh_terminate_job,
|
2006-09-15 01:29:51 +04:00
|
|
|
orte_pls_rsh_terminate_orteds,
|
2005-03-14 23:57:21 +03:00
|
|
|
orte_pls_rsh_terminate_proc,
|
2006-06-08 22:27:17 +04:00
|
|
|
orte_pls_rsh_signal_job,
|
|
|
|
orte_pls_rsh_signal_proc,
|
2005-03-14 23:57:21 +03:00
|
|
|
orte_pls_rsh_finalize
|
|
|
|
};
|
|
|
|
|
2007-06-21 15:40:42 +04:00
|
|
|
typedef enum {
|
2005-09-06 20:10:05 +04:00
|
|
|
ORTE_PLS_RSH_SHELL_BASH = 0,
|
2007-03-03 04:42:03 +03:00
|
|
|
ORTE_PLS_RSH_SHELL_ZSH,
|
2005-09-06 20:10:05 +04:00
|
|
|
ORTE_PLS_RSH_SHELL_TCSH,
|
|
|
|
ORTE_PLS_RSH_SHELL_CSH,
|
|
|
|
ORTE_PLS_RSH_SHELL_KSH,
|
2006-11-09 13:16:45 +03:00
|
|
|
ORTE_PLS_RSH_SHELL_SH,
|
2005-09-06 20:10:05 +04:00
|
|
|
ORTE_PLS_RSH_SHELL_UNKNOWN
|
2007-06-21 15:40:42 +04:00
|
|
|
} orte_pls_rsh_shell_t;
|
2005-09-06 20:10:05 +04:00
|
|
|
|
2007-06-21 15:40:42 +04:00
|
|
|
/* These strings *must* follow the same order as the enum
|
|
|
|
ORTE_PLS_RSH_SHELL_* */
|
2005-09-06 20:10:05 +04:00
|
|
|
static const char * orte_pls_rsh_shell_name[] = {
|
|
|
|
"bash",
|
2007-03-03 04:42:03 +03:00
|
|
|
"zsh",
|
2005-09-06 20:10:05 +04:00
|
|
|
"tcsh", /* tcsh has to be first otherwise strstr finds csh */
|
|
|
|
"csh",
|
|
|
|
"ksh",
|
2007-06-07 00:24:42 +04:00
|
|
|
"sh",
|
|
|
|
"unknown"
|
2005-09-06 20:10:05 +04:00
|
|
|
};
|
|
|
|
|
2007-06-21 15:40:42 +04:00
|
|
|
/*
|
|
|
|
* Local functions
|
|
|
|
*/
|
|
|
|
static void set_handler_default(int sig);
|
|
|
|
static orte_pls_rsh_shell_t find_shell(char *shell);
|
|
|
|
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
/* local global storage of timing variables */
|
|
|
|
static struct timeval joblaunchstart, joblaunchstop;
|
|
|
|
|
2007-04-26 19:07:40 +04:00
|
|
|
/* global storage of active jobid being launched */
|
|
|
|
static orte_jobid_t active_job=ORTE_JOBID_INVALID;
|
2006-10-07 19:45:24 +04:00
|
|
|
|
|
|
|
|
2005-09-06 20:10:05 +04:00
|
|
|
/**
|
|
|
|
* Check the Shell variable on the specified node
|
|
|
|
*/
|
|
|
|
|
2007-06-21 15:40:42 +04:00
|
|
|
static int orte_pls_rsh_probe(orte_mapped_node_t *node,
|
|
|
|
orte_pls_rsh_shell_t *shell)
|
2005-09-06 20:10:05 +04:00
|
|
|
{
|
|
|
|
char ** argv;
|
2007-04-06 00:17:10 +04:00
|
|
|
int argc, rc = ORTE_SUCCESS, i;
|
2005-09-06 20:10:05 +04:00
|
|
|
int fd[2];
|
|
|
|
pid_t pid;
|
|
|
|
char outbuf[4096];
|
|
|
|
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: going to check SHELL variable on node %s\n",
|
2006-10-07 19:45:24 +04:00
|
|
|
node->nodename);
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
|
|
|
*shell = ORTE_PLS_RSH_SHELL_UNKNOWN;
|
|
|
|
if (pipe(fd)) {
|
|
|
|
opal_output(0, "pls:rsh: pipe failed with errno=%d\n", errno);
|
|
|
|
return ORTE_ERR_IN_ERRNO;
|
|
|
|
}
|
|
|
|
if ((pid = fork()) < 0) {
|
|
|
|
opal_output(0, "pls:rsh: fork failed with errno=%d\n", errno);
|
|
|
|
return ORTE_ERR_IN_ERRNO;
|
|
|
|
}
|
|
|
|
else if (pid == 0) { /* child */
|
|
|
|
if (dup2(fd[1], 1) < 0) {
|
|
|
|
opal_output(0, "pls:rsh: dup2 failed with errno=%d\n", errno);
|
2007-04-14 21:36:27 +04:00
|
|
|
exit(01);
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
2007-04-05 23:22:26 +04:00
|
|
|
/* Build argv array */
|
|
|
|
argv = opal_argv_copy(mca_pls_rsh_component.agent_argv);
|
|
|
|
argc = mca_pls_rsh_component.agent_argc;
|
|
|
|
opal_argv_append(&argc, &argv, node->nodename);
|
|
|
|
opal_argv_append(&argc, &argv, "echo $SHELL");
|
|
|
|
|
2005-09-06 20:10:05 +04:00
|
|
|
execvp(argv[0], argv);
|
|
|
|
exit(errno);
|
|
|
|
}
|
|
|
|
if (close(fd[1])) {
|
|
|
|
opal_output(0, "pls:rsh: close failed with errno=%d\n", errno);
|
|
|
|
return ORTE_ERR_IN_ERRNO;
|
|
|
|
}
|
2007-04-05 23:22:26 +04:00
|
|
|
|
|
|
|
{
|
|
|
|
ssize_t ret = 1;
|
|
|
|
char* ptr = outbuf;
|
|
|
|
size_t outbufsize = sizeof(outbuf);
|
2007-04-06 00:17:10 +04:00
|
|
|
|
2007-04-05 23:22:26 +04:00
|
|
|
do {
|
|
|
|
ret = read (fd[0], ptr, outbufsize-1);
|
|
|
|
if (ret < 0) {
|
|
|
|
if (errno == EINTR)
|
|
|
|
continue;
|
2007-04-06 00:17:10 +04:00
|
|
|
opal_output( 0, "Unable to detect the remote shell (error %s)\n",
|
|
|
|
strerror(errno) );
|
2005-09-06 20:10:05 +04:00
|
|
|
rc = ORTE_ERR_IN_ERRNO;
|
|
|
|
break;
|
|
|
|
}
|
2007-04-05 23:22:26 +04:00
|
|
|
if( outbufsize > 1 ) {
|
|
|
|
outbufsize -= ret;
|
|
|
|
ptr += ret;
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
2007-04-05 23:22:26 +04:00
|
|
|
} while( 0 != ret );
|
|
|
|
*ptr = '\0';
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
2007-04-05 23:22:26 +04:00
|
|
|
close(fd[0]);
|
2005-09-06 20:10:05 +04:00
|
|
|
|
2007-04-05 23:22:26 +04:00
|
|
|
if( outbuf[0] != '\0' ) {
|
|
|
|
char *sh_name = rindex(outbuf, '/');
|
|
|
|
if( NULL != sh_name ) {
|
2006-11-09 13:16:45 +03:00
|
|
|
sh_name++; /* skip '/' */
|
|
|
|
/* We cannot use "echo -n $SHELL" because -n is not portable. Therefore
|
|
|
|
* we have to remove the "\n" */
|
|
|
|
if ( sh_name[strlen(sh_name)-1] == '\n' ) {
|
|
|
|
sh_name[strlen(sh_name)-1] = '\0';
|
|
|
|
}
|
2007-04-05 23:22:26 +04:00
|
|
|
/* Search for the substring of known shell-names */
|
|
|
|
for (i = 0; i < (int)(sizeof (orte_pls_rsh_shell_name)/
|
|
|
|
sizeof(orte_pls_rsh_shell_name[0])); i++) {
|
|
|
|
if ( 0 == strcmp(sh_name, orte_pls_rsh_shell_name[i]) ) {
|
|
|
|
*shell = i;
|
|
|
|
break;
|
|
|
|
}
|
2006-11-09 13:16:45 +03:00
|
|
|
}
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
2007-06-13 02:40:44 +04:00
|
|
|
if( ORTE_PLS_RSH_SHELL_UNKNOWN == *shell ) {
|
2007-06-13 03:22:09 +04:00
|
|
|
opal_output(0, "pls:rsh: node:%s has unhandled SHELL\n",
|
|
|
|
node->nodename);
|
2007-06-13 02:40:44 +04:00
|
|
|
} else {
|
|
|
|
opal_output(0, "pls:rsh: node:%s has SHELL: %s\n",
|
|
|
|
node->nodename, orte_pls_rsh_shell_name[*shell]);
|
|
|
|
}
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Fill the exec_path variable with the directory to the orted
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int orte_pls_rsh_fill_exec_path ( char ** exec_path)
|
|
|
|
{
|
|
|
|
struct stat buf;
|
|
|
|
|
2007-04-21 04:15:05 +04:00
|
|
|
asprintf(exec_path, "%s/orted", opal_install_dirs.bindir);
|
2005-09-06 20:10:05 +04:00
|
|
|
if (0 != stat(*exec_path, &buf)) {
|
|
|
|
char *path = getenv("PATH");
|
|
|
|
if (NULL == path) {
|
|
|
|
path = ("PATH is empty!");
|
|
|
|
}
|
|
|
|
opal_show_help("help-pls-rsh.txt", "no-local-orted",
|
2007-04-21 04:15:05 +04:00
|
|
|
true, path, opal_install_dirs.bindir);
|
2005-09-06 20:10:05 +04:00
|
|
|
return ORTE_ERR_NOT_FOUND;
|
|
|
|
}
|
|
|
|
return ORTE_SUCCESS;
|
|
|
|
}
|
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
/**
|
|
|
|
* Callback on daemon exit.
|
|
|
|
*/
|
|
|
|
|
|
|
|
static void orte_pls_rsh_wait_daemon(pid_t pid, int status, void* cbdata)
|
|
|
|
{
|
2005-03-19 02:58:36 +03:00
|
|
|
int rc;
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
unsigned long deltat;
|
2007-07-12 23:53:18 +04:00
|
|
|
orte_buffer_t ack;
|
|
|
|
int src[3] = {-1, -1};
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2005-03-31 08:23:55 +04:00
|
|
|
if (! WIFEXITED(status) || ! WEXITSTATUS(status) == 0) {
|
|
|
|
/* tell the user something went wrong */
|
2007-04-26 19:07:40 +04:00
|
|
|
opal_output(0, "ERROR: A daemon failed to start as expected.");
|
2005-07-04 03:31:27 +04:00
|
|
|
opal_output(0, "ERROR: There may be more information available from");
|
|
|
|
opal_output(0, "ERROR: the remote shell (see above).");
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2005-03-19 02:58:36 +03:00
|
|
|
if (WIFEXITED(status)) {
|
2005-07-04 03:31:27 +04:00
|
|
|
opal_output(0, "ERROR: The daemon exited unexpectedly with status %d.",
|
2007-04-26 19:07:40 +04:00
|
|
|
WEXITSTATUS(status));
|
2005-03-19 02:58:36 +03:00
|
|
|
} else if (WIFSIGNALED(status)) {
|
|
|
|
#ifdef WCOREDUMP
|
|
|
|
if (WCOREDUMP(status)) {
|
2005-07-04 03:31:27 +04:00
|
|
|
opal_output(0, "The daemon received a signal %d (with core).",
|
2005-09-05 00:55:27 +04:00
|
|
|
WTERMSIG(status));
|
2005-04-13 02:13:55 +04:00
|
|
|
} else {
|
2005-09-05 00:55:27 +04:00
|
|
|
opal_output(0, "The daemon received a signal %d.", WTERMSIG(status));
|
2005-03-19 02:58:36 +03:00
|
|
|
}
|
2005-04-13 02:13:55 +04:00
|
|
|
#else
|
2005-09-05 00:55:27 +04:00
|
|
|
opal_output(0, "The daemon received a signal %d.", WTERMSIG(status));
|
2005-03-19 02:58:36 +03:00
|
|
|
#endif /* WCOREDUMP */
|
|
|
|
} else {
|
2005-07-04 03:31:27 +04:00
|
|
|
opal_output(0, "No extra status information is available: %d.", status);
|
2005-03-19 02:58:36 +03:00
|
|
|
}
|
2007-07-12 23:53:18 +04:00
|
|
|
/* need to fake a message to the daemon callback system so it can break out
|
|
|
|
* of its receive loop
|
|
|
|
*/
|
|
|
|
src[2] = pid;
|
|
|
|
if(WIFSIGNALED(status)) {
|
|
|
|
src[1] = WTERMSIG(status);
|
|
|
|
}
|
|
|
|
OBJ_CONSTRUCT(&ack, orte_buffer_t);
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_dss.pack(&ack, &src, 3, ORTE_INT))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
rc = orte_rml.send_buffer(ORTE_PROC_MY_NAME, &ack, ORTE_RML_TAG_ORTED_CALLBACK, 0);
|
|
|
|
if (0 > rc) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
OBJ_DESTRUCT(&ack);
|
|
|
|
|
2007-04-26 19:07:40 +04:00
|
|
|
/* The usual reasons for ssh to exit abnormally all are a pretty good
|
|
|
|
indication that the child processes aren't going to start up properly.
|
|
|
|
Set the job state to indicate we failed to launch so orterun's exit status
|
|
|
|
will be non-zero and forcibly terminate the job so orterun can exit
|
|
|
|
*/
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_smr.set_job_state(active_job, ORTE_JOB_STATE_FAILED_TO_START))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_wakeup(active_job))) {
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
} /* if abnormal exit */
|
2005-03-19 02:58:36 +03:00
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
/* release any waiting threads */
|
2005-07-04 02:45:48 +04:00
|
|
|
OPAL_THREAD_LOCK(&mca_pls_rsh_component.lock);
|
2006-10-07 19:45:24 +04:00
|
|
|
|
2005-09-05 00:55:27 +04:00
|
|
|
if (mca_pls_rsh_component.num_children-- >=
|
2005-08-04 19:09:02 +04:00
|
|
|
mca_pls_rsh_component.num_concurrent ||
|
|
|
|
mca_pls_rsh_component.num_children == 0) {
|
2005-07-04 02:45:48 +04:00
|
|
|
opal_condition_signal(&mca_pls_rsh_component.cond);
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
|
|
|
if (mca_pls_rsh_component.timing && mca_pls_rsh_component.num_children == 0) {
|
|
|
|
if (0 != gettimeofday(&joblaunchstop, NULL)) {
|
|
|
|
opal_output(0, "pls_rsh: could not obtain job launch stop time");
|
|
|
|
} else {
|
|
|
|
deltat = (joblaunchstop.tv_sec - joblaunchstart.tv_sec)*1000000 +
|
2007-04-26 19:07:40 +04:00
|
|
|
(joblaunchstop.tv_usec - joblaunchstart.tv_usec);
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
opal_output(0, "pls_rsh: total time to launch job is %lu usec", deltat);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2005-07-04 02:45:48 +04:00
|
|
|
OPAL_THREAD_UNLOCK(&mca_pls_rsh_component.lock);
|
2005-03-19 02:58:36 +03:00
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
2005-03-31 19:47:37 +04:00
|
|
|
/**
|
|
|
|
* Launch a daemon (bootproxy) on each node. The daemon will be responsible
|
|
|
|
* for launching the application.
|
|
|
|
*/
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2007-04-26 19:07:40 +04:00
|
|
|
/* When working in this function, ALWAYS jump to "cleanup" if
|
|
|
|
* you encounter an error so that orterun will be woken up and
|
|
|
|
* the job can cleanly terminate
|
|
|
|
*/
|
2005-03-14 23:57:21 +03:00
|
|
|
int orte_pls_rsh_launch(orte_jobid_t jobid)
|
|
|
|
{
|
2007-04-26 19:07:40 +04:00
|
|
|
orte_job_map_t *map=NULL;
|
2006-10-07 19:45:24 +04:00
|
|
|
opal_list_item_t *n_item;
|
|
|
|
orte_mapped_node_t *rmaps_node;
|
2005-03-18 06:43:59 +03:00
|
|
|
int node_name_index1;
|
|
|
|
int node_name_index2;
|
2005-03-14 23:57:21 +03:00
|
|
|
int proc_name_index;
|
2005-08-04 19:09:02 +04:00
|
|
|
int local_exec_index, local_exec_index_end;
|
2006-11-16 00:12:27 +03:00
|
|
|
char *jobid_string = NULL;
|
2007-04-11 21:15:14 +04:00
|
|
|
char *param;
|
2007-04-05 23:22:26 +04:00
|
|
|
char **argv = NULL;
|
2006-10-07 19:45:24 +04:00
|
|
|
char *prefix_dir;
|
2005-03-14 23:57:21 +03:00
|
|
|
int argc;
|
|
|
|
int rc;
|
2005-05-19 17:33:28 +04:00
|
|
|
sigset_t sigs;
|
2005-08-04 19:09:02 +04:00
|
|
|
struct passwd *p;
|
2006-11-09 13:16:45 +03:00
|
|
|
bool remote_sh = false, remote_csh = false;
|
|
|
|
bool local_sh = false, local_csh = false;
|
2006-05-16 18:14:12 +04:00
|
|
|
char *lib_base = NULL, *bin_base = NULL;
|
2007-04-26 19:07:40 +04:00
|
|
|
bool failed_launch = true;
|
2007-06-21 15:40:42 +04:00
|
|
|
orte_pls_rsh_shell_t shell;
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
2007-07-12 23:53:18 +04:00
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: launching job %ld", (long)jobid);
|
|
|
|
}
|
|
|
|
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
if (mca_pls_rsh_component.timing) {
|
|
|
|
if (0 != gettimeofday(&joblaunchstart, NULL)) {
|
|
|
|
opal_output(0, "pls_rsh: could not obtain start time");
|
|
|
|
joblaunchstart.tv_sec = 0;
|
|
|
|
joblaunchstart.tv_usec = 0;
|
|
|
|
}
|
|
|
|
}
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2007-04-26 19:07:40 +04:00
|
|
|
/* set the active jobid */
|
|
|
|
active_job = jobid;
|
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* Get the map for this job
|
2005-10-08 02:24:52 +04:00
|
|
|
* We need the entire mapping for a couple of reasons:
|
|
|
|
* - need the prefix to start with.
|
2006-10-07 19:45:24 +04:00
|
|
|
* - need to know the nodes we are launching on
|
2005-10-08 02:24:52 +04:00
|
|
|
* All other mapping responsibilities fall to orted in the fork PLS
|
2005-03-14 23:57:21 +03:00
|
|
|
*/
|
2006-10-07 19:45:24 +04:00
|
|
|
rc = orte_rmaps.get_job_map(&map, jobid);
|
2005-08-04 19:09:02 +04:00
|
|
|
if (ORTE_SUCCESS != rc) {
|
2006-11-16 18:11:45 +03:00
|
|
|
ORTE_ERROR_LOG(rc);
|
2007-04-26 19:07:40 +04:00
|
|
|
goto cleanup;
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
2007-07-12 23:53:18 +04:00
|
|
|
if (0 == map->num_new_daemons) {
|
|
|
|
/* have all the daemons we need - launch app */
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: no new daemons to launch");
|
|
|
|
}
|
|
|
|
goto launch_apps;
|
2006-11-16 00:12:27 +03:00
|
|
|
}
|
2007-06-12 18:23:33 +04:00
|
|
|
|
2006-10-24 19:59:02 +04:00
|
|
|
if (mca_pls_rsh_component.debug_daemons &&
|
2007-07-12 23:53:18 +04:00
|
|
|
mca_pls_rsh_component.num_concurrent < map->num_new_daemons) {
|
2007-04-06 00:36:33 +04:00
|
|
|
/**
|
|
|
|
* If we are in '--debug-daemons' we keep the ssh connection
|
|
|
|
* alive for the span of the run. If we use this option
|
|
|
|
* AND we launch on more than "num_concurrent" machines
|
|
|
|
* then we will deadlock. No connections are terminated
|
|
|
|
* until the job is complete, no job is started
|
|
|
|
* since all the orteds are waiting for all the others
|
|
|
|
* to come online, and the others ore not launched because
|
|
|
|
* we are waiting on those that have started to terminate
|
|
|
|
* their ssh tunnels. :(
|
|
|
|
* As we cannot run in this situation, pretty print the error
|
|
|
|
* and return an error code.
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
*/
|
2006-10-24 19:59:02 +04:00
|
|
|
opal_show_help("help-pls-rsh.txt", "deadlock-params",
|
2007-07-12 23:53:18 +04:00
|
|
|
true, mca_pls_rsh_component.num_concurrent, map->num_new_daemons);
|
2007-04-26 19:07:40 +04:00
|
|
|
rc = ORTE_ERR_FATAL;
|
|
|
|
goto cleanup;
|
2006-10-24 19:59:02 +04:00
|
|
|
}
|
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/*
|
|
|
|
* After a discussion between Ralph & Jeff, we concluded that we
|
|
|
|
* really are handling the prefix dir option incorrectly. It currently
|
|
|
|
* is associated with an app_context, yet it really refers to the
|
|
|
|
* location where OpenRTE/Open MPI is installed on a NODE. Fixing
|
|
|
|
* this right now would involve significant change to orterun as well
|
|
|
|
* as elsewhere, so we will intentionally leave this incorrect at this
|
|
|
|
* point. The error, however, is identical to that seen in all prior
|
|
|
|
* releases of OpenRTE/Open MPI, so our behavior is no worse than before.
|
|
|
|
*
|
|
|
|
* A note to fix this, along with ideas on how to do so, has been filed
|
|
|
|
* on the project's Trac system under "feature enhancement".
|
|
|
|
*
|
|
|
|
* For now, default to the prefix_dir provided in the first app_context.
|
|
|
|
* Since there always MUST be at least one app_context, we are safe in
|
|
|
|
* doing this.
|
|
|
|
*/
|
|
|
|
prefix_dir = map->apps[0]->prefix_dir;
|
|
|
|
|
2005-08-04 19:09:02 +04:00
|
|
|
/* What is our local shell? */
|
|
|
|
p = getpwuid(getuid());
|
2007-04-05 23:22:26 +04:00
|
|
|
if( NULL == p ) {
|
|
|
|
/* This user is unknown to the system. Therefore, there is no reason we
|
|
|
|
* spawn whatsoever in his name. Give up with a HUGE error message.
|
|
|
|
*/
|
|
|
|
opal_show_help( "help-pls-rsh.txt", "unknown-user", true, (int)getuid() );
|
|
|
|
rc = ORTE_ERR_FATAL;
|
|
|
|
goto cleanup;
|
2007-06-13 02:40:44 +04:00
|
|
|
} else {
|
2007-06-21 15:40:42 +04:00
|
|
|
param = p->pw_shell;
|
|
|
|
shell = find_shell(p->pw_shell);
|
|
|
|
}
|
|
|
|
/* If we didn't find it in getpwuid(), try looking at the $SHELL
|
|
|
|
environment variable (see
|
|
|
|
https://svn.open-mpi.org/trac/ompi/ticket/1060) */
|
|
|
|
if (ORTE_PLS_RSH_SHELL_UNKNOWN == shell &&
|
|
|
|
NULL != (param = getenv("SHELL"))) {
|
|
|
|
shell = find_shell(param);
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (shell) {
|
|
|
|
case ORTE_PLS_RSH_SHELL_SH: /* fall through */
|
|
|
|
case ORTE_PLS_RSH_SHELL_KSH: /* fall through */
|
|
|
|
case ORTE_PLS_RSH_SHELL_ZSH: /* fall through */
|
|
|
|
case ORTE_PLS_RSH_SHELL_BASH: local_sh = true; break;
|
|
|
|
case ORTE_PLS_RSH_SHELL_TCSH: /* fall through */
|
|
|
|
case ORTE_PLS_RSH_SHELL_CSH: local_csh = true; break;
|
|
|
|
default:
|
|
|
|
opal_output(0, "WARNING: local probe returned unhandled shell:%s assuming bash\n",
|
|
|
|
(NULL != param) ? param : "unknown");
|
|
|
|
remote_sh = true;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: local csh: %d, local sh: %d\n",
|
|
|
|
local_csh, local_sh);
|
2005-08-04 19:09:02 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/* What is our remote shell? */
|
|
|
|
if (mca_pls_rsh_component.assume_same_shell) {
|
2006-11-09 13:16:45 +03:00
|
|
|
remote_sh = local_sh;
|
2005-08-04 19:09:02 +04:00
|
|
|
remote_csh = local_csh;
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: assuming same remote shell as local shell");
|
|
|
|
}
|
|
|
|
} else {
|
2007-06-21 15:40:42 +04:00
|
|
|
orte_pls_rsh_shell_t shell;
|
2006-10-07 19:45:24 +04:00
|
|
|
rmaps_node = (orte_mapped_node_t*)opal_list_get_first(&map->nodes);
|
|
|
|
rc = orte_pls_rsh_probe(rmaps_node, &shell);
|
2005-09-06 20:10:05 +04:00
|
|
|
|
|
|
|
if (ORTE_SUCCESS != rc) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
2007-04-26 19:07:40 +04:00
|
|
|
goto cleanup;
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
switch (shell) {
|
2006-11-09 13:16:45 +03:00
|
|
|
case ORTE_PLS_RSH_SHELL_SH: /* fall through */
|
2005-09-06 20:10:05 +04:00
|
|
|
case ORTE_PLS_RSH_SHELL_KSH: /* fall through */
|
2007-06-21 15:40:42 +04:00
|
|
|
case ORTE_PLS_RSH_SHELL_ZSH: /* fall through */
|
2006-11-09 13:16:45 +03:00
|
|
|
case ORTE_PLS_RSH_SHELL_BASH: remote_sh = true; break;
|
2005-09-06 20:10:05 +04:00
|
|
|
case ORTE_PLS_RSH_SHELL_TCSH: /* fall through */
|
|
|
|
case ORTE_PLS_RSH_SHELL_CSH: remote_csh = true; break;
|
|
|
|
default:
|
2007-06-21 15:40:42 +04:00
|
|
|
opal_output(0, "WARNING: rsh probe returned unhandled shell; assuming bash\n");
|
2006-11-09 13:16:45 +03:00
|
|
|
remote_sh = true;
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
2005-08-04 19:09:02 +04:00
|
|
|
}
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
2006-11-09 13:16:45 +03:00
|
|
|
opal_output(0, "pls:rsh: remote csh: %d, remote sh: %d\n",
|
|
|
|
remote_csh, remote_sh);
|
2005-08-04 19:09:02 +04:00
|
|
|
}
|
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
/*
|
2005-05-13 01:44:23 +04:00
|
|
|
* Build argv array
|
2005-03-14 23:57:21 +03:00
|
|
|
*/
|
2005-12-22 17:37:19 +03:00
|
|
|
argv = opal_argv_copy(mca_pls_rsh_component.agent_argv);
|
|
|
|
argc = mca_pls_rsh_component.agent_argc;
|
2005-03-18 06:43:59 +03:00
|
|
|
node_name_index1 = argc;
|
2005-09-29 16:35:43 +04:00
|
|
|
opal_argv_append(&argc, &argv, "<template>");
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2005-05-13 01:44:23 +04:00
|
|
|
/* add the daemon command (as specified by user) */
|
2005-05-12 23:12:53 +04:00
|
|
|
local_exec_index = argc;
|
2005-07-04 04:13:44 +04:00
|
|
|
opal_argv_append(&argc, &argv, mca_pls_rsh_component.orted);
|
2005-09-05 00:55:27 +04:00
|
|
|
|
2007-04-10 18:23:32 +04:00
|
|
|
/*
|
2007-07-12 23:53:18 +04:00
|
|
|
* Add the basic arguments to the orted command line, including
|
|
|
|
* all debug options
|
2007-04-10 18:23:32 +04:00
|
|
|
*/
|
|
|
|
orte_pls_base_orted_append_basic_args(&argc, &argv,
|
|
|
|
&proc_name_index,
|
|
|
|
&node_name_index2,
|
2007-06-12 18:23:33 +04:00
|
|
|
map->num_nodes);
|
2007-04-10 18:23:32 +04:00
|
|
|
|
2005-08-04 19:09:02 +04:00
|
|
|
local_exec_index_end = argc;
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
param = opal_argv_join(argv, ' ');
|
|
|
|
if (NULL != param) {
|
2005-09-29 16:35:43 +04:00
|
|
|
opal_output(0, "pls:rsh: final template argv:");
|
2005-08-04 19:09:02 +04:00
|
|
|
opal_output(0, "pls:rsh: %s", param);
|
|
|
|
free(param);
|
|
|
|
}
|
|
|
|
}
|
2007-07-12 23:53:18 +04:00
|
|
|
|
2006-05-16 18:14:12 +04:00
|
|
|
/* Figure out the basenames for the libdir and bindir. This
|
|
|
|
requires some explanation:
|
|
|
|
|
2007-04-21 04:15:05 +04:00
|
|
|
- Use opal_install_dirs.libdir and opal_install_dirs.bindir.
|
2006-05-16 18:14:12 +04:00
|
|
|
|
|
|
|
- After a discussion on the devel-core mailing list, the
|
2007-04-05 23:22:26 +04:00
|
|
|
developers decided that we should use the local directory
|
|
|
|
basenames as the basis for the prefix on the remote note.
|
|
|
|
This does not handle a few notable cases (e.g., if the
|
|
|
|
libdir/bindir is not simply a subdir under the prefix, if the
|
|
|
|
libdir/bindir basename is not the same on the remote node as
|
|
|
|
it is here on the local node, etc.), but we decided that
|
|
|
|
--prefix was meant to handle "the common case". If you need
|
|
|
|
something more complex than this, a) edit your shell startup
|
|
|
|
files to set PATH/LD_LIBRARY_PATH properly on the remove
|
|
|
|
node, or b) use some new/to-be-defined options that
|
|
|
|
explicitly allow setting the bindir/libdir on the remote
|
|
|
|
node. We decided to implement these options (e.g.,
|
|
|
|
--remote-bindir and --remote-libdir) to orterun when it
|
|
|
|
actually becomes a problem for someone (vs. a hypothetical
|
|
|
|
situation).
|
2006-05-16 18:14:12 +04:00
|
|
|
|
|
|
|
Hence, for now, we simply take the basename of this install's
|
|
|
|
libdir and bindir and use it to append this install's prefix
|
|
|
|
and use that on the remote node.
|
|
|
|
*/
|
|
|
|
|
2007-04-21 04:15:05 +04:00
|
|
|
lib_base = opal_basename(opal_install_dirs.libdir);
|
|
|
|
bin_base = opal_basename(opal_install_dirs.bindir);
|
2006-05-16 18:14:12 +04:00
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
/*
|
2006-10-07 19:45:24 +04:00
|
|
|
* Iterate through each of the nodes
|
2005-03-14 23:57:21 +03:00
|
|
|
*/
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
for(n_item = opal_list_get_first(&map->nodes);
|
|
|
|
n_item != opal_list_get_end(&map->nodes);
|
|
|
|
n_item = opal_list_get_next(n_item)) {
|
|
|
|
pid_t pid;
|
|
|
|
char *exec_path;
|
|
|
|
char **exec_argv;
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
rmaps_node = (orte_mapped_node_t*)n_item;
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
Bring in the generalized xcast communication system along with the correspondingly revised orted launch. I will send a message out to developers explaining the basic changes. In brief:
1. generalize orte_rml.xcast to become a general broadcast-like messaging system. Messages can now be sent to any tag on the daemons or processes. Note that any message sent via xcast will be delivered to ALL processes in the specified job - you don't get to pick and choose. At a later date, we will introduce an augmented capability that will use the daemons as relays, but will allow you to send to a specified array of process names.
2. extended orte_rml.xcast so it supports more scalable message routing methodologies. At the moment, we support three: (a) direct, which sends the message directly to all recipients; (b) linear, which sends the message to the local daemon on each node, which then relays it to its own local procs; and (b) binomial, which sends the message via a binomial algo across all the daemons, each of which then relays to its own local procs. The crossover points between the algos are adjustable via MCA param, or you can simply demand that a specific algo be used.
3. orteds no longer exhibit two types of behavior: bootproxy or VM. Orteds now always behave like they are part of a virtual machine - they simply launch a job if mpirun tells them to do so. This is another step towards creating an "orteboot" functionality, but also provided a clean system for supporting message relaying.
Note one major impact of this commit: multiple daemons on a node cannot be supported any longer! Only a single daemon/node is now allowed.
This commit is known to break support for the following environments: POE, Xgrid, Xcpu, Windows. It has been tested on rsh, SLURM, and Bproc. Modifications for TM support have been made but could not be verified due to machine problems at LANL. Modifications for SGE have been made but could not be verified. The developers for the non-verified environments will be separately notified along with suggestions on how to fix the problems.
This commit was SVN r15007.
2007-06-12 17:28:54 +04:00
|
|
|
/* if this daemon already exists, don't launch it! */
|
|
|
|
if (rmaps_node->daemon_preexists) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* setup node name */
|
|
|
|
free(argv[node_name_index1]);
|
|
|
|
if (NULL != rmaps_node->username &&
|
|
|
|
0 != strlen (rmaps_node->username)) {
|
|
|
|
asprintf (&argv[node_name_index1], "%s@%s",
|
|
|
|
rmaps_node->username, rmaps_node->nodename);
|
|
|
|
} else {
|
|
|
|
argv[node_name_index1] = strdup(rmaps_node->nodename);
|
|
|
|
}
|
2005-10-31 23:37:44 +03:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
free(argv[node_name_index2]);
|
|
|
|
argv[node_name_index2] = strdup(rmaps_node->nodename);
|
|
|
|
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
/* fork a child to exec the rsh/ssh session */
|
2006-10-07 19:45:24 +04:00
|
|
|
|
|
|
|
pid = fork();
|
|
|
|
if (pid < 0) {
|
2007-04-26 19:07:40 +04:00
|
|
|
ORTE_ERROR_LOG(ORTE_ERR_SYS_LIMITS_CHILDREN);
|
|
|
|
rc = ORTE_ERR_SYS_LIMITS_CHILDREN;
|
2006-10-07 19:45:24 +04:00
|
|
|
goto cleanup;
|
|
|
|
}
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* child */
|
|
|
|
if (pid == 0) {
|
|
|
|
char* name_string;
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
char** env;
|
2006-10-07 19:45:24 +04:00
|
|
|
char* var;
|
|
|
|
long fd, fdmax = sysconf(_SC_OPEN_MAX);
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: launching on node %s\n",
|
|
|
|
rmaps_node->nodename);
|
|
|
|
}
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2007-07-12 23:53:18 +04:00
|
|
|
/* setup environment */
|
|
|
|
env = opal_argv_copy(environ);
|
|
|
|
|
|
|
|
/* clean any mca params that shouldn't go to the backend */
|
|
|
|
orte_pls_base_purge_mca_params(&env);
|
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* We don't need to sense an oversubscribed condition and set the sched_yield
|
|
|
|
* for the node as we are only launching the daemons at this time. The daemons
|
|
|
|
* are now smart enough to set the oversubscribed condition themselves when
|
|
|
|
* they launch the local procs.
|
|
|
|
*/
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* Is this a local launch?
|
|
|
|
*
|
|
|
|
* Not all node names may be resolvable (if we found
|
|
|
|
* localhost in the hostfile, for example). So first
|
|
|
|
* check trivial case of node_name being same as the
|
|
|
|
* current nodename, which must be local. If that doesn't
|
|
|
|
* match, check using ifislocal().
|
|
|
|
*/
|
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 22:34:59 +03:00
|
|
|
if (!mca_pls_rsh_component.force_rsh &&
|
|
|
|
(0 == strcmp(rmaps_node->nodename, orte_system_info.nodename) ||
|
2007-04-05 23:22:26 +04:00
|
|
|
opal_ifislocal(rmaps_node->nodename))) {
|
2005-08-04 19:09:02 +04:00
|
|
|
if (mca_pls_rsh_component.debug) {
|
2006-10-07 19:45:24 +04:00
|
|
|
opal_output(0, "pls:rsh: %s is a LOCAL node\n",
|
|
|
|
rmaps_node->nodename);
|
2005-08-04 19:09:02 +04:00
|
|
|
}
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
2007-01-26 10:06:52 +03:00
|
|
|
exec_path = opal_path_findv(argv[local_exec_index], 0, environ, NULL);
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
if (NULL == exec_path && NULL == prefix_dir) {
|
|
|
|
rc = orte_pls_rsh_fill_exec_path (&exec_path);
|
|
|
|
if (ORTE_SUCCESS != rc) {
|
2007-04-26 19:07:40 +04:00
|
|
|
/* don't normally ERROR_LOG this problem as the function has already
|
|
|
|
* printed out a nice error message for us - do the ERROR_LOG only
|
|
|
|
* when we are in debug mode so we can see where it occurred
|
|
|
|
*/
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
exit(-1); /* the forked process MUST exit */
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
|
|
|
} else {
|
2006-10-07 19:45:24 +04:00
|
|
|
if (NULL != prefix_dir) {
|
2007-04-06 00:17:10 +04:00
|
|
|
exec_path = opal_os_path( false, prefix_dir, bin_base, mca_pls_rsh_component.orted, NULL );
|
2005-09-29 16:35:43 +04:00
|
|
|
}
|
2006-10-07 19:45:24 +04:00
|
|
|
/* If we yet did not fill up the execpath, do so now */
|
|
|
|
if (NULL == exec_path) {
|
2005-09-06 20:10:05 +04:00
|
|
|
rc = orte_pls_rsh_fill_exec_path (&exec_path);
|
|
|
|
if (ORTE_SUCCESS != rc) {
|
2007-04-26 19:07:40 +04:00
|
|
|
/* don't normally ERROR_LOG this problem as the function has already
|
|
|
|
* printed out a nice error message for us - do the ERROR_LOG only
|
|
|
|
* when we are in debug mode so we can see where it occurred
|
|
|
|
*/
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
2007-04-14 21:36:27 +04:00
|
|
|
exit(-1); /* the forked process MUST exit */
|
2005-07-28 17:00:32 +04:00
|
|
|
}
|
2005-09-29 16:35:43 +04:00
|
|
|
}
|
2006-10-07 19:45:24 +04:00
|
|
|
}
|
2007-04-26 19:07:40 +04:00
|
|
|
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
/* If we have a prefix, then modify the PATH and
|
|
|
|
LD_LIBRARY_PATH environment variables. We're
|
|
|
|
already in the child process, so it's ok to modify
|
|
|
|
environ. */
|
|
|
|
if (NULL != prefix_dir) {
|
|
|
|
char *oldenv, *newenv;
|
2007-04-26 19:07:40 +04:00
|
|
|
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
/* Reset PATH */
|
|
|
|
newenv = opal_os_path( false, prefix_dir, bin_base, NULL );
|
|
|
|
oldenv = getenv("PATH");
|
|
|
|
if (NULL != oldenv) {
|
|
|
|
char *temp;
|
|
|
|
asprintf(&temp, "%s:%s", newenv, oldenv );
|
|
|
|
free( newenv );
|
|
|
|
newenv = temp;
|
|
|
|
}
|
2007-07-12 23:53:18 +04:00
|
|
|
opal_setenv("PATH", newenv, true, &env);
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: reset PATH: %s", newenv);
|
|
|
|
}
|
|
|
|
free(newenv);
|
2007-04-26 19:07:40 +04:00
|
|
|
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
/* Reset LD_LIBRARY_PATH */
|
|
|
|
newenv = opal_os_path( false, prefix_dir, lib_base, NULL );
|
|
|
|
oldenv = getenv("LD_LIBRARY_PATH");
|
|
|
|
if (NULL != oldenv) {
|
|
|
|
char* temp;
|
|
|
|
asprintf(&temp, "%s:%s", newenv, oldenv);
|
|
|
|
free(newenv);
|
|
|
|
newenv = temp;
|
|
|
|
}
|
2007-07-12 23:53:18 +04:00
|
|
|
opal_setenv("LD_LIBRARY_PATH", newenv, true, &env);
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
opal_output(0, "pls:rsh: reset LD_LIBRARY_PATH: %s",
|
|
|
|
newenv);
|
|
|
|
}
|
|
|
|
free(newenv);
|
|
|
|
}
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* Since this is a local execution, we need to
|
2007-04-26 19:07:40 +04:00
|
|
|
potentially whack the final ")" in the argv (if
|
Bring in the generalized xcast communication system along with the correspondingly revised orted launch. I will send a message out to developers explaining the basic changes. In brief:
1. generalize orte_rml.xcast to become a general broadcast-like messaging system. Messages can now be sent to any tag on the daemons or processes. Note that any message sent via xcast will be delivered to ALL processes in the specified job - you don't get to pick and choose. At a later date, we will introduce an augmented capability that will use the daemons as relays, but will allow you to send to a specified array of process names.
2. extended orte_rml.xcast so it supports more scalable message routing methodologies. At the moment, we support three: (a) direct, which sends the message directly to all recipients; (b) linear, which sends the message to the local daemon on each node, which then relays it to its own local procs; and (b) binomial, which sends the message via a binomial algo across all the daemons, each of which then relays to its own local procs. The crossover points between the algos are adjustable via MCA param, or you can simply demand that a specific algo be used.
3. orteds no longer exhibit two types of behavior: bootproxy or VM. Orteds now always behave like they are part of a virtual machine - they simply launch a job if mpirun tells them to do so. This is another step towards creating an "orteboot" functionality, but also provided a clean system for supporting message relaying.
Note one major impact of this commit: multiple daemons on a node cannot be supported any longer! Only a single daemon/node is now allowed.
This commit is known to break support for the following environments: POE, Xgrid, Xcpu, Windows. It has been tested on rsh, SLURM, and Bproc. Modifications for TM support have been made but could not be verified due to machine problems at LANL. Modifications for SGE have been made but could not be verified. The developers for the non-verified environments will be separately notified along with suggestions on how to fix the problems.
This commit was SVN r15007.
2007-06-12 17:28:54 +04:00
|
|
|
sh/csh conditionals, from above). Note that we're
|
2007-04-26 19:07:40 +04:00
|
|
|
modifying the argv[] in the child process, so
|
|
|
|
there's no need to save this and restore it
|
|
|
|
afterward -- the parent's argv[] is unmodified. */
|
2006-10-07 19:45:24 +04:00
|
|
|
if (NULL != argv[local_exec_index_end]) {
|
|
|
|
free(argv[local_exec_index_end]);
|
|
|
|
argv[local_exec_index_end] = NULL;
|
2005-08-04 19:09:02 +04:00
|
|
|
}
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2007-01-25 17:17:44 +03:00
|
|
|
/* tell the daemon to setup its own process session/group */
|
|
|
|
opal_argv_append(&argc, &argv, "--set-sid");
|
2007-01-26 10:06:52 +03:00
|
|
|
exec_argv = &argv[local_exec_index];
|
2007-01-25 17:17:44 +03:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* Finally, chdir($HOME) because we're making the
|
2007-04-26 19:07:40 +04:00
|
|
|
assumption that this is what will happen on
|
|
|
|
remote nodes (via rsh/ssh). This allows a user
|
|
|
|
to specify a path that is relative to $HOME for
|
|
|
|
both the cwd and argv[0] and it will work on
|
|
|
|
all nodes -- including the local nost.
|
|
|
|
Otherwise, it would work on remote nodes and
|
|
|
|
not the local node. If the user does not start
|
|
|
|
in $HOME on the remote nodes... well... let's
|
|
|
|
hope they start in $HOME. :-) */
|
2006-10-07 19:45:24 +04:00
|
|
|
var = getenv("HOME");
|
|
|
|
if (NULL != var) {
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
2007-04-14 21:36:27 +04:00
|
|
|
opal_output(0, "pls:rsh: changing to directory %s", var);
|
2006-10-07 19:45:24 +04:00
|
|
|
}
|
|
|
|
/* Ignore errors -- what are we going to do?
|
2007-04-26 19:07:40 +04:00
|
|
|
(and we ignore errors on the remote nodes
|
|
|
|
in the fork pls, so this is consistent) */
|
2006-10-07 19:45:24 +04:00
|
|
|
chdir(var);
|
|
|
|
}
|
|
|
|
} else {
|
2005-10-27 21:04:10 +04:00
|
|
|
if (mca_pls_rsh_component.debug) {
|
2006-10-07 19:45:24 +04:00
|
|
|
opal_output(0, "pls:rsh: %s is a REMOTE node\n",
|
|
|
|
rmaps_node->nodename);
|
|
|
|
}
|
|
|
|
exec_argv = argv;
|
|
|
|
exec_path = strdup(mca_pls_rsh_component.agent_path);
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
if (NULL != prefix_dir) {
|
2007-04-21 04:15:05 +04:00
|
|
|
char *opal_prefix = getenv("OPAL_PREFIX");
|
2006-11-09 13:16:45 +03:00
|
|
|
if (remote_sh) {
|
2006-10-07 19:45:24 +04:00
|
|
|
asprintf (&argv[local_exec_index],
|
2007-04-21 04:15:05 +04:00
|
|
|
"%s%s%s PATH=%s/%s:$PATH ; export PATH ; "
|
2006-10-07 19:45:24 +04:00
|
|
|
"LD_LIBRARY_PATH=%s/%s:$LD_LIBRARY_PATH ; export LD_LIBRARY_PATH ; "
|
|
|
|
"%s/%s/%s",
|
2007-04-21 04:15:05 +04:00
|
|
|
(opal_prefix != NULL ? "OPAL_PREFIX=" : ""),
|
|
|
|
(opal_prefix != NULL ? opal_prefix : ""),
|
|
|
|
(opal_prefix != NULL ? " ;" : ""),
|
2006-10-07 19:45:24 +04:00
|
|
|
prefix_dir, bin_base,
|
|
|
|
prefix_dir, lib_base,
|
|
|
|
prefix_dir, bin_base,
|
|
|
|
mca_pls_rsh_component.orted);
|
2007-04-05 23:22:26 +04:00
|
|
|
} else if (remote_csh) {
|
2006-10-07 19:45:24 +04:00
|
|
|
/* [t]csh is a bit more challenging -- we
|
|
|
|
have to check whether LD_LIBRARY_PATH
|
|
|
|
is already set before we try to set it.
|
|
|
|
Must be very careful about obeying
|
|
|
|
[t]csh's order of evaluation and not
|
|
|
|
using a variable before it is defined.
|
2007-04-26 19:07:40 +04:00
|
|
|
See this thread for more details:
|
2006-10-07 19:45:24 +04:00
|
|
|
http://www.open-mpi.org/community/lists/users/2006/01/0517.php. */
|
|
|
|
asprintf (&argv[local_exec_index],
|
2007-04-21 04:15:05 +04:00
|
|
|
"%s%s%s set path = ( %s/%s $path ) ; "
|
2006-10-07 19:45:24 +04:00
|
|
|
"if ( $?LD_LIBRARY_PATH == 1 ) "
|
|
|
|
"set OMPI_have_llp ; "
|
|
|
|
"if ( $?LD_LIBRARY_PATH == 0 ) "
|
|
|
|
"setenv LD_LIBRARY_PATH %s/%s ; "
|
|
|
|
"if ( $?OMPI_have_llp == 1 ) "
|
|
|
|
"setenv LD_LIBRARY_PATH %s/%s:$LD_LIBRARY_PATH ; "
|
|
|
|
"%s/%s/%s",
|
2007-04-21 04:15:05 +04:00
|
|
|
(opal_prefix != NULL ? "setenv OPAL_PREFIX " : ""),
|
|
|
|
(opal_prefix != NULL ? opal_prefix : ""),
|
|
|
|
(opal_prefix != NULL ? " ;" : ""),
|
2006-10-07 19:45:24 +04:00
|
|
|
prefix_dir, bin_base,
|
|
|
|
prefix_dir, lib_base,
|
|
|
|
prefix_dir, lib_base,
|
|
|
|
prefix_dir, bin_base,
|
|
|
|
mca_pls_rsh_component.orted);
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
|
|
|
}
|
2006-10-07 19:45:24 +04:00
|
|
|
}
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* setup process name */
|
Bring in the generalized xcast communication system along with the correspondingly revised orted launch. I will send a message out to developers explaining the basic changes. In brief:
1. generalize orte_rml.xcast to become a general broadcast-like messaging system. Messages can now be sent to any tag on the daemons or processes. Note that any message sent via xcast will be delivered to ALL processes in the specified job - you don't get to pick and choose. At a later date, we will introduce an augmented capability that will use the daemons as relays, but will allow you to send to a specified array of process names.
2. extended orte_rml.xcast so it supports more scalable message routing methodologies. At the moment, we support three: (a) direct, which sends the message directly to all recipients; (b) linear, which sends the message to the local daemon on each node, which then relays it to its own local procs; and (b) binomial, which sends the message via a binomial algo across all the daemons, each of which then relays to its own local procs. The crossover points between the algos are adjustable via MCA param, or you can simply demand that a specific algo be used.
3. orteds no longer exhibit two types of behavior: bootproxy or VM. Orteds now always behave like they are part of a virtual machine - they simply launch a job if mpirun tells them to do so. This is another step towards creating an "orteboot" functionality, but also provided a clean system for supporting message relaying.
Note one major impact of this commit: multiple daemons on a node cannot be supported any longer! Only a single daemon/node is now allowed.
This commit is known to break support for the following environments: POE, Xgrid, Xcpu, Windows. It has been tested on rsh, SLURM, and Bproc. Modifications for TM support have been made but could not be verified due to machine problems at LANL. Modifications for SGE have been made but could not be verified. The developers for the non-verified environments will be separately notified along with suggestions on how to fix the problems.
This commit was SVN r15007.
2007-06-12 17:28:54 +04:00
|
|
|
rc = orte_ns.get_proc_name_string(&name_string, rmaps_node->daemon);
|
2006-10-07 19:45:24 +04:00
|
|
|
if (ORTE_SUCCESS != rc) {
|
Bring in the generalized xcast communication system along with the correspondingly revised orted launch. I will send a message out to developers explaining the basic changes. In brief:
1. generalize orte_rml.xcast to become a general broadcast-like messaging system. Messages can now be sent to any tag on the daemons or processes. Note that any message sent via xcast will be delivered to ALL processes in the specified job - you don't get to pick and choose. At a later date, we will introduce an augmented capability that will use the daemons as relays, but will allow you to send to a specified array of process names.
2. extended orte_rml.xcast so it supports more scalable message routing methodologies. At the moment, we support three: (a) direct, which sends the message directly to all recipients; (b) linear, which sends the message to the local daemon on each node, which then relays it to its own local procs; and (b) binomial, which sends the message via a binomial algo across all the daemons, each of which then relays to its own local procs. The crossover points between the algos are adjustable via MCA param, or you can simply demand that a specific algo be used.
3. orteds no longer exhibit two types of behavior: bootproxy or VM. Orteds now always behave like they are part of a virtual machine - they simply launch a job if mpirun tells them to do so. This is another step towards creating an "orteboot" functionality, but also provided a clean system for supporting message relaying.
Note one major impact of this commit: multiple daemons on a node cannot be supported any longer! Only a single daemon/node is now allowed.
This commit is known to break support for the following environments: POE, Xgrid, Xcpu, Windows. It has been tested on rsh, SLURM, and Bproc. Modifications for TM support have been made but could not be verified due to machine problems at LANL. Modifications for SGE have been made but could not be verified. The developers for the non-verified environments will be separately notified along with suggestions on how to fix the problems.
This commit was SVN r15007.
2007-06-12 17:28:54 +04:00
|
|
|
opal_output(0, "orte_pls_rsh: unable to get daemon name as string");
|
2005-03-14 23:57:21 +03:00
|
|
|
exit(-1);
|
2006-10-07 19:45:24 +04:00
|
|
|
}
|
|
|
|
free(argv[proc_name_index]);
|
|
|
|
argv[proc_name_index] = strdup(name_string);
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
if (!mca_pls_rsh_component.debug) {
|
2007-04-05 23:22:26 +04:00
|
|
|
/* setup stdin */
|
2006-10-07 19:45:24 +04:00
|
|
|
int fd = open("/dev/null", O_RDWR);
|
|
|
|
dup2(fd, 0);
|
|
|
|
close(fd);
|
|
|
|
}
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* close all file descriptors w/ exception of stdin/stdout/stderr */
|
|
|
|
for(fd=3; fd<fdmax; fd++)
|
|
|
|
close(fd);
|
2007-04-26 19:07:40 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* Set signal handlers back to the default. Do this close
|
2007-04-05 23:22:26 +04:00
|
|
|
to the execve() because the event library may (and likely
|
|
|
|
will) reset them. If we don't do this, the event
|
|
|
|
library may have left some set that, at least on some
|
|
|
|
OS's, don't get reset via fork() or exec(). Hence, the
|
|
|
|
orted could be unkillable (for example). */
|
2006-10-07 19:45:24 +04:00
|
|
|
|
|
|
|
set_handler_default(SIGTERM);
|
|
|
|
set_handler_default(SIGINT);
|
|
|
|
set_handler_default(SIGHUP);
|
|
|
|
set_handler_default(SIGPIPE);
|
|
|
|
set_handler_default(SIGCHLD);
|
|
|
|
|
|
|
|
/* Unblock all signals, for many of the same reasons that
|
2007-04-05 23:22:26 +04:00
|
|
|
we set the default handlers, above. This is noticable
|
|
|
|
on Linux where the event library blocks SIGTERM, but we
|
|
|
|
don't want that blocked by the orted (or, more
|
|
|
|
specifically, we don't want it to be blocked by the
|
|
|
|
orted and then inherited by the ORTE processes that it
|
|
|
|
forks, making them unkillable by SIGTERM). */
|
2006-10-07 19:45:24 +04:00
|
|
|
sigprocmask(0, 0, &sigs);
|
|
|
|
sigprocmask(SIG_UNBLOCK, &sigs, 0);
|
|
|
|
|
|
|
|
/* exec the daemon */
|
|
|
|
if (mca_pls_rsh_component.debug) {
|
|
|
|
param = opal_argv_join(exec_argv, ' ');
|
|
|
|
if (NULL != param) {
|
2007-01-30 06:56:48 +03:00
|
|
|
opal_output(0, "pls:rsh: executing: (%s) [%s]", exec_path, param);
|
2007-01-26 11:09:22 +03:00
|
|
|
free(param);
|
2005-10-27 21:04:10 +04:00
|
|
|
}
|
2005-03-18 06:43:59 +03:00
|
|
|
}
|
2006-10-07 19:45:24 +04:00
|
|
|
execve(exec_path, exec_argv, env);
|
2007-01-26 10:06:52 +03:00
|
|
|
opal_output(0, "pls:rsh: execv of %s failed with errno=%s(%d)\n",
|
|
|
|
exec_path, strerror(errno), errno);
|
2006-10-07 19:45:24 +04:00
|
|
|
exit(-1);
|
|
|
|
|
|
|
|
} else { /* father */
|
Bring in the generalized xcast communication system along with the correspondingly revised orted launch. I will send a message out to developers explaining the basic changes. In brief:
1. generalize orte_rml.xcast to become a general broadcast-like messaging system. Messages can now be sent to any tag on the daemons or processes. Note that any message sent via xcast will be delivered to ALL processes in the specified job - you don't get to pick and choose. At a later date, we will introduce an augmented capability that will use the daemons as relays, but will allow you to send to a specified array of process names.
2. extended orte_rml.xcast so it supports more scalable message routing methodologies. At the moment, we support three: (a) direct, which sends the message directly to all recipients; (b) linear, which sends the message to the local daemon on each node, which then relays it to its own local procs; and (b) binomial, which sends the message via a binomial algo across all the daemons, each of which then relays to its own local procs. The crossover points between the algos are adjustable via MCA param, or you can simply demand that a specific algo be used.
3. orteds no longer exhibit two types of behavior: bootproxy or VM. Orteds now always behave like they are part of a virtual machine - they simply launch a job if mpirun tells them to do so. This is another step towards creating an "orteboot" functionality, but also provided a clean system for supporting message relaying.
Note one major impact of this commit: multiple daemons on a node cannot be supported any longer! Only a single daemon/node is now allowed.
This commit is known to break support for the following environments: POE, Xgrid, Xcpu, Windows. It has been tested on rsh, SLURM, and Bproc. Modifications for TM support have been made but could not be verified due to machine problems at LANL. Modifications for SGE have been made but could not be verified. The developers for the non-verified environments will be separately notified along with suggestions on how to fix the problems.
This commit was SVN r15007.
2007-06-12 17:28:54 +04:00
|
|
|
/* indicate this daemon has been launched in case anyone is sitting on that trigger */
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_smr.set_proc_state(rmaps_node->daemon, ORTE_PROC_STATE_LAUNCHED, 0))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
goto cleanup;
|
|
|
|
}
|
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
OPAL_THREAD_LOCK(&mca_pls_rsh_component.lock);
|
2007-04-06 00:36:33 +04:00
|
|
|
/* This situation can lead to a deadlock if '--debug-daemons' is set.
|
|
|
|
* However, the deadlock condition is tested at the begining of this
|
|
|
|
* function, so we're quite confident it should not happens here.
|
2006-10-07 19:45:24 +04:00
|
|
|
*/
|
|
|
|
if (mca_pls_rsh_component.num_children++ >=
|
|
|
|
mca_pls_rsh_component.num_concurrent) {
|
|
|
|
opal_condition_wait(&mca_pls_rsh_component.cond, &mca_pls_rsh_component.lock);
|
|
|
|
}
|
|
|
|
OPAL_THREAD_UNLOCK(&mca_pls_rsh_component.lock);
|
|
|
|
|
|
|
|
/* setup callback on sigchild - wait until setup above is complete
|
|
|
|
* as the callback can occur in the call to orte_wait_cb
|
|
|
|
*/
|
2007-04-26 19:07:40 +04:00
|
|
|
orte_wait_cb(pid, orte_pls_rsh_wait_daemon, NULL);
|
2006-10-07 19:45:24 +04:00
|
|
|
|
|
|
|
/* if required - add delay to avoid problems w/ X11 authentication */
|
|
|
|
if (mca_pls_rsh_component.debug && mca_pls_rsh_component.delay) {
|
|
|
|
sleep(mca_pls_rsh_component.delay);
|
|
|
|
}
|
2005-09-06 20:10:05 +04:00
|
|
|
}
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
2007-07-12 23:53:18 +04:00
|
|
|
|
|
|
|
/* wait for daemons to callback */
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_pls_base_daemon_callback(map->num_new_daemons))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
goto cleanup;
|
|
|
|
}
|
|
|
|
|
|
|
|
launch_apps:
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_pls_base_launch_apps(map))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
goto cleanup;
|
|
|
|
}
|
|
|
|
|
2007-04-26 19:07:40 +04:00
|
|
|
/* get here if launch went okay */
|
|
|
|
failed_launch = false;
|
2007-07-12 23:53:18 +04:00
|
|
|
|
|
|
|
|
2007-04-05 23:22:26 +04:00
|
|
|
cleanup:
|
2007-04-26 19:07:40 +04:00
|
|
|
if (NULL != map) {
|
|
|
|
OBJ_RELEASE(map);
|
|
|
|
}
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2006-05-16 18:14:12 +04:00
|
|
|
if (NULL != lib_base) {
|
|
|
|
free(lib_base);
|
|
|
|
}
|
|
|
|
if (NULL != bin_base) {
|
|
|
|
free(bin_base);
|
|
|
|
}
|
|
|
|
|
2007-04-26 19:07:40 +04:00
|
|
|
if (NULL != jobid_string) {
|
|
|
|
free(jobid_string); /* done with this variable */
|
|
|
|
}
|
|
|
|
if (NULL != argv) {
|
|
|
|
opal_argv_free(argv);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* check for failed launch - if so, force terminate */
|
|
|
|
if (failed_launch) {
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_smr.set_job_state(jobid, ORTE_JOB_STATE_FAILED_TO_START))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_wakeup(jobid))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
}
|
2005-10-08 02:24:52 +04:00
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
2005-03-31 19:47:37 +04:00
|
|
|
|
|
|
|
/**
|
2006-09-15 01:29:51 +04:00
|
|
|
* Terminate all processes for a given job
|
2005-03-31 19:47:37 +04:00
|
|
|
*/
|
2007-01-25 17:17:44 +03:00
|
|
|
int orte_pls_rsh_terminate_job(orte_jobid_t jobid, struct timeval *timeout, opal_list_t *attrs)
|
2005-03-14 23:57:21 +03:00
|
|
|
{
|
2006-09-15 01:29:51 +04:00
|
|
|
int rc;
|
|
|
|
|
|
|
|
/* order them to kill their local procs for this job */
|
2007-04-24 05:58:40 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_pls_base_orted_kill_local_procs(jobid, timeout, attrs))) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Terminate the orteds for a given job
|
|
|
|
*/
|
2007-04-25 00:53:54 +04:00
|
|
|
int orte_pls_rsh_terminate_orteds(struct timeval *timeout, opal_list_t *attrs)
|
2006-09-15 01:29:51 +04:00
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
/* now tell them to die! */
|
2007-04-24 05:58:40 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_pls_base_orted_exit(timeout, attrs))) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
return rc;
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/*
|
|
|
|
* Terminate a specific process
|
|
|
|
*/
|
2005-03-14 23:57:21 +03:00
|
|
|
int orte_pls_rsh_terminate_proc(const orte_process_name_t* proc)
|
|
|
|
{
|
2006-10-02 22:29:15 +04:00
|
|
|
OPAL_TRACE(1);
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
return ORTE_ERR_NOT_IMPLEMENTED;
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 22:34:59 +03:00
|
|
|
int orte_pls_rsh_signal_job(orte_jobid_t jobid, int32_t signal, opal_list_t *attrs)
|
2006-06-08 22:27:17 +04:00
|
|
|
{
|
2006-09-15 01:29:51 +04:00
|
|
|
int rc;
|
|
|
|
|
|
|
|
/* order them to pass this signal to their local procs */
|
2007-04-24 05:58:40 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_pls_base_orted_signal_local_procs(jobid, signal, attrs))) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
return rc;
|
2006-06-08 22:27:17 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
int orte_pls_rsh_signal_proc(const orte_process_name_t* proc, int32_t signal)
|
|
|
|
{
|
2006-10-02 22:29:15 +04:00
|
|
|
OPAL_TRACE(1);
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
return ORTE_ERR_NOT_IMPLEMENTED;
|
2006-06-08 22:27:17 +04:00
|
|
|
}
|
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
int orte_pls_rsh_finalize(void)
|
|
|
|
{
|
2006-09-15 01:29:51 +04:00
|
|
|
int rc;
|
|
|
|
|
2005-04-01 02:37:46 +04:00
|
|
|
/* cleanup any pending recvs */
|
2006-09-15 01:29:51 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_pls_base_comm_stop())) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
return rc;
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Handle threading issues.
|
|
|
|
*/
|
|
|
|
|
2005-03-24 18:45:44 +03:00
|
|
|
#if OMPI_HAVE_POSIX_THREADS && OMPI_THREADS_HAVE_DIFFERENT_PIDS && OMPI_ENABLE_PROGRESS_THREADS
|
2005-03-14 23:57:21 +03:00
|
|
|
|
|
|
|
struct orte_pls_rsh_stack_t {
|
2005-07-04 02:45:48 +04:00
|
|
|
opal_condition_t cond;
|
|
|
|
opal_mutex_t mutex;
|
2005-03-14 23:57:21 +03:00
|
|
|
bool complete;
|
|
|
|
orte_jobid_t jobid;
|
|
|
|
int rc;
|
|
|
|
};
|
|
|
|
typedef struct orte_pls_rsh_stack_t orte_pls_rsh_stack_t;
|
|
|
|
|
|
|
|
static void orte_pls_rsh_stack_construct(orte_pls_rsh_stack_t* stack)
|
|
|
|
{
|
2005-07-04 02:45:48 +04:00
|
|
|
OBJ_CONSTRUCT(&stack->mutex, opal_mutex_t);
|
|
|
|
OBJ_CONSTRUCT(&stack->cond, opal_condition_t);
|
2005-03-14 23:57:21 +03:00
|
|
|
stack->rc = 0;
|
|
|
|
stack->complete = false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void orte_pls_rsh_stack_destruct(orte_pls_rsh_stack_t* stack)
|
|
|
|
{
|
|
|
|
OBJ_DESTRUCT(&stack->mutex);
|
|
|
|
OBJ_DESTRUCT(&stack->cond);
|
|
|
|
}
|
|
|
|
|
|
|
|
static OBJ_CLASS_INSTANCE(
|
|
|
|
orte_pls_rsh_stack_t,
|
2005-07-03 20:06:07 +04:00
|
|
|
opal_object_t,
|
2005-03-14 23:57:21 +03:00
|
|
|
orte_pls_rsh_stack_construct,
|
|
|
|
orte_pls_rsh_stack_destruct);
|
|
|
|
|
|
|
|
static void orte_pls_rsh_launch_cb(int fd, short event, void* args)
|
|
|
|
{
|
|
|
|
orte_pls_rsh_stack_t *stack = (orte_pls_rsh_stack_t*)args;
|
2005-07-04 02:45:48 +04:00
|
|
|
OPAL_THREAD_LOCK(&stack->mutex);
|
2005-03-14 23:57:21 +03:00
|
|
|
stack->rc = orte_pls_rsh_launch(stack->jobid);
|
|
|
|
stack->complete = true;
|
2005-07-04 02:45:48 +04:00
|
|
|
opal_condition_signal(&stack->cond);
|
|
|
|
OPAL_THREAD_UNLOCK(&stack->mutex);
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static int orte_pls_rsh_launch_threaded(orte_jobid_t jobid)
|
|
|
|
{
|
|
|
|
struct timeval tv = { 0, 0 };
|
2005-07-04 03:09:55 +04:00
|
|
|
struct opal_event event;
|
2005-03-14 23:57:21 +03:00
|
|
|
struct orte_pls_rsh_stack_t stack;
|
|
|
|
|
|
|
|
OBJ_CONSTRUCT(&stack, orte_pls_rsh_stack_t);
|
|
|
|
|
|
|
|
stack.jobid = jobid;
|
2005-09-19 19:54:53 +04:00
|
|
|
if( opal_event_progress_thread() ) {
|
|
|
|
stack.rc = orte_pls_rsh_launch( jobid );
|
|
|
|
} else {
|
|
|
|
opal_evtimer_set(&event, orte_pls_rsh_launch_cb, &stack);
|
|
|
|
opal_evtimer_add(&event, &tv);
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2005-09-19 19:54:53 +04:00
|
|
|
OPAL_THREAD_LOCK(&stack.mutex);
|
|
|
|
while (stack.complete == false) {
|
|
|
|
opal_condition_wait(&stack.cond, &stack.mutex);
|
|
|
|
}
|
|
|
|
OPAL_THREAD_UNLOCK(&stack.mutex);
|
2005-08-04 19:09:02 +04:00
|
|
|
}
|
2005-03-14 23:57:21 +03:00
|
|
|
OBJ_DESTRUCT(&stack);
|
|
|
|
return stack.rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
2005-05-19 17:33:28 +04:00
|
|
|
|
|
|
|
static void set_handler_default(int sig)
|
|
|
|
{
|
|
|
|
struct sigaction act;
|
|
|
|
|
|
|
|
act.sa_handler = SIG_DFL;
|
|
|
|
act.sa_flags = 0;
|
|
|
|
sigemptyset(&act.sa_mask);
|
|
|
|
|
|
|
|
sigaction(sig, &act, (struct sigaction *)0);
|
|
|
|
}
|
2007-06-21 15:40:42 +04:00
|
|
|
|
|
|
|
|
|
|
|
static orte_pls_rsh_shell_t find_shell(char *shell)
|
|
|
|
{
|
|
|
|
int i = 0;
|
|
|
|
char *sh_name = NULL;
|
|
|
|
|
|
|
|
sh_name = rindex(shell, '/');
|
|
|
|
/* skip the '/' */
|
|
|
|
++sh_name;
|
|
|
|
for (i = 0; i < (int)(sizeof (orte_pls_rsh_shell_name) /
|
|
|
|
sizeof(orte_pls_rsh_shell_name[0])); ++i) {
|
|
|
|
if (0 == strcmp(sh_name, orte_pls_rsh_shell_name[i])) {
|
|
|
|
return i;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* We didn't find it */
|
|
|
|
return ORTE_PLS_RSH_SHELL_UNKNOWN;
|
|
|
|
}
|