Closed MatthewRalston closed 9 years ago
I was looking into the cloudman code, and it looks like the cloudman version you are using is a bit old. The get_file_from_public_bucket had been replaced by get_file_from_public_location on April 5th. Can you check cm/util/misc.py and check whether get_file_from_public_bucket is doing config.get or ud.get for properties like the port? I think it must be config.get() to work correctly with the cloudlaunch settings you've mentioned here: galaxyproject/cloudlaunch#46.
It's still pretty weird that it's concatenating a null value though, even the older code defaults to port 443 if None.
@nuwang you're right. The cm.tar.gz
tarball that I acquired from the "cloudman" S3 bucket uses an older version of cloudman and the file misc.py
uses get_file_from_public_bucket
and uses ud.get
instead of config.get
. I will update my tarball and boot script, relaunch, and let you know what happens.
Updating my python version (CentOS's devel copy is 2.6.6 X( ) and updating the Cloudman source solved this problem.
I am having challenges getting cloudman to launch successfully. The cm_boot.py script runs fine with cloudlaunch after some configurations and downloads the tar file "cm.tar.gz" from my bucket. This tar file was pulled from the cloudman bucket on 10/29/15. The cm_boot.py script then extracts and triggers the run.sh script of Cloudman.
I noticed that Cloudlaunch hangs when something goes wrong during Cloudman startup: Cloudlaunch #46
I get some 404's in the middle of run.sh because I do not also have snaps.yaml or persistent_data.yaml in my bucket. I have found a few mentions of "persistent_data.yaml" in the documentation, but no examples or descriptions of what I need to add there. Also, snaps.yaml is not described at all. What do I need to provided here and do I need to supply these snapshots?
The uncaught URL error occurs next during the parsing of "s3.amazonaws.com:None". My s3 and ec2 ports are both null in the userData.yaml file. The error seems to start in the method "get_file_from_public_bucket" and my default bucket is not public. The same error seems to occur when trying to fetch snaps.yaml but doesn't occur when fetching persistent_data.yaml.