On Fri, Jul 20, 2012 at 05:25:46PM -0300, Guido Iribarren wrote:
On Mon, Jul 2, 2012 at 11:36 AM, Antonio Quartulli <ordex(a)autistici.org> wrote:
Has debug support been compiled in batman-adv? IF yes, it would be interesting
so see the output of the tt log (batctl ll tt; batctl l)
Ah, I should have re-read
this before :(
Recently we fixed a bug that which fix has not
been released yet. If we are sure
that this is the cause, you could eventually try an upgrade to a more recente
dev-version. But let's see the log first (if possible)
Last week I came across this bug again, with the latest firm which
includes the fixes mentioned, pushed by Marek.
We were kinda in a hurry so i didn't have much time to check it
thoroughly, so there's a *slim* chance it was just a coincidence, such
as very poor signal giving erratic results.
But if I recall correctly Nico Echaniz did stump on this too, using
the latest firm.
How did you solve it then? Rebooting?
So, although i can't confirm it 100%, it seems so
far the fixes didn't help :(
We'll keep an eye on it and try a "batctl l"
Yes, please. Remember to set the TT log level (batctl ll tt) before launching
Actually it would be very interesting to see the log of the involved nodes
during the "wrong behaviour period".
However, please keep an eye on the log anyway and report if you get any
message matching "*inconsistency*" (but report the whole part of the log, not
only this message). When you see those messages, please be sure that no clients
is connecting at that time (if so, it could be the normal procedure). If you get
this message, you should also see which node is involved in the inconsistency
(it is reported in the message too) and please report the tt log from that node
Thank you very much!
..each of us alone is worth nothing..
Ernesto "Che" Guevara