Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Syslog message: BGP_WRITE_WOULD_BLOCK

0

0

Article ID: KB32551 KB Last Updated: 24 Oct 2018Version: 1.0
Summary:

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.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search