[IPython-dev] scp error in ipcluster start when profile doesn't exist on engine host

Drain, Theodore R (392P) theodore.r.drain at jpl.nasa.gov
Wed Feb 19 13:34:58 EST 2014

It's from Feb 05.  I'll update to the latest and go from there.


From: ipython-dev-bounces at scipy.org [ipython-dev-bounces at scipy.org] on behalf of MinRK [benjaminrk at gmail.com]
Sent: Wednesday, February 19, 2014 10:21 AM
To: IPython developers list
Subject: Re: [IPython-dev] scp error in ipcluster start when profile doesn't exist on engine host

What is the commit you are using? I believe this was fixed very recently in master.


On Wed, Feb 19, 2014 at 9:50 AM, Drain, Theodore R (392P) <theodore.r.drain at jpl.nasa.gov<mailto:theodore.r.drain at jpl.nasa.gov>> wrote:
I'm running the 2.0 development code and getting an error when I try to start a cluster using the ssh engine launcher.  The error happens when it tries to copy the json security file to the engine.  If any of the directories in the path to the json file (.ipython/profile_NAME/security) don't exist, then scp throws an exception which stops the cluster.

It's fairly annoying to have to log in to each machine in my cluster and create a directory tree every time I change the name of the profile.  So - is this the expected behavior?

There are some ways to use scp (or maybe rsync) that might be more robust:

IPython-dev mailing list
IPython-dev at scipy.org<mailto:IPython-dev at scipy.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20140219/e8bc0cdd/attachment.html>

More information about the IPython-dev mailing list