gistfile1.txt

$ ipcluster start -n4 --engines=MPIEngineSetLauncher
2013-05-23 19:40:39,864.864 [IPClusterStart] Using existing profile dir: u'/home/goldbaum/.ipython/profile_default'
2013-05-23 19:40:39.871 [IPClusterStart] Starting ipcluster with [daemon=False]
2013-05-23 19:40:39.872 [IPClusterStart] Creating pid file: /home/goldbaum/.ipython/profile_default/pid/ipcluster.pid
2013-05-23 19:40:39.873 [IPClusterStart] Starting Controller with LocalControllerLauncher
2013-05-23 19:40:40.872 [IPClusterStart] Starting 4 Engines with MPIEngineSetLauncher
2013-05-23 19:40:41.116 [IPClusterStart]
            Engines shutdown early, they probably failed to connect.

            Check the engine log files for output.

            If your controller and engines are not on the same machine, you probably
            have to instruct the controller to listen on an interface other than localhost.

            You can set this by adding "--ip='*'" to your ControllerLauncher.controller_args.

            Be sure to read our security docs before instructing your controller to listen on
            a public interface.

2013-05-23 19:40:41.117 [IPClusterStart] IPython cluster: stopping
2013-05-23 19:40:44.118 [IPClusterStart] Removing pid file: /home/goldbaum/.ipython/profile_default/pid/ipcluster.pid