[IPython-user] ipython1 problem?
ellisonbg.net at gmail.com
Tue Nov 21 13:58:52 CST 2006
It looks like the engines are starting but are not finding the
controller you have running. Things to check:
1. Do you have a firewall blocking ports on the controller's computer?
2. Did you tell the engines where the controller is running:
ipengine --controller-ip=[ip of the machine running the controller]
Another way of finding out what is going on is to start the
ipcontroller and ipengine with the -l flags:
ipcontroller -l cont
ipengine -l eng
These will cause the log files to be written to disk in the format:
Things to look for. You should see the controller log a message that
the engines are being registered. In the engine log you should see
the factor start. If you see the factor start and then stop, the
engine didn't find the controller and is dead.
On 11/21/06, Flavio Coelho <fccoelho at gmail.com> wrote:
> Hi I am testing Ipython1 on another machine ( on mine it works perfectly)
> and everything starts up nicely, I can see all the engines and the
> controller with ps -xa |grep ip but when I create a RemoteController inside
> ipython, I can't connect to the nodes:
> In :import ipython1.kernel.api as kernel
> In :rc =kernel.RemoteController(('127.0.0.1',10105))
> In :rc.getIDs()
> Connecting to controller: (' 127.0.0.1', 10105)
> I have the latest SVN of ipython, ipython1, twisted and nevow. Plus the
> recommended version of ZopeInterface.
> Any hins of what may be going on? Do I have to have a Zope server running?
> Flávio Codeço Coelho
> registered Linux user # 386432
> "Laws are like sausages. It's better not to see them being made."
> Otto von Bismark
> IPython-user mailing list
> IPython-user at scipy.org
More information about the IPython-user