iptables stopped logging to files, but shows in ring buffer
I am running a 2.4.24 system with grsecurity-1.9.13-2.4.24.patch and patch-cryptoloop-jari-2.4.22-rc2.0. The problem I just discovered is that after I enabled a iptables rule to log incoming --syn packets on feb 1st, the machine stopped logging to any of the files in /var/log after about half a day. 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.
I have attached my .config as well. I havent tried rebooting or restarting network yet just in case I get some suggestions or things to try while I have the borked behaviour. If you have any ideas, please drop me a line, thanks guys.
troubled
Quoted 3 lines · Dan McGrath
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.
Quoted 1 line
troubled
Signature · 5 lines
- Harald Welte <[email protected]> http://www.netfilter.org/ ============================================================================ "Fragmentation is like classful addressing -- an interesting early architectural error that shows how much experimentation was going on while IP was being designed." -- Paul Vixie
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 10 lines · you
Quoted 3 lines · Dan McGrath
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-----