Bug #685

xmlrpc exceptions when getting pools of elements intensively

Added by Hector Sanjuan over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:06/16/2011
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:Release 3.0
Resolution:duplicate Pull request:
Affected Versions:

Description

Making many continious calls to extract pools of elements via OpenNebula ruby OCA throws

*** glibc detected *** /srv/cloud/one-crash/bin/oned: double free or corruption (!prev): 0x0812b158 ***
======= Backtrace: =========
/lib/libc.so.6(+0x6dffb)[0xb700bffb]
/lib/libc.so.6(+0x6ed7b)[0xb700cd7b]
/lib/libc.so.6(cfree+0x6d)[0xb7010add]
/usr/lib/libstdc++.so.6(_ZdlPv+0x1f)[0xb720398f]
/usr/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1b)[0xb71e405b]
/usr/lib/libstdc++.so.6(_ZNSs6assignERKSs+0xab)[0xb71e5beb]
/usr/lib/libstdc++.so.6(_ZNSsaSERKSs+0x23)[0xb71e5c43]
/srv/cloud/one-crash/bin/oned[0x807dea9]
/usr/lib/libxmlrpc_server++.so.3(+0x3531)[0xb7406531]
/usr/lib/libxmlrpc_server.so.3(xmlrpc_dispatchCall+0x1cf)[0xb73f86cf]
/usr/lib/libxmlrpc_server.so.3(xmlrpc_registry_process_call+0xfe)[0xb73f87fe]
/usr/lib/libxmlrpc_server_abyss.so.3(+0x226e)[0xb73ff26e]
/usr/lib/libxmlrpc_abyss.so.3(+0x97a1)[0xb73ec7a1]
/usr/lib/libxmlrpc_abyss.so.3(+0x4f90)Error monitoring: Connection refused - connect(2)

The core backtrace shows

(gdb) bt
#0  0xb757a81a in xmlrpc_serialize_value () from /usr/lib/libxmlrpc.so.3
#1  0xb757b06c in xmlrpc_serialize_response () from /usr/lib/libxmlrpc.so.3
#2  0xb75c28d4 in xmlrpc_registry_process_call () from /usr/lib/libxmlrpc_server.so.3
#3  0xb75c926e in ?? () from /usr/lib/libxmlrpc_server_abyss.so.3
#4  0xb75b67a1 in ?? () from /usr/lib/libxmlrpc_abyss.so.3
#5  0xb75b1f90 in ?? () from /usr/lib/libxmlrpc_abyss.so.3
#6  0xb75b9966 in ?? () from /usr/lib/libxmlrpc_abyss.so.3
#7  0xb7597b25 in start_thread () from /lib/libpthread.so.0
#8  0xb723b46e in clone () from /lib/libc.so.6

and the "thread apply all bt"

Thread 17 (Thread 29104):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 16 (Thread 29106):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 15 (Thread 29109):
Cannot access memory at address 0xbfc8862c

Thread 14 (Thread 29116):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 13 (Thread 29110):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 12 (Thread 29111):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 11 (Thread 29114):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 10 (Thread 29112):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

0  0xffffe424 in __kernel_vsyscall ()
#1  0x79726575 in ?? ()
#2  0x6e75662d in ?? ()
#3  0x6f697463 in ?? ()
#4  0x0000736e in ?? ()
#5  0x00000045 in ?? ()
#6  0x00000000 in ?? ()

Thread 8 (Thread 29527):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 7 (Thread 29113):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 6 (Thread 29115):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 5 (Thread 29108):
Cannot access memory at address 0xb5677188

Thread 4 (Thread 29098):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 3 (Thread 29105):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 2 (Thread 29103):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0x00000000 in ?? ()

Thread 1 (Thread 29526):
#0  0xb751781a in xmlTextWriterStartCDATA () from /usr/lib/libxml2.so.2
#1  0x00000000 in ?? ()

Related issues

Duplicates Bug #702: oned crashed Closed 06/28/2011

History

#1 Updated by Ruben S. Montero over 9 years ago

  • Status changed from New to Closed
  • Target version set to Release 3.0
  • Resolution set to fixed

#2 Updated by Ruben S. Montero over 9 years ago

  • Resolution changed from fixed to duplicate

Also available in: Atom PDF