Kernel Keeps restarting #329
Comments
|
There was another issue raised recently about restarting kernels. #328. As far as I gathered it was due to ZMQ as seen in this issue JuliaInterop/ZMQ.jl#83. Can you check your ZMQ version? |
|
I think that's not his issue #74 (comment) and the ZMQ issue should be fixed now. |
|
@rohitvarkey As far as I understand the ZMQ isn't my issue as @yuyichao says. FYI the version of ZMQ I'm using is 4.0.5. Installed it yesterday |
|
Does running |
|
Also, try the "debugging IJulia" tips in the README to get more output. |
|
Running ipython notebook from the command line only works for Python notebooks. I still get the same restarting problem with Julia notebooks julia> using IJulia
julia> notebook()This the output. |
|
Your comment "Running ipython notebook from the command line only works for Python notebooks" makes no sense to me. Are you using IPython 3.x? (Try If you are using IPython 2.x, you will have to do |
|
Sorry I wasn't very clear with that statement. There is a "New" button that gives the option to create Python or Julia notebooks. What I meant to say was that the Python notebook works ok. I can work on a Python notebook without the Kernel restarting and causing problems. It only restarts when I open a Julia notebook |
|
Unfortunately, the error log is not telling us much. There is a timeout waiting for the Can you try |
|
So I've just tried julia> Pkg.checkout("IJulia","master")in the Julia terminal but I get: Really not sure what to do. P.S. I forgot to mention last time that my IPython version is 3.2.0 |
|
That's because you modified IJulia above. Go to the |
|
Thanks for clarifying. I've done all of that and tried running the Julia notebook from my command line but I still get the same problem with the kernel restarting but this time with a longer error message that I can't decipher |
|
The relevant error message is: i.e. it is not responding for some reason. The long error message that follows is a crash that only occurs after IPython restarts the kernel. If I were there, at this point I'd probably start inserting some |
|
I have a similar problem. I start jupiter from the julia repl. I then can choose to create either a new Juila 0.3.10 or Python 3 notebook. In either case, the kernel crashes and resets every few seconds. If I start jupiter from the start menu (start -> Anaconda (64-bit) -> IPython (Py3.4) Notebook) I can create a new Python 3 notebook and everything is OK. creating a Julia 0.3.10 nothbook still causes a crash and reset every few seconds. so far I have tried:
I still have the same problem. Any suggestions? |
|
@cstook, what operating system are you using? Can you try the "debugging IJulia" suggestions in the README? |
|
Also, @cstook, what version of Julia are you running? (What is the output of |
|
here is the version info |
|
from command line opened a new julia notebook |
|
(The problem with these "kernel keeps restarting" issues is that they aren't much more informative than "IJulia isn't working for me". It could be any number of completely unrelated problems. Unless you can provide more technical debugging details, or we can reproduce a problem, it is hard to do much.) |
|
i have tried all the relevant suggestions in the "Troubleshooting:" section of the readme except for deleting and re adding all packages. I will try that next. from the "Debugging IJulia problems" section I have turned on the more descriptive error messages. I don't know how to cut and paste out of the julia repl. |
|
Thanks for the super quick response! I'll try to collect more information and post it here. |
|
My problem is solved! Here is what I did. deleted .julia directory this gave an error asking me to call WinRPM.update(). then start IJulia with works great! |
|
@cstook, thanks! You shouldn't have had to delete the @StefanKarpinski, @tkelman, it is disturbing to have a situation where an error message appears only once, and doesn't reappear unless the package is recreated from scratch. Can the WinRPM upgrade message be made more prominent, and repeated each time the user tries |
|
I did not see the warning about WinRPM when I tried Pkg.build("IJulia"). |
|
I'm not sure exactly what the issue is or why you'd ever need to call |
|
I updated to julia version 0.3.10. I don't remember what version I updated from. I think it was 0.3.3. It's been at least 6 months since I updated, probably longer. The problem with IJulia started the first time I used it after the update. |
|
Aha, thank you, then that does make sense. You would need to either clear out We're somewhat hamstrung here by the fact that WinRPM is pulling from an unstable development repository that can (and does) change at any time, rather than something stable and consistent that is known to work with one set of package versions like a Linux distro release. Ref JuliaPackaging/WinRPM.jl#36 Maybe to handle the "Upgraded Julia" case, we could add some state, a tagfile or something in WinRPM that saves the version of Julia it was last built with, and when the user runs with something newer it forces an update? Not sure if we could make that much more robust than what we have now. |
|
Sorry for late reply. I've been away. I've tried WinRPM.update(), and then I deleted and re-added IJulia but it still doesn't work. I'll do what you suggested and put in some println statements. This is using Julia v0.3.11. I recently downloaded Julia v0.4.0-dev as well and IJulia notebook works absolutely fine from there. I'm only having problems with v0.3.* Anyway I'll see what I can find and get back to you. |
|
One thing you could try is moving |
|
@tkelman I must admit I was sceptical at first because of the amount I've tried but your suggestion worked! Thank you very much. |
|
@tkelman, can you file a WinRPM.jl issue for automating this upgrade process? I would file one myself, but I don't really understand what the problem was here. |
|
Okay, JuliaPackaging/WinRPM.jl#45. I do want to make sure other people understand what's going on here. Opensuse upgrades their version of gcc cross-compilers occasionally, or modifies configure flags in ways that break ABI, for libstdc++ and sometimes libgfortran. That causes issues with packages that use C++ libraries from WinRPM. If Julia is built with a non-matching ABI, then dlopen of those libraries can fail giving confusing "provider packagemanager failed to satisfy dependency" errors. So we try to keep the latest released version of Julia using a matching ABI to what opensuse uses. But WinRPM apparently doesn't always upgrade installed copies of packages when newer versions or available, at least not automatically. So people here were going from a working setup with an old version of Julia and old versions of WinRPM packages that were compatible, then tried to upgrade Julia and packages (or Julia itself) wouldn't work - dlopen failures or segfaults, etc. To get a newer version of Julia working, they had to force WinRPM to update everything, or download new copies from scratch. I hope that makes sense. |
|
Thanks @tkelman for elaborating on the problem. I would also like to thank everyone, especially @stevengj, for putting up with my questions and helping me with the problem. I don't often open issues because I'm usually worried that my problem is a stupid one that has an answer somewhere but yo didn't make me feel stupid for my ignorance. I really really appreciate it. |
|
Glad we finally got it working. |
My kernel keeps restarting when I run IJulia with the following commands:
This gives the following output:
I (re)installed IJulia and ZMQ yesterday and I'm using Julia v 0.3.10.
I'm a noob to this so I apologize if the fix is blatantly in the output somewhere, it wasn't obvious to me despite following the debugging options given in the Readme.
The text was updated successfully, but these errors were encountered: