public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Steve Newcomb <srn@coolheads.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: can't find logged information
Date: Fri, 7 Feb 2020 10:18:19 -0500	[thread overview]
Message-ID: <b696db36-b9db-d31a-d8a6-0523f8a0986c@coolheads.com> (raw)
In-Reply-To: <24aa48bb-8f52-78be-28df-98ec2e2a054b@coolheads.com>


On 2/7/20 9:51 AM, Simon Wunderlich wrote:
> On Friday, February 7, 2020 3:13:47 PM CET Steve Newcomb wrote:
>> @rpc152:/tmp/log# echo "$(logread)" | grep batman
>> Thu Feb 6 15:21:13 2020 kern.warn kernel: [174193.938445] batman_adv:
>> [Deprecated]: batctl (pid 22747) Use of debugfs file "nc_nodes".
>> @rpc152:/tmp/log#
>>
>>
>> What have I missed?
> Hi Steve,
>
> you can use "batctl log" to retrieve the log. It will not appear in your
> logread.
Alas, that doesn't work either, and I don't know why:

root@rpc152:~# batctl log
Error - no valid command or debug table specified: log
Usage: batctl [options] command|debug table [parameters]
options:
         -h print this help (or 'batctl <command|debug table> -h' for 
the parameter help)
         -v print version

commands:
         meshif <netdev> aggregation|ag [0|1] display or modify 
aggregation setting
...
>
> When the problem happens, you can also check "iw wlan0 station dump" 
> and other
> debug files (batctl n for neighbors) to find out if the WiFi layer is 
> still
> working. It wouldn't be the first time that actually the WiFi chip or 
> driver
> has a problem, not batman-adv.
I've seen that "batctl n" works, and "iw mesh0 station dump" works, too.

I am arranging for the nodes to send me such mail when things have gone 
awry, but prior to rebooting.  I've written a tiny mail queueing system 
that optionally uses nonvolatile memory for the queue.


       reply	other threads:[~2020-02-07 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <24aa48bb-8f52-78be-28df-98ec2e2a054b@coolheads.com>
2020-02-07 15:18 ` Steve Newcomb [this message]
2020-02-07 15:52   ` can't find logged information Simon Wunderlich
2020-02-07 16:59     ` Steve Newcomb
2020-02-07 17:07       ` Simon Wunderlich
2020-02-11 19:03         ` Steve Newcomb
2020-02-19  9:50           ` Simon Wunderlich
2020-02-19 15:00             ` Steve Newcomb
2020-02-07 14:13 Steve Newcomb
2020-02-07 14:51 ` Simon Wunderlich

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

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

  git send-email \
    --in-reply-to=b696db36-b9db-d31a-d8a6-0523f8a0986c@coolheads.com \
    --to=srn@coolheads.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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