Customer observing below logs;

LAB> show log messages | match RPD_KRT_Q_RETRIES

Jun 22 20:56:58 2024 LAB rpd[8481]: RPD_KRT_Q_RETRIES: list nexthop ADD: Device busy

No service impact was observed. Customer observed only RPD_KRT_Q_RETRIES messages.

From logs it was observed that one of the ports went down resulting in below logs.

Jun 22 20:54:09 2024 LAB rpd[8481]: RPD_LDP_SESSIONDOWN: LDP session 24.175.52.130 is down, reason: received notification from peer

Jun 22 20:54:09 2024 LAB rpd[8481]: RPD_LAYER2_VC_DOWN: State of Layer 2 VC (Neighbor : 24.175.52.130, VC-ID : 585) changed from UP to DELETED

Jun 22 20:54:09 2024 LAB mib2d[8480]: SNMP_TRAP_LINK_DOWN: ifIndex 698, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/36:1.0

RPD_Q_KRT_RETRIES logs are observed due to above event.

EBUSY from Kernel is expected when the RPD is sending the Add before a delete is processed. This is transient in nature and will eventually will go away without any manual intervention

This is seen only once in customer environment.