Kernel restarts and "Bad Gateway" nuisance pop-ups #1170
Comments
|
Here's a screenvideo of what I'm dealing with. This typically happens on first log in. I keep selecting things until it goes away. I think that means that the logical selection eventually works, so it does seem like some sort of race condition. in.mov |
|
This might still be related to xeus. Here are the logs from around when this was happening (you can also look on the server for the full logs). |
|
So I poked around a bit, and was able to repro this fairly easily. There were no 504 errors in the notebook log, but I do see 504 errors in the nginx log and the proxy process. In the proxy process, I can see: And that correlates with the entries from the nginx log: So it looks like I don't have the log lines from xeus-sql you're seeing yet. |
|
Aha, maybe jupyter/notebook#6164 is what you are experiencing? |
|
Maybe 2i2c-org/utexas-image#7 can fix it, as jupyter/notebook#6221 has been merged. However, the current image is on notebook 6.3.0, so I've upgraded it to latest in 2i2c-org/utexas-image#7. Let's see if that fixes it. |
yuvipanda
added a commit
to yuvipanda/repo2docker
that referenced
this issue
Apr 8, 2022
- We should stop auto updating 3.6 now, so we can move on to newer notebook packages - a new notebook version ought to fix issues like 2i2c-org/infrastructure#1170 for example. - No longer explicitly pin nbconvert, as whatever version notebook brings in should be sufficient. - Bump up ipywidgets and jupyterlab while we're at it. - No longer pin jupyterhub-singleuser either, as that too works properly with 3.7
|
Ok, so i deployed the newly built image to the hub, and it looks like it fixed the annoying popups! You also got RStudio for free :) Let me know if this recurs, @jameshowison! jupyterhub/repo2docker#1149 should also fix this longer term for other hubs. |
|
Great. So far so good. I'll let you know if we see any recurrences, but this sure seems well diagnosed. And I'm stoked that this helps with other images/upstream :) |
yuvipanda
added a commit
to yuvipanda/repo2docker
that referenced
this issue
Apr 11, 2022
- We should stop auto updating 3.6 now, so we can move on to newer notebook packages - a new notebook version ought to fix issues like 2i2c-org/infrastructure#1170 for example. - No longer explicitly pin nbconvert, as whatever version notebook brings in should be sufficient. - Bump up ipywidgets and jupyterlab while we're at it. - No longer pin jupyterhub-singleuser either, as that too works properly with 3.7
|
@choldgraf tweeted about this https://twitter.com/choldgraf/status/1513612334815535106 |
|
Love it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
On the utexas hub I'm having some nuisance issues causing popups about Kernel restarts. This was one of the issues discussed in #1021 but we thought it was just xsql related. I haven't used xsql for weeks and it's still happening.
It primarily happens on startup where I get the pop up shown in #1021 (comment) I think this is related to files that were open when the hub suspended. Perhaps that is why it is hard to replicate, need to have "open" files with running kernels?
Before the Bad Gateway message I see a message something like "Kernel is not running, select kernel" but whichever one I select from the drop-down it pops up a few more times before disappearing.
I'll try to capture it in action with screenshots or a screencast.
As I say this is more of a nuisance than a big issue, but it's not a great look when demoing.
Proposal
No response
Updates and actions
No response
The text was updated successfully, but these errors were encountered: