On Thu, Jan 28, 2010 at 04:40:54PM +0300, Mikhail A. Grishin wrote:
We found that "Finite state machine error" problem is not related to your patches. It randomly occurs on our production server at the time of daemon startup :((
The problem is occurs on small number of peers. (2 or 3 or 4 from ~280) Some problem peers are the same at next startup, some - not.
On test server with small number of active peers (and same config) we doesn't see this issue.
What can be done? Right now we see the problem on pure 1.2.0 release...
About "UPDATE message immediately after it sent OPEN" - we ask one of our customers (which hit that problem) to collect debug from his side. See the attachments (3 files).
I will look at it.
One more, after applying the "well-known communities" patch, the BIRD goes to .core two times ( 5-30 seconds after startup):( Do you need the last core file?
Yes, if you could send me core file and bird binary. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."