I managed to resolve the problem if anyone is interested by compiling from sources the latest rsyslog (5.4.0)

/etc/init.d/rsyslog stop
/etc/init.d/rsyslog.dpkg-new stop

cd /usr/src
wget http://www.rsyslog.com/Downloads-req-getit-lid-197.phtml
tar zxvf rsyslog-5.4.0.tar.gz.
cd rsyslog-5.4.0
./configure
make
make install

mv /etc/rsyslog.conf /etc/rsyslog.conf.original
cp /usr/src/rsyslog.conf /etc/rsyslog.conf

reboot

Now everything works as expected, no kern errors, no memory leaks, and i think that the logs are more organized (iptables messages are logged only in /var/log/messages and not in 3 logs like before).

I retract what I wrote earlier because this solution is messing with the default logging system in lucid.

Another solution which seems to work is the following:

- I copied the /etc/init/rsyslog-kmsg.conf from an Ubuntu 9.10 box
- I made a soft link in /etc/init.d to the upstart-job:
ln -s /lib/init/upstart-job /etc/init.d/rsyslog-kmsg
- I changed $KLogPath in /etc/rsyslog.conf to be: /var/run/rsyslog/kmsg

service rsyslog restart

And now it works.

Running Ubuntu 10.04 LTS, using the Latest 2.6 Paravirt (2.6.32.12-linode25) kernel, experienced same issue recently.

At the advice of HoopyCat on the #linode irc channel, I changed my boot profile to use the 2.6.34-linode26 kernel.

After a reboot, I no longer get the error message in /var/log/kern.log, however I'm not sure rsyslog is reading iptables/UFW log info correctly.

rsyslog is indeed logging iptables correctly!

HoopyCat/streamline, thanks for the helpfully information.

--
Travis