On Fri, Apr 09, 2004 at 02:59:46PM -0500, Sarat C Maruvada wrote:
> Hello Everyone. I am sure the The subject shows a topic that has been
> written about time and time again. Rest assured that I did look through
> mmost of them before deciding to post again. Here is the problem:
>
> LAM/MPI version 7.0.2
> Sun Grid Engine v 5.3p4
>
> * installed a OSCAR based cluster. LAM/MPI works perfectly fine when run
> as a user (lamboot followed by mpi runs and lamclean) all work very well
> * When using integration script with SGE, the nodes do not boot because of
> "warning: fake X11 data forwarded" and hence the lamboot fails. As a user
> all the nodes of the cluster have ssh keys that are in known_hosts file.
>
> I have tried the latest integration scripts shown in the mailing list also
> but to no avail. There was a note about ckill.c having problems but the
> LAM installed didnt have the file ckill.c. After many unsuccessful tries,I
> have given up. I will attach the PE script in SGE here along with any
> other relevant scripts. Any help would be grately appricieated.
>
> PE: lammpi
> ----------
> pe_name lammpi
> queue_list all
> slots 30
> user_lists NONE
> xuser_lists NONE
> start_proc_args /home/SGE/mpi/lamstart.sh $pe_hostfile
> stop_proc_args /home/SGE/mpi/lamstop.sh
> allocation_rule $round_robin
> control_slaves FALSE
> job_is_first_task TRUE
>
> lamstart.sh:
> ------------
> #!/bin/sh
>
> cat /dev/null > /tmp/lamnodes-$USER.$HOSTNAME
> cat $1 | while read line; do
> host=`echo $line | cut -f1 -d" "| cut -f1 -d"."`
> nslots=`echo $line | cut -f2 -d" "`
> echo "${host} cpu=${nslots}" >> /tmp/lamnodes-$USER.$HOSTNAME
> done
> /opt/lam-7.0/bin/lamboot -ssi boot rsh -ssi rsh_agent "ssh -x"
> /tmp/lamnodes-$USER.$HOSTNAME > /dev/null
> #/opt/lam-7.0/bin/lamboot /tmp/lamnodes-$USER.$HOSTNAME >/dev/null
>
> ##rm -f /tmp/lamnodes-$USER.$HOSTNAME
> -> Tried using ssh -x to supress error message but works as if -x option
> was not specified at all.Anywhere else I should change it?
> ******************************************************************
Rather then using -x you might disable X11 forwarding in your
~/.ssh/config file. The following should do it:
# Disable X11 forwarding on all connections.
Host *
ForwardX11 no
-- Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
- application/pgp-signature attachment: stored
|
