[CONTROLLER-1254] Reconnect not working when Agent/netconfd alone is brought down Created: 16/Apr/15  Updated: 25/Jul/23  Resolved: 28/Apr/15

Status: Resolved
Project: controller
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Manjunath Patil Assignee: Maros Marsalek
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 3001

 Description   

initially when the agent is up, the ssh connection is up and running.
root@4b1fc42506f3:/# netstat -na | grep 111.11.11.3
tcp6 0 0 172.17.0.11:46562 111.11.11.3:830 ESTABLISHED
root@4b1fc42506f3:/#

when we stop the agent (netconfd) alone, they enter into TIME_WAIT state

root@4b1fc42506f3:/# netstat -na | grep 111.11.11.3

tcp6 0 0 172.17.0.11:46565 111.11.11.3:830 TIME_WAIT

tcp6 0 0 172.17.0.11:46562 111.11.11.3:830 TIME_WAIT

after sometime when we bring the netconfd up again, these disappear
there is no reconnection

root@4b1fc42506f3:/# netstat -na | grep 111.11.11.3

root@4b1fc42506f3:/#

When sshd is restarted the reconnect seems to work fine. But not in this case.



 Comments   
Comment by Maros Marsalek [ 22/Apr/15 ]

Not confirmed on current Lithium. Needs to be rechecked with latest code in your specific use case

Comment by Maros Marsalek [ 28/Apr/15 ]

Not reproducable on current master branch

Generated at Wed Feb 07 19:55:04 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.