Description

This article provides a solution to the BGP_WRITE_WOULD_BLOCK error message.

 

Symptoms

The following message is reported when a BGP session is being established:  

Dec  6 13:17:47  xxx-re0 rpd[1829]: %DAEMON-4-RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer x.x.x.x (Internal AS xxxxx) changed state from EstabSync to Established (event RsyncAck) (instance master)
Dec  6 13:17:47  xxx-re0 rpd[1829]: %DAEMON-3-BGP_WRITE_WOULD_BLOCK: bgp_send: sending xx bytes to x.x.x.x (Internal AS xxxxx) blocked (no spooling requested): Resource temporarily unavailable
The issue can be seen when:
  • Non-stop routing (NSR) is enabled on the router
  • BGP session flaps or is newly established

Solution

This BGP error message safely be ignored and has no service impact. The "BGP_WRITE_WOULD_BLOCK" has no relation to the cause of why BGP flapped and has no impact on the BGP session

The error log has been removed from the log files in the latest Junos releases. This issue is tracked in PR1240885 .