Internal server error 500 "could not start rstudio in time"

Notebook
1

Hi,

I encountered a problem when launching the binder from

The problem is that I get an internal server error 500

grafik
grafik1171×265 13.4 KB

Maybe this could be fixed if I use holepunch to recreate the runtime etc. But I am looking for a solution that allows me (and colleagues) to create long-term sustainable notebooks. Therefore I want to understand what went wrong with this one that is (at this point) 7 Months old.

Thanks! :slight_smile:
Jürgen

2

If you launch your container, then remove the /rstudio component you’ll reach the default JupyterLab interface where you can launch a terminal. The logs from the container are copied into a file ~/.jupyer-server-log.txt:

rserver: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
rserver: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
rserver: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
rserver: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
rserver: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
...

I don’t know what the root cause is though

1 Like
3

If I am understanding your post and you haven’t done anything & it was working 7 months ago, it probably isn’t anything you did.
RStudio from launched sessions using environmental.yml as the configuration file stopped working, too, see here and the rest of the thread below there.
The root cause hasn’t been found but this adds another piece to the puzzle.

I had posted a workaround for the one with environment.yml to allow accessing the RStudio interface; however, your set-up does not match that and I don’t see a way to apply the trick in your case.

1 Like