tor-agents and control-node crashed multiple times on scale setup (at __GI___open_catalog)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
High
|
Hari Prasad Killi | ||
R2.1 |
New
|
Undecided
|
Hari Prasad Killi |
Bug Description
R2.1 Build 40 Ubuntu 14.04 Multi-node icehouse
nodei38 has 128 tor-agents (110 tors ) , 11K vmis, 100 vmis per tor
On supervisor-vrouter restart, it was seen that multiple tor-agents crashed repeatedly.. for about 30 mins and stopped.
Later restarts of supervisor-vrouter did not hit this
Few Cores will be in http://
bt :
[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 0x00007f3216078bb9 in __GI___open_catalog (cat_name=
nlspath=
at open_catalog.c:151
151 open_catalog.c: No such file or directory.
(gdb) bt
#0 0x00007f3216078bb9 in __GI___open_catalog (cat_name=
nlspath=
at open_catalog.c:151
#1 0x6e672d78756e696c in ?? ()
#2 0x2f766e6f63672f75 in ?? ()
Also seen in R2.1 Build 49
Using host libthread_db library "/lib/x86_ 64-linux- gnu/libthread_ db.so.1" . contrail- tor-agent --config_file /etc/contrail/ contrail- tor-agent- 1.co'. 0x20746e756f635 f5f <error: Cannot access memory at address 0x20746e756f635 f5f>, <optimized out>, env_var= 0x203d3c2029372 026 <error: Cannot access memory at address 0x203d3c2029372 026>, catalog= 0x70616d2820666 f65) 0x20746e756f635 f5f <error: Cannot access memory at address 0x20746e756f635 f5f>, <optimized out>, env_var= 0x203d3c2029372 026 <error: Cannot access memory at address 0x203d3c2029372 026>, catalog= 0x70616d2820666 f65)
Core was generated by `/usr/bin/
Program terminated with signal SIGABRT, Aborted.
#0 0x00007ff6c3d51bb9 in __GI___open_catalog (cat_name=
nlspath=
at open_catalog.c:151
151 open_catalog.c: No such file or directory.
(gdb) bt
#0 0x00007ff6c3d51bb9 in __GI___open_catalog (cat_name=
nlspath=
at open_catalog.c:151
#1 0x6e672d78756e696c in ?? ()
#2 0x2f766e6f63672f75 in ?? ()
#3 0x6f6d2d766e6f6367 in ?? ()