Guest

Preview Tool

Cisco Bug: CSCvs41922 - Automatic recover of closed connection between process uidb_server and prm_server_to

Last Modified

Jan 16, 2020

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

6.4.2.BASE

Description (partial)

Symptom:
Under certain scenarios multiple processes may be seen blocked on process uidb_server.
This will occur in the event that permanent connection between uidb_server and prm_server_to process is inadvertently closed.

Conditions:
While attempting to commit interface IP related configurations commit takes long and although succeeding IPv4 related configuration commands are missing.

Additionally, while attempting 'show ip' commands these timeout and similar log is observed:

<snip>
sysdb_svr_local[188]: %SYSDB-SYSDB-6-TIMEOUT_EDM : EDM request for 'oper/ipv4-io/node/20/if/vrf/0x0/0/ifbrief/' from 'show_ip_interface' (jid 69073, node 0/RSP0/CPU0). No response from 'ipv4_ma' (jid 211, node 0/RSP0/CPU0) within the timeout period (100 seconds) 
<snip>

Moreover ipv4_ma and multiple other processes are seen blocked on process uidb_server at line card.
As seen from 'show processes blocked location all':

<snip>
 node:  node0_0_CPU0
------------------------------------------

  Jid       Pid Tid          ProcessName        State   TimeInState    Blocked-on
  328      4876 4876            qos_ma_ea        Reply 0002:18:22.0452    4397 uidb_server
  182      6466 6507             vic_0_11        Reply 0001:12:39.0832    4397 uidb_server
  182      6466 6466             vic_0_11        Mutex 0001:12:39.0535 0x7f9e8d81f138 6507 vic_0_11 vic_drv_lock:3433
  359      6317 6317                  cdp        Reply 0002:26:39.0820    5068 pm
  166      6138 6138              vlan_ea        Reply 0002:28:19.0831    4397 uidb_server
  309      6126 6126   ether_caps_partner        Reply 0002:28:19.0833    5063 ifmgr
  354      5605 5605              mpls_io        Reply 0002:16:24.0519    5063 ifmgr
  129      5081 5081    ipv4_mfwd_partner        Reply 0002:19:23.0546    4397 uidb_server
  273      5083 5552              ipv4_io        Reply 0002:23:19.0825    5085 fib_mgr
  126      5085 5568              fib_mgr        Reply 0002:23:19.0825    4397 uidb_server
  352      5068 5068                   pm        Reply 0002:26:39.0829    4397 uidb_server
  125      5086 5325              ipv4_ma        Reply 0002:13:43.0549    5063 ifmgr
  125      5086 5086              ipv4_ma        Mutex 0002:14:43.0508 0x55dbc6ee4340 5325 ipv4_ma ipv4_process:681
  348      5077 5077           mpls_io_ea        Reply 0002:16:24.0525    4397 uidb_server
 
node:  node0_RSP0_CPU0
------------------------------------------
  Jid       Pid Tid          ProcessName        State   TimeInState    Blocked-on
67654     14406 14406   sh_proc_ng_blocked        Reply 0000:00:00.0271    4531 procfs_server
 1188      7195 7195            intf_mgbl        Reply 0000:00:11.0227    4505 sysdb_mc
  412      7208 7208              mpls_io        Reply 1932:25:12.0870    5874 ifmgr
  252      7233 7910              lpts_fm        Reply 0000:00:00.0879    5878 lpts_pa
  419      7197 7197              eint_ma        Reply 1932:25:08.0677    5874 ifmgr
  211      5917 5917              ipv4_ma        Reply 1932:24:58.0329    5874 ifmgr
<snip>
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.