[openstack-dev] Metadata via dhcp namespace not working for icehouse release
Hii Guys, I am trying to run Metadata via the DHCP namespace by following blog post mentioned below: http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html Commands mentioned on above link for debugging o/p is exactly same for my setup. Also i am able to ping 169.254.169.254 metadata server ip. But while running below command from VM i get curl http://169.254.169.254 curl: (7) Failed to connect to 169.254.169.254 port 80: Connection timed out and curl http://169.254.169.254:53 gives empty response & from controller node if i run curl http://169.254.169.254 i get curl http://169.254.169.254:8775 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04 On controller node: netstat -nap | grep 8775 gives tcp0 0 0.0.0.0:87750.0.0.0:* LISTEN 13619/python *Please suggest some pointers i am stuck at the same point from last 10 days.* Regards Pradeep Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Segmentation Fault in nova-compute service on ARM platform.
Hi michael, I did tried icehouse release but getting same error. I think there is some issue with python code but how to resolve that need some guidance on the same. On Jul 7, 2015 11:32 AM, Michael Still mi...@stillhq.com wrote: Havana is very very old and no longer supported. Why are you porting that release in particular? Michael On Tue, Jul 7, 2015 at 3:51 PM, Pradeep kumar topradeepyaduvan...@gmail.com wrote: Hi Guys, I am porting openstack on arm platform, but while running nova-compute service on it throws segmentaion fault. Below are the logs: 2015-06-05 09:24:12.195 11374 INFO nova.virt.driver [-] Loading compute driver 'libvirt.LibvirtDriver' 2015-06-05 09:24:13.483 11374 INFO nova.openstack.common.rpc.common [req-ba16a115-ed64-4fb5-b13e-f28e03a28b24 None None] Connected to AMQP server on 192.168.1.100:5672 2015-06-05 09:24:13.600 11374 INFO nova.openstack.common.rpc.common [req-ba16a115-ed64-4fb5-b13e-f28e03a28b24 None None] Connected to AMQP server on 192.168.1.100:5672 2015-06-05 09:24:13.808 11374 AUDIT nova.service [-] Starting compute node (version 2013.2.2) Program received signal SIGSEGV, Segmentation fault. 0x76f244d4 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 While tracing the same with gdb: I am getting corrupt stack: (gdb) bt #0 0x76f244d4 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #1 0x76f2ab78 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #2 0x76f2905c in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #3 0x76f2ab78 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #4 0x76eaf690 in ?? () from /usr/lib/libpython2.7.so.1.0 Cannot access memory at address 0x0 #5 0x76eaf690 in ?? () from /usr/lib/libpython2.7.so.1.0 Cannot access memory at address 0x0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) The function PyEval_EvalFrameEx () is present in ceval.c Also I am using havana release of openstack. I am new to openstack just tried openstack nodes on x-86 platform. Any help in order to solve the above issue is appreciated. Regards Pradeep Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Rackspace Australia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Segmentation Fault in nova-compute service on ARM platform.
Ohk sean I am Using a platform with low configuration.IF u can help regarding some achitectural changes actually i am stuck at same point from last 7 days. Thanks sean On Jul 7, 2015 5:11 PM, Sean Dague s...@dague.net wrote: On 07/07/2015 07:07 AM, Pradeep kumar wrote: Hi michael, I did tried icehouse release but getting same error. I think there is some issue with python code but how to resolve that need some guidance on the same. It is extremely unlikely that anything in the OpenStack code is responsible for a segfault in python. This seems like your python interpreter being broken on your processor / os. I think you will need to solve that much deeper problem. -Sean -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Segmentation Fault in nova-compute service on ARM platform.
Hi Guys, I am porting openstack on arm platform, but while running nova-compute service on it throws segmentaion fault. Below are the logs: 2015-06-05 09:24:12.195 11374 INFO nova.virt.driver [-] Loading compute driver 'libvirt.LibvirtDriver' 2015-06-05 09:24:13.483 11374 INFO nova.openstack.common.rpc.common [req-ba16a115-ed64-4fb5-b13e-f28e03a28b24 None None] Connected to AMQP server on 192.168.1.100:5672 2015-06-05 09:24:13.600 11374 INFO nova.openstack.common.rpc.common [req-ba16a115-ed64-4fb5-b13e-f28e03a28b24 None None] Connected to AMQP server on 192.168.1.100:5672 2015-06-05 09:24:13.808 11374 AUDIT nova.service [-] Starting compute node (version 2013.2.2) Program received signal SIGSEGV, Segmentation fault. 0x76f244d4 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 While tracing the same with gdb: I am getting corrupt stack: (gdb) bt #0 0x76f244d4 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #1 0x76f2ab78 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #2 0x76f2905c in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #3 0x76f2ab78 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #4 0x76eaf690 in ?? () from /usr/lib/libpython2.7.so.1.0 Cannot access memory at address 0x0 #5 0x76eaf690 in ?? () from /usr/lib/libpython2.7.so.1.0 Cannot access memory at address 0x0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) The function PyEval_EvalFrameEx () is present in ceval.c Also I am using havana release of openstack. I am new to openstack just tried openstack nodes on x-86 platform. Any help in order to solve the above issue is appreciated. Regards Pradeep Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
