tor-agent continously crashing while trying to bringup SSL connection with openvswitch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Committed
|
High
|
Prabhjot Singh Sethi | ||
R2.20 |
Fix Committed
|
High
|
Prabhjot Singh Sethi |
Bug Description
R2.20 Build 27 Ubuntu 14.04 Juno multi-node setup
Was trying to bringup tor-agent controlling a openvswitch over SSL and see that tor-agent is continuously crashing.
env.roledefs = {
'all': [host1, host2, host3, host4, host5, host6, host7],
'cfgm': [host1,
'openstack': [host1,
'control': [host1,
'compute': [host4,host5, host6, host7],
'collector': [host1,
'webui': [host1],
'database': [host1,
'toragent': [host6, host7],
'tsn': [host6, host7],
'build': [host_build],
}
env.hostnames = {
'all': ['nodec1', 'nodec2', 'nodec3', 'nodek1', 'nodek2', 'nodek3', 'nodeg11']
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
Core was generated by `/usr/bin/
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f9d54a8bcc9 in __GI_raise (sig=sig@entry=6) at ../nptl/
56 ../nptl/
(gdb) bt
#0 0x00007f9d54a8bcc9 in __GI_raise (sig=sig@entry=6) at ../nptl/
#1 0x00007f9d54a8f0d8 in __GI_abort () at abort.c:89
#2 0x00007f9d54a84b86 in __assert_fail_base (fmt=0x7f9d54bd5830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
file=
function=
#3 0x00007f9d54a84c32 in __GI___assert_fail (assertion=0xde2ad5 "0", file=0xdf6b60 "controller/
function=
#4 0x0000000000914c4a in OVSDB::
#5 0x00000000009154a5 in OVSDB::
#6 0x0000000000cea191 in TcpMessageReade
#7 0x0000000000cca930 in boost::
#8 0x0000000000ccbb74 in SslSession:
#9 0x0000000000dab4e0 in TaskImpl::execute() ()
#10 0x00007f9d5565ab3a in ?? () from /usr/lib/
#11 0x00007f9d55656816 in ?? () from /usr/lib/
#12 0x00007f9d55655f4b in ?? () from /usr/lib/
#13 0x00007f9d556520ff in ?? () from /usr/lib/
#14 0x00007f9d556522f9 in ?? () from /usr/lib/
#15 0x00007f9d55876182 in start_thread (arg=0x7f9d357f
#16 0x00007f9d54b4f47d in clone () at ../sysdeps/
(gdb)
Core will be in http://
root@nodek3:
total 248160
-rw------- 1 root root 178106368 May 23 21:16 core.contrail-
-rw------- 1 root root 157593600 May 23 21:17 core.contrail-
-rw------- 1 root root 157597696 May 23 21:17 core.contrail-
-rw------- 1 root root 153407488 May 23 23:49 core.contrail-
-rw------- 1 root root 157597696 May 24 01:36 core.contrail-
-rw------- 1 root root 149209088 May 24 02:17 core.contrail-
root@nodek3:
root@nodek3:
total 248160
-rw------- 1 root root 178106368 May 23 21:16 core.contrail-
-rw------- 1 root root 157593600 May 23 21:17 core.contrail-
-rw------- 1 root root 157597696 May 23 21:17 core.contrail-
-rw------- 1 root root 153407488 May 23 23:49 core.contrail-
-rw------- 1 root root 157597696 May 24 01:36 core.contrail-
-rw------- 1 root root 149209088 May 24 02:17 core.contrail-
root@nodek3:
there is an error the received message causing parser to fail. currently we are asserting on parse failure.
ideally on parse failures we can close the session and let the session get re-established on next attempt instead of assertion.