Re: Trouble with ipcluster on a Raspberry Pi

Thomas Baruchel <[email protected]> Thu, 7 May 2015 18:21:20 +0200 (CEST)

Newsgroups	gmane.comp.python.ipython.user
Message-ID	<alpine.DEB.2.02.1505071816360.12877@raspberrypi>

On Wed, 15 Apr 2015, MinRK wrote:
> That’s probably the issue. What happens if you do ipcontroller --ip=127.0.0.1?

As previously said, I get an issue with it, but below is what happens if I now
try other settings:

   ipcontroller --ip="*"
     seems to work; no error and the process is waiting.
     netstat -lnptu   shows several python processes listening on various ports
then
   ipengine  says:
2015-05-07 18:18:43,091.091 [IPEngineApp] Using existing profile dir: u'/home/pi/.config/ipython/profile_default'
2015-05-07 18:18:43.104 [IPEngineApp] Loading url_file u'/home/pi/.config/ipython/profile_default/security/ipcontroller-engine.json'
2015-05-07 18:18:43.147 [IPEngineApp] Registering with controller at tcp://127.0.0.1:55468
2015-05-07 18:18:45.149 [IPEngineApp] Registration timed out after 2.0 seconds

(port 55468 was among the ports being listened at)

   ipcontroller --ip="192.168.0.63'  behaves as  the previous one "*"

Any hints?

Regards,

-- 
Thomas Baruchel

_______________________________________________
IPython-User mailing list
[email protected]
http://mail.scipy.org/mailman/listinfo/ipython-user