Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Joseph Swick <cerowrt@decoy.cotse.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] how is everyone's uptime?
Date: Thu, 11 Dec 2014 20:30:15 -0500	[thread overview]
Message-ID: <MTAwMDA0NC5kZWNveQ.1418347816@quikprotect> (raw)
In-Reply-To: <CAA93jw6mJ=n2HkrgmG=y21BC5HGYH6-OAr2SEL9zp_uACpsmnQ@mail.gmail.com>



On 12/10/2014 05:52 PM, Dave Taht wrote:
> the lab where I was keeping a box up under load had a long enough
> power failure last week to keeelll my approximatively 76 days uptime.
> 
> Anybody else got any record-holders here?
> 
> 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
> 
> uptime
> free
> df
> 
> periodically would be nice.
> 

(Hopefully this gets through) Here's mine:

root@gw:~# uptime
 01:10:07 up 117 days,  1:43,  load average: 0.26, 0.17, 0.12

root@gw:~# free
             total         used         free       shared      buffers
Mem:        126256        55744        70512            0         6240
-/+ buffers:              49504        76752
Swap:            0            0            0

root@gw:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                    7296       404      6892   6% /
/dev/root                 7680      7680         0 100% /rom
tmpfs                    63128      1272     61856   2% /tmp
/dev/mtdblock5            7296       404      6892   6% /overlay
overlayfs:/overlay        7296       404      6892   6% /
tmpfs

However, while I'm getting an IPv6 address from Comcast, I don't have
IPv6 working inside, and I see this regularly in my logs:

Fri Dec 12 01:23:53 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on sw00 thus we don't announce a
default route!
Fri Dec 12 01:23:54 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on se00 thus we don't announce a
default route!
Fri Dec 12 01:23:58 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on sw00 thus we don't announce a
default route!
Fri Dec 12 01:23:59 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on se00 thus we don't announce a
default route!
Fri Dec 12 01:24:02 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on sw00 thus we don't announce a
default route!


I had tried to send a message to the list about it a while back, but I
think it may have gone to the bit-bucket due to how I setup my email
aliases (hoping the same fate doesn't happen to this message).  At the
time I thought it may have been PLEBKAC (mine), but I think there's been
a few others who have posted similar error messages.  I just haven't had
a whole lot of time to try to investigate myself, so I've just been
continuing to live with just IPv4.

-- Joseph Swick

  parent reply	other threads:[~2014-12-12  1:30 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
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 ` Joseph Swick [this message]
2014-12-12  1:52 ` [Cerowrt-devel] how is everyone's uptime? 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=MTAwMDA0NC5kZWNveQ.1418347816@quikprotect \
    --to=cerowrt@decoy.cotse.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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