From: Michael Buesch <mbuesch@freenet.de>
To: Dan McGrath <troubled@emaildesktop.com>
Cc: Harald Welte <laforge@netfilter.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: iptables stopped logging to files, but shows in ring buffer
Date: Wed, 4 Feb 2004 14:14:58 +0100 [thread overview]
Message-ID: <200402041415.14059.mbuesch@freenet.de> (raw)
In-Reply-To: <20040204122550.GE25175@obroa-skai.de.gnumonks.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 04 February 2004 13:25, you wrote:
> On Tue, Feb 03, 2004 at 11:16:07PM -0500, Dan McGrath wrote:
> > I remembered that iptables logs seem to show in dmesg command in the
> > past, and sure enough, they are all showing up there no problems, but not in
> > any files, including dmesg.log.
>
> If they are in dmesg, but in no files, than this cannot be a kernel
> problem. It has to be a userspace (klogd/syslogd) issue.
>
> Thus, it is off-topic to lkml, and is not a problem of
> netfilter/iptables.
I had the same problem a while ago.
The cause was: I've a cron-job that cleans logfiles
via bash script. This bash script shuts down syslogd and restarts
it. After cleaning the logs, kernel-messages didn't reach userspace
anymore. The solution was to not only shut down syslogd but also
klogd.
So, try to restart klogd _and_ syslogd.
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAIPBgFGK1OIvVOP4RAolGAJ96DUqZh4daeKiDQc4YzV87FhlZ+wCfdnHY
WceebWbSfmTVfcdoEqXxF2g=
=0Y6M
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-02-04 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 4:16 iptables stopped logging to files, but shows in ring buffer Dan McGrath
2004-02-04 12:25 ` Harald Welte
2004-02-04 13:14 ` Michael Buesch [this message]
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=200402041415.14059.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=troubled@emaildesktop.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