Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 Error Jupyter notebook #818

Closed
kstory8 opened this issue Feb 13, 2019 · 4 comments
Closed

500 Error Jupyter notebook #818

kstory8 opened this issue Feb 13, 2019 · 4 comments

Comments

@kstory8
Copy link

kstory8 commented Feb 13, 2019

I tried to launch a jupyter notebook from a custom docker image. This failed (presumably because of permissions issues accessing the particular GCR). Now, jupyterhub keeps failing with the following error:

500 : Internal Server Error
Failed to reach your server. Please try again later. Contact admin if the issue persists.

You can try restarting your server from the home page.

@kstory8
Copy link
Author

kstory8 commented Feb 13, 2019

screen shot 2019-02-12 at 4 35 34 pm

@gaoning777
Copy link
Contributor

gaoning777 commented Feb 13, 2019

instructions on customizing jupyterhub and notebook images:
https://github.com/kubeflow/kubeflow/tree/master/components/jupyterhub
https://github.com/kubeflow/kubeflow/tree/master/components/jupyterhub#notebook-image

If you've already followed the instructions on the above link to create notebook images, create a secret with the credentials and add it to the jupyterhub serviceaccount:
kubectl patch -n kubeflow serviceaccount jupyter -p '{"imagePullSecrets": [{"name": "secretname"}]}'

@jlewi Can you offer more instructions or the user practice to customize notebook images?

@jlewi
Copy link
Contributor

jlewi commented Feb 17, 2019

Can you provide the full JupyterHub logs?
I would also suggest deleting the JupyterHub pod to force it to restart.
You can also check for any jupyter pods and delete those.

@vicaire
Copy link
Contributor

vicaire commented Mar 26, 2019

Resolving since this issue has been inactive for a while. Please re-open if needed.

@vicaire vicaire closed this as completed Mar 26, 2019
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
… the task (kubeflow#818)

* fix(pylint): detect failures and erros associated with the task

* do not break if neither failure or failure element doesn't have message attribute

* send xml files to artifacts folder to get detected by spyglass

* parse all the tests to xml

* path for pytest gets added from generate_xml function

* Revert "path for pytest gets added from generate_xml function"

This reverts commit 8be433afb7f93fa9017dad1a7870d9929c4d4e7b.

* add only: path for pytest gets added from generate_xml function
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
* Return 503 from healthhandler when model is not ready

If the model is not marked ready, then don't return 200 from health
check handler, return a 503 instead so it can be used for kubernetes
readiness probe

* Fix lint warning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants