Re: [galaxy-dev] [galaxy-user] Problem using Galaxy on the cloud
Hi Jan, Since this question is about a Cloud installation, I am going to forward your question over to the galaxy-dev@bx.psu.edu mailing list so that the development community will have a better chance of seeing it and providing feedback. http://wiki.g2.bx.psu.edu/Support#Mailing_Lists Thanks! Jen Galaxy team On 3/6/12 1:44 PM, Jan R McDowell wrote:
Hi all, I have been trying to get an instance of Galaxy going on the EC2. I have no problem going through BioCloudCentral and getting an instance going. I can also successfully load my data from an S2 bucket into Galaxy. The problem occurs when I try to use velveth. I always says 'job waiting to run'. As a matter of curiosity, I then used SSH to get into CloudBioLinux, which worked. However, when I try to use NX to get the virtual desktop going I get the message usr/bin/nxserver: line 381: echo: write error: No space left on device.
Using the df -h command, I get:
Filesystem Size Used Avail Use% Mounted on /dev/xvda1 20G 19G 0 100% / udev 8.4G 4.0K 8.4G 1% /dev tmpfs 3.4G 660K 3.4G 1% /run none 5.0M 0 5.0M 0% /run/lock none 8.4G 0 8.4G 0% /run/shm /dev/xvdb 404G 202M 383G 1% /mnt /dev/xvdg1 700G 654G 47G 94% /mnt/galaxyIndices /dev/xvdg2 10G 1.7G 8.4G 17% /mnt/galaxyTools /dev/xvdg3 200G 11G 190G 6% /mnt/galaxyData
So, I guess my question as a new user is: How do I point Galaxy and CloudBioLinux to all of this unused space? I assume the problem is with the /dev/xvda1 that is 100% full. I am obviously doing something silly and/or missing a really big step. Any help would be greatly appreciated.
Many thanks in advance, Jan
___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at:
-- Jennifer Jackson http://usegalaxy.org http://galaxyproject.org/wiki/Support
Jan; Glad to hear you got Galaxy running successfully. It sounds like everything is good to go once we sort out the disk space issue.
However, when I try to use NX to get the virtual desktop going I get the message usr/bin/nxserver: line 381: echo: write error: No space left on device.
Using the df -h command, I get:
Filesystem Size Used Avail Use% Mounted on /dev/xvda1 20G 19G 0 100% / udev 8.4G 4.0K 8.4G 1% /dev tmpfs 3.4G 660K 3.4G 1% /run none 5.0M 0 5.0M 0% /run/lock none 8.4G 0 8.4G 0% /run/shm /dev/xvdb 404G 202M 383G 1% /mnt /dev/xvdg1 700G 654G 47G 94% /mnt/galaxyIndices /dev/xvdg2 10G 1.7G 8.4G 17% /mnt/galaxyTools /dev/xvdg3 200G 11G 190G 6% /mnt/galaxyData
So, I guess my question as a new user is: How do I point Galaxy and CloudBioLinux to all of this unused space?
By default CloudMan will put files into /mnt/galaxyData. However, as you noticed the main filesystem got filled up at some point. Could this have happened while transferring files over from S3? Are there files in your home directory that you could delete or move to /mnt/galaxyData to free up space? CloudBioLinux and CloudMan shouldn't put a large number of files in the root directory, but when the root filesystem is full it's going to be very unhappy. Once you manually clear up some room there hopefully things will run smoother. If that doesn't help let us know and we can dig into it further. Thanks, Brad
participants (2)
-
Brad Chapman
-
Jennifer Jackson