Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] how is everyone's uptime?
Date: Thu, 11 Dec 2014 14:58:57 -0500	[thread overview]
Message-ID: <16381.1418327937@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 10 Dec 2014 14:52:59 -0800." <CAA93jw6mJ=n2HkrgmG=y21BC5HGYH6-OAr2SEL9zp_uACpsmnQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]

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.

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.

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.




[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  reply	other threads:[~2014-12-11 19:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 22:52 Dave Taht
2014-12-11 19:58 ` Valdis.Kletnieks [this message]
2014-12-11 21:50   ` Dave Taht
2014-12-12  0:18     ` Valdis.Kletnieks
2014-12-12  0:22       ` Dave Taht
2014-12-12  0:32 ` Aaron Wood
2014-12-12  0:42   ` Dave Taht
2014-12-12  7:33     ` [Cerowrt-devel] an option for a new platform? Erkki Lintunen
2014-12-12 14:52       ` Dave Taht
2014-12-13 23:02         ` David P. Reed
2014-12-16  9:02           ` Dave Taht
2014-12-12  1:30 ` [Cerowrt-devel] how is everyone's uptime? Joseph Swick
2014-12-12  1:52 ` Jim Gettys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16381.1418327937@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox