[IPython-user] Fwd: TaskClient problems

Brian Granger ellisonbg.net@gmail....
Thu Apr 2 19:11:17 CDT 2009


This is extremely odd and I have not seen this behavior before.  Is it
possible that you can try a different Python on OS X, like the built
in one?  Is it possible you are using packages compiled for a
different Python?  Can you begin to check things like PATH, PYTHONPATH
and make sure you are getting the right python and various packages?
I have never tried this on macports.

Brian

On Thu, Apr 2, 2009 at 5:02 PM, Mike Trumpis <mtrumpis@gmail.com> wrote:
> oops.. I misunderstood what you wanted me to run. When I start up the
> controller/engines that way, and then run the code, I do get the exact
> same errors.
>
> 2009-04-02 16:58:42-0700 [-]
> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/IPython/kernel/twistedutil.py:42:
> exceptions.DeprecationWarning: Reactor already running! This behavior
> is deprecated since Twisted 8.0
> Fatal Python error: PyEval_RestoreThread: NULL tstate
> Abort trap
>
> Mike
>
> On Thu, Apr 2, 2009 at 4:46 PM, Brian Granger <ellisonbg.net@gmail.com> wrote:
>> What resolved the issue?
>>
>> Brian
>>
>> On Thu, Apr 2, 2009 at 4:25 PM, Mike Trumpis <mtrumpis@gmail.com> wrote:
>>> seems to work.. here's the output:
>>>
>>> puma:~ miket$ ipcontroller
>>> 2009-04-02 16:23:28-0700 [-] Log opened.
>>> 2009-04-02 16:23:28-0700 [-] foolscap.pb.Listener starting on 63775
>>> 2009-04-02 16:23:28-0700 [-] foolscap.pb.Listener starting on 63776
>>> 2009-04-02 16:23:28-0700 [-] Adapting Controller to interface: multiengine
>>> 2009-04-02 16:23:28-0700 [-] Saving furl for interface [multiengine]
>>> to file: /Users/miket/.ipython/security/ipcontroller-mec.furl
>>> 2009-04-02 16:23:28-0700 [-] Adapting Controller to interface: task
>>> 2009-04-02 16:23:28-0700 [-] Saving furl for interface [task] to file:
>>> /Users/miket/.ipython/security/ipcontroller-tc.furl
>>> 2009-04-02 16:23:28-0700 [-] Saving furl for the engine to file:
>>> /Users/miket/.ipython/security/ipcontroller-engine.furl
>>> 2009-04-02 16:23:28-0700 [-]
>>> twisted.internet.protocol.DatagramProtocol starting on 50966
>>> 2009-04-02 16:23:28-0700 [-] Starting protocol
>>> <twisted.internet.protocol.DatagramProtocol instance at 0x2ad1be8>
>>> 2009-04-02 16:23:28-0700 [-]
>>> twisted.internet.protocol.DatagramProtocol starting on 50967
>>> 2009-04-02 16:23:28-0700 [-] Starting protocol
>>> <twisted.internet.protocol.DatagramProtocol instance at 0x2b80fd0>
>>> 2009-04-02 16:23:28-0700 [-] (Port 50966 Closed)
>>> 2009-04-02 16:23:28-0700 [-] Stopping protocol
>>> <twisted.internet.protocol.DatagramProtocol instance at 0x2ad1be8>
>>> 2009-04-02 16:23:28-0700 [-] (Port 50967 Closed)
>>> 2009-04-02 16:23:28-0700 [-] Stopping protocol
>>> <twisted.internet.protocol.DatagramProtocol instance at 0x2b80fd0>
>>> 2009-04-02 16:23:32-0700 [-] registered engine with id: 0
>>> 2009-04-02 16:23:32-0700 [-] distributing Tasks
>>>
>>> puma:~ miket$ ipengine
>>> 2009-04-02 16:23:32-0700 [-] Log opened.
>>> 2009-04-02 16:23:32-0700 [-] Using furl file:
>>> /Users/miket/.ipython/security/ipcontroller-engine.furl
>>> 2009-04-02 16:23:32-0700 [Negotiation,client] engine registration
>>> succeeded, got id: 0
>>>
>>> Thanks..
>>>
>>> Mike
>>>
>>>
>>> On Thu, Apr 2, 2009 at 3:50 PM, Brian Granger <ellisonbg.net@gmail.com> wrote:
>>>> Can you try to start the controller and engine separately in 2
>>>> terminals by doing:
>>>>
>>>> $ ipcontroller
>>>>
>>>> then
>>>>
>>>> $ ipengine
>>>>
>>>> And don't background these with & so you can just see what is going
>>>> on.  Let me know if that works.
>>>>
>>>> Brian
>>>>
>>>>
>>>> On Thu, Apr 2, 2009 at 2:54 PM, M Trumpis <mtrumpis@berkeley.edu> wrote:
>>>>> I'll try and see on Mac OS, but I do see the same thing in Ubuntu with
>>>>> twisted 8.1.0
>>>>>
>>>>> There is no weird stdout when starting up ipcluster, but the engines
>>>>> do shut down in the same way, and the twisted exception is pretty much
>>>>> the same:
>>>>>
>>>>> 2009-04-02 13:58:18-0700 [-] Log opened.
>>>>> 2009-04-02 13:58:18-0700 [-] Using furl file:
>>>>> /home/mike/.ipython/security/ipcontroller-engine.furl
>>>>> 2009-04-02 13:58:18-0700 [Negotiation,client] engine registration
>>>>> succeeded, got id: 0
>>>>> 2009-04-02 13:58:36-0700 [-]
>>>>> /usr/lib/python2.5/site-packages/twisted/internet/base.py:1047:
>>>>> exceptions.DeprecationWarning: Reactor already running! This behavior
>>>>> is deprecated since Twisted 8.0
>>>>>
>>>>> I actually think the engines shut down when doing a mec.push in this
>>>>> case, instead of anything with the TaskClient.
>>>>>
>>>>> In Ubuntu, I rolled back to the 0.9.1 release and was able to fire off
>>>>> the jobs successfully.
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>> On Thu, Apr 2, 2009 at 2:30 PM, Fernando Perez <fperez.net@gmail.com> wrote:
>>>>>> On Thu, Apr 2, 2009 at 2:23 PM, Yichun Wei <yichun.wei@gmail.com> wrote:
>>>>>>> I had the impression that I needed Twised 8.1 to have my code work.
>>>>>>> The warning about reactor.run reminds me that it might be related.
>>>>>>> Just an idea, not sure if it helps. -yichun
>>>>>>
>>>>>> Good point!  On my ubuntu box, I have this too:
>>>>>>
>>>>>> In [2]: twisted.__version__
>>>>>> Out[2]: '8.1.0'
>>>>>>
>>>>>>
>>>>>> Mike, could you try updating your twisted and seeing if that helps?
>>>>>>
>>>>>> f
>>>>>> _______________________________________________
>>>>>> IPython-user mailing list
>>>>>> IPython-user@scipy.org
>>>>>> http://mail.scipy.org/mailman/listinfo/ipython-user
>>>>>>
>>>>> _______________________________________________
>>>>> IPython-user mailing list
>>>>> IPython-user@scipy.org
>>>>> http://mail.scipy.org/mailman/listinfo/ipython-user
>>>>>
>>>>
>>>
>>
>


More information about the IPython-user mailing list