From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org, srn@coolheads.com
Subject: Re: can't find logged information
Date: Fri, 07 Feb 2020 15:51:51 +0100 [thread overview]
Message-ID: <2835529.L2OpFjvxA2@prime> (raw)
In-Reply-To: <501bc34b-2c77-a12a-6cb0-c49903eb420b@coolheads.com>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
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.
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.
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-07 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 14:13 can't find logged information Steve Newcomb
2020-02-07 14:51 ` Simon Wunderlich [this message]
[not found] <24aa48bb-8f52-78be-28df-98ec2e2a054b@coolheads.com>
2020-02-07 15:18 ` Steve Newcomb
2020-02-07 15:52 ` 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
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=2835529.L2OpFjvxA2@prime \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=srn@coolheads.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