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

Slicer Kernel cannot start #72

Closed
bveeni opened this issue May 5, 2022 · 5 comments
Closed

Slicer Kernel cannot start #72

bveeni opened this issue May 5, 2022 · 5 comments

Comments

@bveeni
Copy link

bveeni commented May 5, 2022

Hi everyone,

I am facing the issue of "unable to start kernel for slicer" , giving logs as

Switch to module:  "Welcome"
Loading Slicer RC file [/home/sliceruser/.slicerrc.py]
Jupyter connection file: [/home/sliceruser/.local/share/jupyter/runtime/kernel-2c7279ff-433a-43c2-88d2-f15696ba54fb.json]
error: [/home/sliceruser/Slicer/bin/SlicerApp-real] exit abnormally - Report the problem.

I am running docker image for 3D slicer
docker run -p 8888:8888 -p49053:49053 -v "$PWD":/home/sliceruser/work --rm -ti lassoan/slicer-notebook:2021-10-15-b3077c2
It works fine on my local machine (windows) and I am able to use 3D slicer via Jupiter notebook.
However, its not working on my remote VM (Ubuntu 18.04). Whenever, I try to open Slicer in notebook, it prompts message "kernel appear to die and restart automatically" but never succeed to start.
Any guidance would be great.
Here is image attached of logs
image

Thanks

@lassoan
Copy link
Contributor

lassoan commented May 5, 2022

Could you try with the latest image - lassoan/slicer-notebook:latest?

@bveeni
Copy link
Author

bveeni commented May 5, 2022

Could you try with the latest image - lassoan/slicer-notebook:latest?

Hi,
With latest image also, it didn't worked.
Also, is there any chance of conflict on network, since I am connected to organization VPN for working on remote VMS for this case.
Along with above mentioned logs, after few times of restarting, this error message pops up as shown in image.
image
Thanks

@lassoan
Copy link
Contributor

lassoan commented May 5, 2022

I don't know what can cause a docker image not run in a certain system. I would expect that docker takes care of creating a reproducible environment.

Are the ports accessible and the current directory ($PWD) writable?

@bveeni
Copy link
Author

bveeni commented May 5, 2022

I don't know what can cause a docker image not run in a certain system. I would expect that docker takes care of creating a reproducible environment.

Are the ports accessible and the current directory ($PWD) writable?

Yes they are all good.

@lassoan
Copy link
Contributor

lassoan commented Jun 26, 2022

I'm closing this issue because we got stuck for a long time and it is not likely that we can make progress with it.

@lassoan lassoan closed this as completed Jun 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants