Re: [Starcluster] connection.execute behavior

From: Dan Yamins <no email>
Date: Fri, 16 Apr 2010 10:10:58 -0400

On Fri, Apr 16, 2010 at 10:01 AM, Justin Riley <jtriley_at_mit.edu> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Dan,
>
> Try using the internal dns names instead of the public dns names and see
> if that helps:
>
> ie solr_conn.execute('ssh -f -N -L 27017:localhost:27017
> gotdata_at_dom-blah-blah.internal')
>
>
Yes -- I think this works.




> ~Justin
>
> On 04/16/2010 08:04 AM, Dan Yamins
> wrote:
> > Here are two places where behavior of executing a command via
> > connection.execute is different from executing it at the actual shell,
> > causing trouble:
> >
> >
> > 1) I can run this command fine at the actual shell of one of my node,
> > when logged in as root:
> >
> > su gotdata -c "ssh -f -N -L 27017:localhost:27017
> > gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com
> > <mailto:gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com>"
> >
> > It runs, returns without blocking, doing exactly what I want
> > (establishing an ssh tunnel from one node to another on port 27017).
> >
> > But when I try to execute this command over the execute method in the
> > starcluster shell, it DOES block:
> >
> > solr_conn.execute('su gotdata -c "ssh -f -N -L 27017:localhost:27017
> > gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com
> > <mailto:gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com>"')
> >
> > ... and only returns when I manually kill the ssh tunnel that it
> > starts. What should I do to get what I want?
> >
> >
> > 2) The same command, minus the su part, runs fine at the actual shell:
> >
> > ssh -f -N -L 27017:localhost:27017
> > gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com
> > <mailto:gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com>
> >
> > but when I run this command via the execute method, it fails:
> >
> > In [31]: solr_conn.execute('ssh -f -N -L 27017:localhost:27017
> > gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com
> > <mailto:gotdata_at_ec2-184-73-101-141.compute-1.amazonaws.com>')
> > Out[31]: ['Host key verification failed.']
> >
> > Why is the behavior different?
> >
> >
> > Thanks,
> > Dan
> >
> >
> >
> > _______________________________________________
> > Starcluster mailing list
> > Starcluster_at_mit.edu
> > http://mailman.mit.edu/mailman/listinfo/starcluster
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkvIbbYACgkQ4llAkMfDcrmiSgCcDtw7x2vmAYN11HliB14+tO12
> +ZsAn02m9fgMwiCMeDQnUU16cuadpsf3
> =mRud
> -----END PGP SIGNATURE-----
>
Received on Fri Apr 16 2010 - 10:11:00 EDT