22 Mar
2017
22 Mar
'17
5:01 a.m.
Thanks for the feedback.
On 21.03.2017 03:00, Gui Iribarren wrote:
Hey Axel,
we're having a flood of these messages in logread,
around 10 per minute, which is quite annoying
Tue Mar 21 01:55:52 2017 daemon.err bmx6[5530]: INFO
create_ogm_aggregation(): IID jump 2 from 432 to 539
Ack, that is annoying. But not harmful. Its probably because you have
many nodes changing their description frequently.
How many nodes does your network have more or less?
And does it appear only as "IID jump 2..." or also as "IID jump 3 and
more...?
they are being logged regardless of dbgMuteTimeout=10000
or dbgMuteTimeout=1 or whatever setting
how exactly does --dbgMuteTimeout work?
It mutes messages that are logged with dbgf_mute() function after having
appeared twice for the amount of ms you specified with --dbgMuteTimeout.
The log message you complain about was not logged with the dbgf_mute()
function and was therefore always logged.
and how can we prevent those messages from showing up in the logs?
You could only change the code, or update to the latest bmx6
master-branch version. It contains below patch :-)
https://github.com/axn/bmx6/commit/4016a1980d900309771e432d1f7c741d6c48d477
cheers too
/axel
cheers!!
22 Mar
22 Mar
7:34 a.m.
New subject: bmx6 logging excesively
how exactly does --dbgMuteTimeout work?
It mutes messages that are logged with dbgf_mute() function after having
appeared twice for the amount of ms you specified with --dbgMuteTimeout.
The log message you complain about was not logged with
the dbgf_mute()
function and was therefore always logged.
and how can we prevent those messages from showing up in the logs?
You could only change the code, or update to the latest bmx6
master-branch version. It contains below patch :-)
https://github.com/axn/bmx6/commit/4016a1980d900309771e432d1f7c741d6c48d477
cheers too
/axel
cheers!!
23 Mar
23 Mar
7:10 p.m.
New subject: bmx6 logging excesively
@Axel, should I update the openwrt-routing feed to include this patch
into official LEDE source?
On 22/03/17 08:34, Axel Neumann wrote:
Let me try better:
It mutes (suspends) log messages for the amount of ms you specified with
--dbgMuteTimeout.
But only those that were internally called via dbgf_mute() function and
only if the to-be-logged string happened more than twice within the
given timeout.
So --dbgMuteTimeout=3600000 should log muted messages at most twice per
hour.
--
./p4u
how exactly does --dbgMuteTimeout work?
It mutes messages that are logged with dbgf_mute() function after having
appeared twice for the amount of ms you specified with --dbgMuteTimeout.
The log message you complain about was not logged
with the dbgf_mute()
function and was therefore always logged.
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
and how can we prevent those messages from showing up in the logs?
You could only change the code, or update to the latest bmx6
master-branch version. It contains below patch :-)
https://github.com/axn/bmx6/commit/4016a1980d900309771e432d1f7c741d6c48d477
cheers too
/axel
cheers!!
7:13 p.m.
New subject: bmx6 logging excesively
BTW @Axel do not forget to also apply this patch (and the previous ones)
to bmx7.
On 23/03/17 20:10, Pau wrote:
@Axel, should I update the openwrt-routing feed to
include this patch
into official LEDE source?
On 22/03/17 08:34, Axel Neumann wrote:
Let me try better:
It mutes (suspends) log messages for the amount of ms you specified with
--dbgMuteTimeout.
But only those that were internally called via dbgf_mute() function and
only if the to-be-logged string happened more than twice within the
given timeout.
So --dbgMuteTimeout=3600000 should log muted messages at most twice per
hour.
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
--
./p4u
how exactly does --dbgMuteTimeout work?
It mutes messages that are logged with dbgf_mute() function after having
appeared twice for the amount of ms you specified with --dbgMuteTimeout.
The log message you complain about was not logged
with the dbgf_mute()
function and was therefore always logged.
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
and how can we prevent those messages from showing up in the logs?
You could only change the code, or update to the latest bmx6
master-branch version. It contains below patch :-)
https://github.com/axn/bmx6/commit/4016a1980d900309771e432d1f7c741d6c48d477
cheers too
/axel
cheers!!
26 Mar
26 Mar
8:50 a.m.
New subject: bmx6 logging excesively
On 23.03.2017 20:13, Pau wrote:
BTW @Axel do not forget to also apply this patch (and
the previous ones)
to bmx7.
The excessive-logging one is not needed for bmx7 (IIDs do not jump in bmx7).
The --configSync one for bmx7 is now in bmx7 branch tip:
https://github.com/axn/bmx6/commit/64e29020ac683b246e28094742838ff39cb7ee80
On 23/03/17 20:10, Pau wrote:
> @Axel, should I update the openwrt-routing feed to include this patch
> into official LEDE source?
Yes, that would be nice. Maybe also update bmx7 package then.
thx
/axel
On 22/03/17 08:34, Axel Neumann wrote:
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
>
> how exactly does --dbgMuteTimeout work?
It mutes messages that are logged with dbgf_mute() function after having
appeared twice for the amount of ms you specified with --dbgMuteTimeout.
Let me try better:
It mutes (suspends) log messages for the amount of ms you specified with
--dbgMuteTimeout.
But only those that were internally called via dbgf_mute() function and
only if the to-be-logged string happened more than twice within the
given timeout.
So --dbgMuteTimeout=3600000 should log muted messages at most twice per
hour.
The log message you complain about was not logged
with the dbgf_mute()
function and was therefore always logged.
>
> and how can we prevent those messages from showing up in the logs?
You could only change the code, or update to the latest bmx6
master-branch version. It contains below patch :-)
https://github.com/axn/bmx6/commit/4016a1980d900309771e432d1f7c741d6c48d477
cheers too
/axel
>
> cheers!!
>
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
2589
days inactive
2593
days old
4 comments
2 participants
participants (2)
-
Axel Neumann -
Pau