Revision history [back]

click to hide/show revision 1
initial version

Vish, now my first instance is not running anymore. I think the problem is that the instance is trying to access this url and after a while it changes to CRITICAL and it stays there forever. The range of IPs is unique and they are dedicated to the instances only. I am also seeing a progressive IP # on new instances but all of them try to access that url. I have entered the iptables cmd on the compute node.

see the beginning and the end of the attached log:

cloud-init start running: Tue, 01 Mar 2011 03:36:54 +0000. up 1.96 seconds 2011-03-01 03:36:56,243 -[WARNING]: waiting for metadata service at

2011-03-01 03:36:56,244 -[WARNING]: 03:36:56 [ 1/100]: url error [timed out]

2011-03-01 03:36:57,250 -[WARNING]: 03:36:57 [ 2/100]: url error [[Errno 113] No route to host]

2011-03-01 03:37:00,256 -[WARNING]: 03:37:00 [ 3/100]: url error [timed out]


2011-03-01 04:17:48,760 -[WARNING]: 04:17:48 [100/100]: url error [timed out]

2011-03-01 04:18:08,782 -[CRITICAL]: giving up on md after 1208 seconds

Traceback (most recent call last): File "/usr/bin/cloud-init-cfg", line 116, in <module> main() File "/usr/bin/cloud-init-cfg", line 63, in main cc = cloudinit.CloudConfig.CloudConfig(cfg_path) File "/usr/lib/python2.6/dist-packages/cloudinit/CloudConfig/", line 35, in __init__ File "/usr/lib/python2.6/dist-packages/cloudinit/", line 270, in get_data_source log.debug("did not find data source from %s" % dslist) TypeError: not all arguments converted during string formatting

======== here is my instance: euca-describe-instances RESERVATION r-gvmuusmn simple_cloud default INSTANCE i-00000002 ami-zjnxlmfr running mykey (simple_cloud, cc1) 0 m1.small 2011-03-01T03:36:25Z nova