[IPython-dev] ipython on the sun grid engine
Sun Mar 22 01:33:14 CDT 2009
On Sat, Mar 21, 2009 at 11:06 PM, Brian Granger <firstname.lastname@example.org> wrote:
> Very nice. Can you just run the controller on the head node (that you
> use to submit the job)?
It doesn't work, the log is full of messages like:
2009-03-21 23:31:44-0700 [-] Main loop terminated.
2009-03-21 23:31:45-0700 [-] 'EngineConnector: engine registration failed:'
2009-03-21 23:31:45-0700 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.internet.error.ConnectionRefusedError: Connection
was refused by other side: 111: Connection refused.
> It is odd that one of the ssh trys failed.
It didn't fail for the second time when I tried it.
> Usually we start the controller on the head node and then run the
> engines using the queue. But on some systems, this is bad I think.
Why is it bad (besides that it doesn't work for me)?
> As for the ugly output , it is definitely a pretty print thing, but
> I don't know where it is coming from. It could be from sage (maybe
> they have a custom ipython config file).
> But, this look great. Were you able to connect to the running cluster
> using a client on your laptop, or was the client on the head node?
The client was on the head node. When I tried to connect from my
workstation, I did:
scp hnode:.ipython/security/ipcontroller-mec.furl .ipython/security/
and then from ipython:
In : from IPython.kernel import client
In : mec = client.MultiEngineClient()
324 information if available.
--> 326 raise self.type, self.value, self.tb
ConnectionRefusedError: Connection was refused by other side: 111:
More information about the IPython-dev