There is a serious bug in ExaBGP including the latest version (4.2.20, while the port is still on 4.2.11).
Depending on network conditions and the number of configured neighbors, ExaBGP may stay in a loop in which it will never connect to them. This bug can be triggered after a power blackout, for example, when it can take some time for connectivity to be restored.
The bug is fixed on Github:
but it hasn't made it to a numbered release. It will for 4.2.21 I imagine.
Meanwhile, as the fix only requires adding two obvious code lines to a file I think it would be wise to add the patch to the port until 4.2.21 is released.
The bug is back, my fault actually.
I reported it for 4.2.11 and it was added to the master branch but I didn't notice 4.2.13 actually existed.
So,the same patch needs to be applied to 4.2.13.
Created attachment 227586 [details]
patch to solve the closed socket selflock
The bug is back on 4.2.13.