On Mon, Oct 14, 2013 at 10:06 PM, Vipin TS <vipin.ts@gmail.com> wrote:
___________________________________________________________Hi dev-team,I am trying to launch cloudman on AWS us-east-1a and I am getting the messageAll cluster services started; the cluster is ready for use. (2013-10-14 19:45:52)I am seeing some error message in the log.19:05:33 - Master starting19:05:35 - Could not find service class matching userData service entry: PSS19:05:35 - Completed the initial cluster startup process. This is a new cluster; waiting to configure the type.19:06:11 - Migration service prerequisites OK; starting the service19:06:11 - SGE service prerequisites OK; starting the service19:06:26 - Setting up SGE...19:06:40 - HTCondor service prerequisites OK; starting the service19:06:48 - Hadoop service prerequisites OK; starting the service19:07:04 - Done adding Hadoop service; service running.19:08:13 - Initializing 'Galaxy' cluster type. Please wait...19:08:14 - Error creating volume: EC2ResponseError: 400 Bad Request VolumeLimitExceededMaximum number of active volumes bytes, 20, exceeded.66659429-b0dd-4f88-b763-36fd9232d3c419:08:17 - Adding volume vol-f9c4728e (FS object for galaxy)...19:08:42 - Successfully grew file system FS object for galaxy19:08:42 - Successfully mounted file system /mnt/galaxy from /dev/xvdfIt seems that the galaxyIndices filesytem is not mounted to the instance. Also I am not able to start the postgres or Galaxy service through cloudman interface, both says that Cannot find the service.Please find the attached image. I think I am missing the galaxyIndices volume from the image,. any idea about the failure to launch the instance.Thanks,Vipin
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/