Discussion:
[spyder] ipython crash on startup: "It seems the kernel died unexpectedly."
Raimar
2015-06-09 10:35:56 UTC
Permalink
Hi,


today when I restarted spyder I could not launch the ipython console
anymore:

"It seems the kernel died unexpectedly. Use 'Restart kernel' to continue
using this console."


This is repeated over and over again. I'm on Gentoo Linux, spyder 2.3.4,
Python 2.7.10 64bits, Qt 4.8.6, PyQt4 (API v2) 4.11.3. These are my
optional dependencies:

IPython >=1.0 : 3.1.0 (OK)
jedi >=0.8.1 : None (NOK)
matplotlib >=1.0: 1.4.3 (OK)
pandas >=0.13.1 : 0.16.1 (OK)
pep8 >=0.6 : None (NOK)
psutil >=0.3 : 2.2.1 (OK)
pyflakes >=0.5.0: 0.8.1 (OK)
pygments >=1.6 : 2.0.2 (OK)
pylint >=0.25 : None (NOK)
rope >=0.9.2 : 0.10.2 (OK)
sphinx >=0.6.6 : 1.3.1 (OK)
sympy >=0.7.3 : None (NOK)
zmq >=2.1.11 : 14.6.0 (OK)

There is nothing suspicious shown in the kernel log. The internal console
only keeps repeating

WARNING:root:kernel died: 3.00297999382


Running a standalone "ipython qtconsole" works just fine. What is strange:
I can even connect to the supposedly died kernel by running ipython
qtconsole --existing kernel-28216.json in
~/.ipython/profile_default/security. When I execute a statement in the
spyder editor like b=5 by pressing F9, I can access this variable in the
external ipython console. This lets me believe that the kernel has not
really died, but spyder just thinks it has. However, the ipython console
becomes unusable by the repeated error messages.

I tried to delete the ipython configuration file, and also "spyder
--default" and "spyder --reset", this did not help. Yesterday, a system
update upgraded the python packages simplejson, cffi, cryptography and
reinstalled pyzmq because of some internal package changes. I tried to
downgrade those packages, but it did not solve my problem.


How can I obtain more useful debugging output from spyder, to determine
where the crash actually happens?



Thanks for your help!
Raimar
--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
David Verelst
2015-06-19 12:32:09 UTC
Permalink
As reported by Alex, downgrading zeromq to 4.0.5 works for him.
An update to zeromq-4.1.2 resolved the issue for me as well (Arch Linux).
Seems zeromq 4.0.6 has some bugs/issues in combination with IPython?

Regards,
David
Post by Raimar
Hi,
today when I restarted spyder I could not launch the ipython console
"It seems the kernel died unexpectedly. Use 'Restart kernel' to continue
using this console."
This is repeated over and over again. I'm on Gentoo Linux, spyder 2.3.4,
Python 2.7.10 64bits, Qt 4.8.6, PyQt4 (API v2) 4.11.3. These are my
IPython >=1.0 : 3.1.0 (OK)
jedi >=0.8.1 : None (NOK)
matplotlib >=1.0: 1.4.3 (OK)
pandas >=0.13.1 : 0.16.1 (OK)
pep8 >=0.6 : None (NOK)
psutil >=0.3 : 2.2.1 (OK)
pyflakes >=0.5.0: 0.8.1 (OK)
pygments >=1.6 : 2.0.2 (OK)
pylint >=0.25 : None (NOK)
rope >=0.9.2 : 0.10.2 (OK)
sphinx >=0.6.6 : 1.3.1 (OK)
sympy >=0.7.3 : None (NOK)
zmq >=2.1.11 : 14.6.0 (OK)
There is nothing suspicious shown in the kernel log. The internal console
only keeps repeating
WARNING:root:kernel died: 3.00297999382
I can even connect to the supposedly died kernel by running ipython
qtconsole --existing kernel-28216.json in
~/.ipython/profile_default/security. When I execute a statement in the
spyder editor like b=5 by pressing F9, I can access this variable in the
external ipython console. This lets me believe that the kernel has not
really died, but spyder just thinks it has. However, the ipython console
becomes unusable by the repeated error messages.
I tried to delete the ipython configuration file, and also "spyder
--default" and "spyder --reset", this did not help. Yesterday, a system
update upgraded the python packages simplejson, cffi, cryptography and
reinstalled pyzmq because of some internal package changes. I tried to
downgrade those packages, but it did not solve my problem.
How can I obtain more useful debugging output from spyder, to determine
where the crash actually happens?
Thanks for your help!
Raimar
--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Carlos Córdoba
2015-06-19 13:46:12 UTC
Permalink
Hi David,

Yes, zeromq 4.0.6 broke the kernel heartbeat. Please see our Github
issue #2485 for details:

https://github.com/spyder-ide/spyder/issues/2485

Cheers,
Carlos
Post by David Verelst
As reported by Alex, downgrading zeromq to 4.0.5 works for him.
An update to zeromq-4.1.2 resolved the issue for me as well (Arch Linux).
Seems zeromq 4.0.6 has some bugs/issues in combination with IPython?
Regards,
David
Hi,
today when I restarted spyder I could not launch the ipython
"It seems the kernel died unexpectedly. Use 'Restart kernel' to
continue using this console."
This is repeated over and over again. I'm on Gentoo Linux, spyder
2.3.4, Python 2.7.10 64bits, Qt 4.8.6, PyQt4 (API v2) 4.11.3.
IPython >=1.0 : 3.1.0 (OK)
jedi >=0.8.1 : None (NOK)
matplotlib >=1.0: 1.4.3 (OK)
pandas >=0.13.1 : 0.16.1 (OK)
pep8 >=0.6 : None (NOK)
psutil >=0.3 : 2.2.1 (OK)
pyflakes >=0.5.0: 0.8.1 (OK)
pygments >=1.6 : 2.0.2 (OK)
pylint >=0.25 : None (NOK)
rope >=0.9.2 : 0.10.2 (OK)
sphinx >=0.6.6 : 1.3.1 (OK)
sympy >=0.7.3 : None (NOK)
zmq >=2.1.11 : 14.6.0 (OK)
There is nothing suspicious shown in the kernel log. The internal
console only keeps repeating
WARNING:root:kernel died: 3.00297999382
Running a standalone "ipython qtconsole" works just fine. What is
strange: I can even connect to the supposedly died kernel by
running ipython qtconsole --existing kernel-28216.json in
~/.ipython/profile_default/security. When I execute a statement in
the spyder editor like b=5 by pressing F9, I can access this
variable in the external ipython console. This lets me believe
that the kernel has not really died, but spyder just thinks it
has. However, the ipython console becomes unusable by the repeated
error messages.
I tried to delete the ipython configuration file, and also "spyder
--default" and "spyder --reset", this did not help. Yesterday, a
system update upgraded the python packages simplejson, cffi,
cryptography and reinstalled pyzmq because of some internal
package changes. I tried to downgrade those packages, but it did
not solve my problem.
How can I obtain more useful debugging output from spyder, to
determine where the crash actually happens?
Thanks for your help!
Raimar
--
You received this message because you are subscribed to the Google
Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Loading...