[openstack-dev] Segmentation Fault in nova-compute service on ARM platform.

Michael Still mikal at stillhq.com
Tue Jul 7 05:59:30 UTC 2015


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
<topradeepyaduvanshi at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Rackspace Australia



More information about the OpenStack-dev mailing list