Closed ryanlovett closed 5 years ago
I think this is related to #44 as well?
Once we switch to simpervisor in nbserverproxy, maybe we can revert to using rsession? I don't think this should be configurable if we can find a proper automatic solution
If I simply switch I am getting:
28 Dec 2018 21:56:27 [rsession-yuvipanda] ERROR system error 2 (No such file or directory) [path=]; OCCURRED AT: rstudio::core::Error rstudio::r::session::discoverR(rstudio::r::session::RLocations*) /home/ubuntu/rstudio/src/cpp/r/session/RDiscovery.cpp:62; LOGGED FROM: int main(int, char* const*) /home/ubuntu/rstudio/src/cpp/session/SessionMain.cpp:1841
Fixed by 6db4a162bfa2e35e65e6b9f06193a4a0f778a118.
This post was useful for me to resolve issues with the /tmp/rstudio-server/secure-cookie-key: https://stackoverflow.com/questions/52381661/how-can-i-use-anaconda-environments-with-rstudio-server/52381662
The change to rserver causes this extension to fail on multi-user systems. When rserver starts, it create /tmp/rstudio-server/secure-cookie-key. If a second user attempts to write there, rserver will fail. This is not configurable within rstudio.
I'm thinking of introducing a traitlet that lets administrators choose between rsession and rserver. Thoughts?