Dear Bioconductor,
I am attempting to follow the instructions here https://www.bioconductor.org/help/bioconductor-cloud-ami/#configuring_starcluster to configure a StarCluster for running the Bioconductor AMI as a cluster.
But I am getting an error when I try to start a cluster. The error is a Python stack trace which seems to indicate AWS cloud refused to authenticate my key. I tried creating a key with "starcluster createkey" and the same error turned up.
(I couldn't create a key, so I tried using my regular AWS key and neither seems to work.)
Is this a StarCluster problem? Should I send them a question? Am I think only one it happens to? Do you still recommend using StarCluster? Is it still an active project? (The fact that I had to install Python 2.7 to build it is not encouraging.) Is there a newer better way to do this?
thanks,
- Sam
Sorry, just saw this. I got the AMI to work with the latest StarCluster version 0.95.6 yesterday.
But now I have a problem with connecting to Rstudio Server.
I can connect to rstudio server on a slave node just fine, but I can't connect to it on the master node. On the master node, I get the login screen and I enter ubuntu/bioc and it spins its wheel for a bit, then it says "Studio initialization error" and "Unable to connect to service."
So I logged into the master node and tried to restart. But I am getting an error with the /etc/rstudio/rserver.conf file. When I do "rstudio-server verify-installation" it says:
"Error reading /etc/rstudio/rserver.conf: option 'path' cannot be specified more than once"
The issue is that there are multiple identical lines in /etc/rstudio/rserver.conf that look like this:
rsession-path=/usr/local/bin/setup_r_mpi.sh
(It looks like every time I attempt to connect, a few more of these lines show up.)
Do you have any insight on this?
thanks,
- Sam