Re: [Cerowrt-devel] how is everyone's uptime?

[Dave Taht <dave.taht@gmail.com>]

just send babeld.log to /dev/null via the setting in /etc/config/bab*

I had, on at least one release, left that logging function on. Other
folk, do check.

Do hate running out of memory for no good reason.


On Thu, Dec 11, 2014 at 11:58 AM,  <Valdis.Kletnieks@vt.edu> wrote:
> On Wed, 10 Dec 2014 14:52:59 -0800, Dave Taht said:
>> I am interested in long term memory leakage (run a free),
>> process usage (runaways like pimd), and growth in disk space usage (df),
>> so output like
>
> root@bogon-gateway-1:~# uptime
>  14:31:39 up 33 days,  8:50,  load average: 0.02, 0.05, 0.05
> root@bogon-gateway-1:~# free
>              total         used         free       shared      buffers
> Mem:        126256       100732        25524            0         6156
> -/+ buffers:              94576        31680
> Swap:            0            0            0
> root@bogon-gateway-1:~# df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> rootfs                    7296       392      6904   5% /
> /dev/root                 7680      7680         0 100% /rom
> tmpfs                    63128     49364     13764  78% /tmp
> /dev/mtdblock5            7296       392      6904   5% /overlay
> overlayfs:/overlay        7296       392      6904   5% /
> tmpfs                      512         0       512   0% /dev
>
> Biggest issue after 33 days of uptime seems to be /tmp/log/babeld.log:
>
> root@bogon-gateway-1:~# ls -l /tmp/log/babeld.log
> -rw-r--r--    1 root     root      49416018 Dec 11 14:34 babeld.log
> root@bogon-gateway-1:~# wc /tmp/log/babeld.log
>    772310   6176740  49416530 /tmp/log/babeld.log
> root@bogon-gateway-1:~# sort /tmp/log/babeld.log | uniq -c
>
> Oh kewl.  That seems to have killed it :)
>
> Uptime is now 11 minutes, and the log is much shorter.

Heh. Sorry!


>
> root@bogon-gateway-1:~# sort /tmp/log/babeld.log | uniq -c
>     107 Couldn't determine channel of interface sw00: Invalid argument.
>     107 Couldn't determine channel of interface sw10: Invalid argument.

This is a longstanding bug in either the kernel or babel on correctly
determining the channel on a wireless device in AP mode.

It is not an error, per se, it just means that diversity routing (which
needs to know the channel) doesn't work as well, as the channel
here gets set to "interfering" rather than the correct channel number.


>
> I'm trying to remember why I even want babeld running.  In any case,
> the log as it stands now those two messages aren't much help.
>
>
>



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks