[IPython-dev] debugging remote engine death

Moritz Beber moritz.beber at gmail.com
Wed Oct 22 18:12:59 EDT 2014


On Thu, Oct 23, 2014 at 12:05 AM, MinRK <benjaminrk at gmail.com> wrote:

> engines logs are identified by the process ID (not a great choice, I
> think). The engine ID should be logged, so you can see which engine had
> which ID:
>     grep 'registration' ~/.ipython/profile_default/log/ipengine-*.log
> Not exactly awesome, but it should get you to the right file, at least.
> -MinRK
Unfortunately, not quite. This gives me the id used internally but not the
uuid of the engine given in the RemoteError.

rror: EngineError(Engine 'bd38ee8e-ad65-41af-944d-a9ea15162c03' died while
running task u'a392e922-e01f-41a7-9e5e-def08ba61da8')"


".ipython/profile_default/log/ipengine-16101.log:2014-10-21 18:37:07.225
[IPEngineApp] Completed registration with id 0"

Thank you for looking into it, though.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20141023/856c2eb0/attachment.html>

More information about the IPython-dev mailing list