Can not access second and next instances via ssh/ping etc
Launched an instance, runs OK, I can access it via ssh/ping etc. Launch a second instance from the same image and I can not access it via ssh/ping etc. Both instances are running OK.
On the second instance console shows:
=======
2011-02-25 16:09:20,916 - DataSourceEc2.
2011-02-25 16:09:20,916 - DataSourceEc2.
2011-02-25 16:50:42,117 - DataSourceEc2.
2011-02-25 16:10:26,875 - DataSourceEc2.
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
cc = cloudinit.
File "/usr/lib/
self.
File "/usr/lib/
log.debug("did not find data source from %s" % dslist)
TypeError: not all arguments converted during string formatting
=======
I have not been able to access any new instance via ssh/ping after the first one which is still running OK.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- arturo lorenzo
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Please paste your nova.conf and your logfiles (I think the logs of nova-network and nova-compute are interesting in this case) to http://
Revision history for this message
|
#2 |
here is the nova.conf file, failed to post the logs using pasted.
--dhcpbridge_
--dhcpbridge=
--logdir=
--state_
--verbose
--sql_connectio
--s3_host=
--rabbit_
--ec2_host=
--ec2_url=http://
--network_
--fixed_
--flat_
--flat_
--dns_server=
--flat_
--network_size=16
--fixed_
thanks
Revision history for this message
|
#3 |
are you seeing the second ip get leased properly? (You should see leased reports every two minutes from each instance in nova-network)
It seems like you might have an ip conflict. If you describe_instances do they show that they have different ips?
Are you sure there isn't an old instance (or another machine on the network) trying to claim the same ip?
Vish
On Feb 28, 2011, at 6:03 AM, arturo lorenzo wrote:
> Question #146894 on OpenStack Compute (nova) changed:
> https:/
>
> Status: Needs information => Open
>
> arturo lorenzo gave more information on the question:
> here is the nova.conf file, failed to post the logs using pasted.
> --dhcpbridge_
> --dhcpbridge=
> --logdir=
> --state_
> --verbose
> --sql_connectio
> --s3_host=
> --rabbit_
> --ec2_host=
> --ec2_url=http://
> --network_
> --fixed_
> --flat_
> --flat_
> --dns_server=
> --flat_
> --network_size=16
> --fixed_
>
> thanks
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).
Revision history for this message
|
#4 |
Vish,
now my first instance is not running anymore. I think the problem is that the instance is trying to access this url http://
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 - DataSourceEc2.
2011-03-01 03:36:56,244 - DataSourceEc2.
2011-03-01 03:36:57,250 - DataSourceEc2.
2011-03-01 03:37:00,256 - DataSourceEc2.
......
2011-03-01 04:17:48,760 - DataSourceEc2.
2011-03-01 04:18:08,782 - DataSourceEc2.
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
cc = cloudinit.
File "/usr/lib/
self.
File "/usr/lib/
log.debug("did not find data source from %s" % dslist)
TypeError: not all arguments converted during string formatting
========
here is my instance:
euca-describe-
RESERVATION r-gvmuusmn simple_cloud default
INSTANCE i-00000002 ami-zjnxlmfr 13.141.230.98 13.141.230.98 running mykey (simple_cloud, cc1) 0 m1.small 2011-03-
thanks!
Revision history for this message
|
#5 |
The iptables command should be on the network node, and it is done automatically by flatdhcp. Also, you may need to give 169.254.169.254 to the network node to allow some guests to reach it properly (this generally happens with desktop images).
for example:
ip addr add 169.254.169.254/32 link local dev br100
On Feb 28, 2011, at 8:43 PM, arturo lorenzo wrote:
> Question #146894 on OpenStack Compute (nova) changed:
> https:/
>
> Status: Answered => Open
>
> arturo lorenzo is still having a problem:
> Vish,
> now my first instance is not running anymore. I think the problem is that the instance is trying to access this url http://
> 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 - DataSourceEc2.
>
> 2011-03-01 03:36:56,244 - DataSourceEc2.
> 1/100]: url error [timed out]
>
> 2011-03-01 03:36:57,250 - DataSourceEc2.
> 2/100]: url error [[Errno 113] No route to host]
>
> 2011-03-01 03:37:00,256 - DataSourceEc2.
> 3/100]: url error [timed out]
>
> ......
>
> 2011-03-01 04:17:48,760 - DataSourceEc2.
> [100/100]: url error [timed out]
>
> 2011-03-01 04:18:08,782 - DataSourceEc2.
> after 1208 seconds
>
> Traceback (most recent call last):
> File "/usr/bin/
> main()
> File "/usr/bin/
> cc = cloudinit.
> File "/usr/lib/
> self.cloud.
> File "/usr/lib/
> log.debug("did not find data source from %s" % dslist)
> TypeError: not all arguments converted during string formatting
>
> ========
> here is my instance:
> euca-describe-
> RESERVATION r-gvmuusmn simple_cloud default
> INSTANCE i-00000002 ami-zjnxlmfr 13.141.230.98 13.141.230.98 running mykey (simple_cloud, cc1) 0 m1.small 2011-03-
>
> thanks!
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).
Revision history for this message
|
#6 |
Still can't run an instance. I have reinstalled nova from zero and I am using this nova.conf:
--dhcpbridge_
--dhcpbridge=
--logdir=
--state_
--verbose
--sql_connectio
--s3_host=
--rabbit_
--ec2_host=
--ec2_url=http://
--network_
--fixed_
--flat_
--flat_
--flat_
--fixed_
--network_size=16
--dns_server=
and when I run an instance I get this:
=======
2011-03-01 20:53:28,561 DEBUG nova.rpc [-] Initing the Adapter Consumer for compute from (pid=8161) __init__ /usr/lib/
2011-03-01 20:53:28,607 DEBUG nova.rpc [-] Initing the Adapter Consumer for compute.ubuntu-svr1 from (pid=8161) __init__ /usr/lib/
2011-03-01 21:09:47,520 DEBUG nova.rpc [-] received {u'_context_
2011-03-01 21:09:47,521 DEBUG nova.rpc [-] unpacked context: {'timestamp': u'2011-
2011-03-01 21:09:47,581 DEBUG nova.virt.
2011-03-01 21:09:47,770 AUDIT nova.compute.
2011-03-01 21:09:47,900 DEBUG nova.rpc [-] Making asynchronous call... from (pid=8161) call /usr/lib/
2011-03-01 21:09:47,900 DEBUG nova.rpc [-] MSG_ID is 6324edb1992c48c
2011-03-01 21:09:49,440 DEBUG nova.rpc [-] Making asynchronous call... from (pid=8161) call /usr/lib/
2011-03-01 21:09:49,441 DEBUG nova.rpc [-] MSG_ID is 310a43e781c6438
2011-03-01 21:09:49,944 DEBUG nova.utils [-] Running cmd (subprocess): ip link show dev br100 from (pid=8161) execute /usr/lib/
2011-03-01 21:09:49,971 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables --delete FORWARD --in-interface br100 -j ACCEPT from (pid=8161) execute /usr/lib/
2011-03-01 21:09:49,982 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables -I FORWARD --in-interface br100 -j ACCEPT from (pid=8161) execute /usr/lib/
2011-03-01 21:09:49,997 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables --delete FORWARD --out-interface br100 -j ACCEPT from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,009 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables -I FORWARD --out-interface br100 -j ACCEPT from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,020 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables -N nova-local from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,030 DEBUG nova.utils [-] Result was 1 from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,036 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables --delete FORWARD -j nova-local from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,046 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables -I FORWARD -j nova-local from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,120 DEBUG nova.virt.
2011-03-01 21:09:50,262 DEBUG nova.virt.
2011-03-01 21:09:50,318 INFO nova [-] called setup_basic_
2011-03-01 21:09:50,318 INFO nova [-] ensuring static filters
2011-03-01 21:09:50,342 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t filter from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,506 INFO nova [-] <nova.db.
2011-03-01 21:09:50,506 INFO nova [-] <nova.db.
2011-03-01 21:09:50,506 INFO nova [-] <nova.db.
2011-03-01 21:09:50,507 INFO nova [-] <nova.db.
2011-03-01 21:09:50,507 INFO nova [-] new_filter: # Generated by iptables-save v1.4.4 on Tue Mar 1 21:09:50 2011
*filter
:INPUT ACCEPT [204991:205122195]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [203774:202929089]
:nova-fallback - [0:0]
:nova-local - [0:0]
:nova-inst-1 - [0:0]
:nova-sg-1 - [0:0]
-A nova-fallback -j DROP
-A FORWARD -j nova-local
-A OUTPUT -j nova-local
-A nova-local -d 10.0.0.2 -j nova-inst-1
-A nova-inst-1 -m state --state INVALID -j DROP
-A nova-inst-1 -m state --state ESTABLISHED,RELATED -j ACCEPT
-A nova-inst-1 -j nova-sg-1
-A nova-inst-1 -s 10.0.0.1 -p udp --sport 67 --dport 68 -j ACCEPT
-A nova-inst-1 -s 10.0.0.0/28 -j ACCEPT
-A nova-inst-1 -j nova-fallback
-A nova-sg-1 -p icmp -s 0.0.0.0/0 -j ACCEPT
-A nova-sg-1 -p tcp -s 0.0.0.0/0 --dport 22 -j ACCEPT
-A nova-sg-1 -p tcp -s 0.0.0.0/0 --dport 80 -j ACCEPT
-A nova-sg-1 -p tcp -s 0.0.0.0/0 --dport 8080 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A FORWARD -o br100 -j ACCEPT
-A FORWARD -i br100 -j ACCEPT
-A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
-A FORWARD -i virbr0 -o virbr0 -j ACCEPT
-A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-
-A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-
COMMIT
# Completed on Tue Mar 1 21:09:50 2011
2011-03-01 21:09:50,507 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=8161) execute /usr/lib/
2011-03-01 21:09:50,529 DEBUG nova.utils [-] Running cmd (subprocess): mkdir -p /var/lib/
2011-03-01 21:09:50,556 INFO nova.virt.
2011-03-01 21:09:50,631 DEBUG nova.utils [-] Running cmd (subprocess): /usr/bin/curl --fail --silent http://
2011-03-01 21:09:50,903 DEBUG nova.utils [-] Running cmd (subprocess): cp /var/lib/
2011-03-01 21:09:51,110 DEBUG nova.utils [-] Running cmd (subprocess): /usr/bin/curl --fail --silent http://
2011-03-01 21:10:12,024 DEBUG nova.utils [-] Running cmd (subprocess): qemu-img create -f qcow2 -o cluster_
2011-03-01 21:10:13,424 INFO nova.virt.
2011-03-01 21:10:16,727 DEBUG nova.utils [-] Running cmd (subprocess): sudo qemu-nbd -c /dev/nbd15 /var/lib/
2011-03-01 21:10:17,993 DEBUG nova.utils [-] Running cmd (subprocess): sudo tune2fs -c 0 -i 0 /dev/nbd15 from (pid=8161) execute /usr/lib/
2011-03-01 21:10:19,391 DEBUG nova.utils [-] Running cmd (subprocess): sudo mount /dev/nbd15 /tmp/tmpJwN7gO from (pid=8161) execute /usr/lib/
2011-03-01 21:10:19,485 DEBUG nova.utils [-] Running cmd (subprocess): sudo mkdir -p /tmp/tmpJwN7gO/
2011-03-01 21:10:19,507 DEBUG nova.utils [-] Running cmd (subprocess): sudo chown root /tmp/tmpJwN7gO/
2011-03-01 21:10:19,566 DEBUG nova.utils [-] Running cmd (subprocess): sudo chmod 700 /tmp/tmpJwN7gO/
2011-03-01 21:10:19,584 DEBUG nova.utils [-] Running cmd (subprocess): sudo tee -a /tmp/tmpJwN7gO/
2011-03-01 21:10:19,638 DEBUG nova.utils [-] Running cmd (subprocess): sudo umount /dev/nbd15 from (pid=8161) execute /usr/lib/
2011-03-01 21:10:21,006 DEBUG nova.utils [-] Running cmd (subprocess): rmdir /tmp/tmpJwN7gO from (pid=8161) execute /usr/lib/
2011-03-01 21:10:21,042 DEBUG nova.utils [-] Running cmd (subprocess): sudo qemu-nbd -d /dev/nbd15 from (pid=8161) execute /usr/lib/
2011-03-01 21:10:22,755 ERROR nova.exception [-] Uncaught exception
(nova.exception): TRACE: Traceback (most recent call last):
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: return f(*args, **kw)
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: self._conn.
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: if ret is None:raise libvirtError(
(nova.exception): TRACE: libvirtError: internal error Process exited while reading console log output: chardev: opening backend "file" failed
(nova.exception): TRACE:
(nova.exception): TRACE:
2011-03-01 21:10:22,798 ERROR nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
=======
and the instance state is:
euca-describe-
RESERVATION r-m5a06is3 simple_cloud default
INSTANCE i-00000001 ami-z21or64q 10.0.0.2 10.0.0.2 failed to spawn mykey (simple_cloud, ubuntu-svr1) 0 m1.tiny 2011-03-
=======
I am using this image: ubuntu1010-
Thanks!
Revision history for this message
|
#7 |
Try:
chmod a+rw instances/
It worked for me. I suspect is a bug...
indro
Revision history for this message
|
#8 |
Indro,
thanks so much for figuring out this problem. you are right. I've tried changing the permissions to the console and run it with the virsh create command successfully.
But I am running this instance with euca-run-instances and there is no way to specify that permission because the instances directories are created when euca-run-instances is launched.
So I guess I need to wait for the fix.
Thanks!
Revision history for this message
|
#9 |
Or you can just change the permission and use euca-reboot-
Revision history for this message
|
#10 |
Yep, that is a temporary working around which works OK. Do you know if this is reported as a bug? should I create a bug report?
Thanks again Indro!
Revision history for this message
|
#11 |
I rebuilt the system from scratch, did an upgrade to the latest bexar components and reinstall it. This fixed the problem.
Thanks for all your help.