[Quagga-bugs] [Bug 297] vty_read: read error on vty client fd

[bugzilla-daemon at allevil.dishone.st]

Please do not reply directly to this email. All additional  
comments should be made in the comments box of this bug  
report.  
  
http://bugzilla.quagga.net/show_bug.cgi?id=297  
  




------- Additional Comments From glut at lanet.net.pl  2006-09-19 10:27 -------
bgp neighbor state change causes the following error in log file:

2006/09/18 08:24:54 BGP: %NOTIFICATION: received from neighbor 87.99.32.34 6/3 
(Cease/Peer Unconfigured) 0 bytes
2006/09/18 08:24:54 BGP: %ADJCHANGE: neighbor 87.99.32.34 Down BGP Notification 
received
2006/09/18 08:25:10 BGP: vty_read: read error on vty client fd 11, closing: 
Connection reset by peer
2006/09/18 08:27:53 BGP: %ADJCHANGE: neighbor 87.99.32.34 Up
2006/09/18 08:31:05 BGP: %NOTIFICATION: sent to neighbor 87.99.32.18 4/0 (Hold 
Timer Expired) 0 bytes
2006/09/18 08:44:29 BGP: 87.99.32.18 [Error] bgp_read_packet error: No route to 
host
2006/09/18 09:11:09 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 09:16:08 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 09:26:14 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 09:31:13 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 09:41:14 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 09:46:16 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 09:56:16 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 10:01:16 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer

log file entries appear until neighbor is up again.

2006/09/18 12:12:53 BGP: %ADJCHANGE: neighbor 62.233.250.101 Up
2006/09/18 12:17:24 BGP: vty_read: read error on vty client fd 21, closing: 
Connection reset by peer
2006/09/18 12:25:22 BGP: vty_read: read error on vty client fd 21, closing: 
Connection reset by peer
2006/09/18 12:30:30 BGP: vty_read: read error on vty client fd 21, closing: 
Connection reset by peer
2006/09/18 12:40:38 BGP: vty_read: read error on vty client fd 21, closing: 
Connection reset by peer
2006/09/18 12:49:18 BGP: %ADJCHANGE: neighbor 87.99.32.18 Up
2006/09/18 12:52:51 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer
2006/09/18 12:58:44 BGP: vty_read: read error on vty client fd 22, closing: 
Connection reset by peer

fd is changed when neighbor went up.

CVS wersion if from  17-09-2006, it contains patch against segfault which 
occured when no neighbor <ip> was issued.

------- Additional Comments From glut at lanet.net.pl  2006-10-18 10:08 -------
it seems like this problem is solved, 'error' was triggered by tcp port check 
issued by Nagios. Somehow this check exited non cleanly.   
  
  
  
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.