Nectar Applications - Troubleshooting R Studio

If you are using a our R studio app from the application catalogue, here are some troubleshooting tips based on errors we have seen in the past.  Of course, if these do not help, you can always contact the help desk. 

Error #1:

"Could not connect to the R session on Rstudio Server.

Error occurred during transmission (6)"

Possible Solutions:

First try reboot your instance. 

If this doesn't work, try the instructions here to reset a user state on an R Studio instance.

If you can't find the "." folders/directory mentioned in the support articles, it might all be in a folder/directory called ".rstudio" (use the command "ls -al" to see what's there, while connected to your instance via SSH) which you can rename to ".rstudio-backup" by running "mv .rstudio .rstudio-backup".

Error #2:

The previous R session terminated abnormally; LOGGED FROM: rstudio::core::Error {anonymous}::rInit(const rstudio::r::session::RInitInfo&) src/cpp/session/SessionMain.cpp:698

Possible Solution:

The database may be corrupt. Try delete the /home/<user>/.local/share/rstudio folder. This should allow Rstudio to load again. 

Error #3

If your Rstudio app or Remote Desktop log in times out or leaves a blank screen.

Possible Solution:

Your volume connected to the R studio app could be full. You will need to connect to your instance via SSH. Use the command df -h to check if the volume has 100% capacity. If it doesn, then you will need to using commands or connect to your instance via Filezilla, and remove some files to increase diskspace. Alternatively you can also expand the size of your volume, if you have quota. View the tutorial here. 

General things to try if the error isn't specifically listed:

Check if disks are full

Log in via SSH and check if the disks are full. In the terminal once connected, type in df -h to check. This will list all disks and percentage of use. If there is no 100% you are fine. If there is, you need to make space on the disk.

Reboot the instance

Try soft reboot the instance, and then if that doesn't work, hard reboot the instance. More information about these types and how to do this can be found here. To test to see if the reboot(s) have worked, try run a small dataset in R studio.