Bug 4967

Summary: LOG target doesn't write to a log file
Product: Mageia Reporter: Jeffrey Laramie <jalaramie>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: remco
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: iptables-1.4.12.2-1.mga2 CVE:
Status comment:

Description Jeffrey Laramie 2012-03-16 01:46:24 CET
Description of problem:
I run custom iptables scripts on my boxes with log certain packets to a log file. My script works as expected on Mageia 1. The same script on the same hardware fails to log using Cauldron/Beta 1.

How reproducible:
Insert any iptables rule using the -j LOG target

Details:
I've been working on this one for weeks assuming it was just a configuration error due to my unfamiliarity with Mageia, but I just can't figure it out. Here's some of what I've done so far.

1. Installed mga1 on the same box using the same iptables configuration script. It works as expected.

2. Re-install Beta 1 on the same box and run the same script. No logging.

3. Run lsmod on the Beta 1 box and compare the results to a Mga1 box with functioning firewall logging. The same modules are loaded.

4. Did a search on every file in /var/log/* to see if the results were being logged to a different file. No logs found.

5. I changed the default security level from secure to standard with no effect.

6. At one point I noticed that the iptables service was active and the the ULOG module was active. I disabled the iptables service and rebooted. The ULOG module was gone, but logging still didn't work.

It seems unlikely that I found a bug in iptables, but I don't know what else to try.

Jeff
Remco Rijnders 2012-03-16 07:58:27 CET

CC: (none) => remco

Comment 1 Jeffrey Laramie 2012-03-16 12:20:20 CET
I forgot to mention that if I run iptables -L -v -n the output shows the packet count increasing on the LOG rules, so I know that the LOG rules are being hit.

Jeff
Manuel Hiebel 2012-03-16 19:08:26 CET

Assignee: bugsquad => tmb

Comment 2 Jeffrey Laramie 2012-04-03 14:08:53 CEST
This was a problem with rsyslog which was fixed by package rsyslog-5.8.9-2.mga2

Status: NEW => RESOLVED
Resolution: (none) => FIXED