[3.1.0.0-6 ] Scale: control-node crash @ __TBB_machine_fetchadd8

Bug #1607627 reported by chhandak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.0
New
Critical
Nischal Sheth
R3.1
New
Critical
Nischal Sheth
Trunk
New
Critical
Nischal Sheth

Bug Description

Observed the crash while loading scaling config . Cluster was gettings called with VN , LIF and VMI.

BackTrace
------------
#0 0x000000000085c65e in __TBB_machine_fetchadd8 (addend=1, ptr=0x20035a11acb7) at /usr/include/tbb/machine/linux_intel64.h:85
#1 fetch_and_add (addend=1, location=0x20035a11acb7) at /usr/include/tbb/atomic.h:208
#2 fetch_and_add<(tbb::memory_semantics)0> (addend=1, this=0x20035a11acb7) at /usr/include/tbb/atomic.h:353
#3 fetch_and_add (addend=1, this=0x20035a11acb7) at /usr/include/tbb/atomic.h:357
#4 operator++ (this=0x20035a11acb7) at /usr/include/tbb/atomic.h:398
#5 inc_tx_update (this=0x7f297c5faf30) at controller/src/bgp/bgp_peer.cc:2431
#6 BgpPeer::SendUpdate (this=0x7f297c5faf30, msg=<optimized out>, msgsize=<optimized out>) at controller/src/bgp/bgp_peer.cc:1378
#7 0x00000000008d9c82 in RibOutUpdates::UpdateSend (this=this@entry=0x7f2934a8bc70, queue_id=queue_id@entry=1,
    message=message@entry=0x7f2938c5f280, dst=..., blocked=blocked@entry=0x7f29777fc960)
    at controller/src/bgp/bgp_ribout_updates.cc:428
#8 0x00000000008da4c1 in RibOutUpdates::DequeueCommon (this=this@entry=0x7f2934a8bc70, queue=queue@entry=0x7f2934a8c010,
    marker=marker@entry=0x7f2934a8c0b8, rt_update=0x7f29a490c2a0, blocked=blocked@entry=0x7f29777fcb20)
    at controller/src/bgp/bgp_ribout_updates.cc:137
#9 0x00000000008da892 in RibOutUpdates::TailDequeue (this=0x7f2934a8bc70, queue_id=1, msync=..., blocked=0x7f29777fcb20)
    at controller/src/bgp/bgp_ribout_updates.cc:213
#10 0x0000000000933fc1 in SchedulingGroup::UpdateRibOut (this=0x7f295496c0c0, ribout=0x7f2934a8bb80, queue_id=1)
    at controller/src/bgp/scheduling_group.cc:1087
#11 0x0000000000939145 in SchedulingGroup::Worker::Run (this=0x7f29a4b14b10) at controller/src/bgp/scheduling_group.cc:421
#12 0x00000000006aebbf in TaskImpl::execute (this=0x7f29bbe07540) at controller/src/base/task.cc:262
#13 0x00007f29c33c8b3a in ?? () from /usr/lib/libtbb.so.2
#14 0x00007f29c33c4816 in ?? () from /usr/lib/libtbb.so.2
#15 0x00007f29c33c3f4b in ?? () from /usr/lib/libtbb.so.2
#16 0x00007f29c33c00ff in ?? () from /usr/lib/libtbb.so.2
#17 0x00007f29c33c02f9 in ?? () from /usr/lib/libtbb.so.2
#18 0x00007f29c35e4182 in start_thread (arg=0x7f29777fd700) at pthread_create.c:312
#19 0x00007f29c26b547d in setfsuid () at ../sysdeps/unix/syscall-template.S:81
#20 0x0000000000000000 in ?? ()

Revision history for this message
chhandak (chhandak) wrote :

/auto/cores/1607627

Changed in juniperopenstack:
importance: Undecided → Critical
assignee: nobody → Nischal Sheth (nsheth)
information type: Proprietary → Public
Revision history for this message
chhandak (chhandak) wrote :

Core copied in /auto/cores/1607627

Revision history for this message
Nischal Sheth (nsheth) wrote :

Appears to be buffer overrun.
Many fields in BgpPeer after buffer_ appear to be corrupted.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.