General

Release-note

Symptom

issue with getting error logs related to sysdb_mc traceback after bundle interface flap on peer router. RP/0/RSP0/CPU0:Sep 2 15:27:20.039 CEST: sysdb_mc[296]: %SYSDB-SYSDB-7-INTERNAL : [5307] : Failed to insert registration response: rc 0x40818600 ('sysdb' detected the 'warning' condition 'A SysDB client tried to access a nonexistent item or list an empty directory') : sysdb_mc : (PID=4993) : -Traceback= 7fceb8fcad04 563cfa52c575 563cfa5172c1 7fceb7e95cfc 7fceb7e9ac9d 7fceb7ea2039 7fceb7ea2e12 7fceb7ea815a 7fceb7c3f930 7fceb7c4d214 563cfa50cdaa

Conditions

RP/0/RSP0/CPU0:Sep 2 15:27:20.039 CEST: sysdb_mc[296]: %SYSDB-SYSDB-7-INTERNAL : [5307] : Failed to insert registration response: rc 0x40818600 ('sysdb' detected the 'warning' condition 'A SysDB client tried to access a nonexistent item or list an empty directory') : sysdb_mc : (PID=4993) : -Traceback= 7fceb8fcad04 563cfa52c575 563cfa5172c1 7fceb7e95cfc 7fceb7e9ac9d 7fceb7ea2039 7fceb7ea2e12 7fceb7ea815a 7fceb7c3f930 7fceb7c4d214 563cfa50cdaa RP/0/RSP0/CPU0:Sep 2 15:34:10.965 CEST: logger[68352]: %OS-SYSLOG-4-LOG_WARNING : PAM detected traceback for sysdb_mc on 0_RSP0_CPU0. All necessary files for debug have been collected and saved at 0/RSP0/CPU0 : harddisk:/cisco_support/PAM-traceback-xr_0_RSP0_CPU0-sysdb_mc-2023Sep02-153410.tgz (Please copy tgz file out of the router and send to Cisco support. This tgz file will be removed after 14 days.) core file is generated

Workaround

NA

Further Problem Description