On 03/01/2013 12:06 PM, Rainer Gerhards wrote: > On Fri, 2013-03-01 at 11:59 +0100, Michal Fiala wrote: >> Hallo, >> >> we are using rsyslogd 5.8.11-2 on debian 7.0. This host is running lxc >> containers. >> You can see rsyslogd configuration in attachment. >> We have problem with facility kern. Messages are malformed. It means >> missing characters, disarranged characters. >> Messages from dmesg output are without problems. Only messages with >> facility kern (primary kern.log) are malformed. >> >> Where could be the problem? >> > There was a couple of fixes for imklog done in 5.10.2. Could they solve > your problem? > > If not, I suggest to move to the currently supported 7.2.5 version and > check if the problem persists.
OK, I will try new versions. Thanks > > Rainer >> Thanks >> >> Michal >> >> dmesg output (OK): >> >> [9831345.731764] UDP: bad checksum. From 212.100.208.26:54727 to >> 80.74.153.213:53 ulen 57 >> [9831345.733800] UDP: bad checksum. From 212.100.208.26:48493 to >> 80.74.153.213:53 ulen 57 >> [9909484.599882] udevd[11916]: starting version 175 >> [9909534.884523] br1: port 1(tap0) entering forwarding state >> [9909534.885352] br1: port 1(tap0) entering disabled state >> [9909538.258828] device tap0 entered promiscuous mode >> [9909538.258924] br1: port 1(tap0) entering forwarding state >> [9909538.258935] br1: port 1(tap0) entering forwarding state >> [9909549.200021] tap0: no IPv6 routers present >> [9909553.312026] br1: port 1(tap0) entering forwarding state >> [9921282.421385] UDP: bad checksum. From 212.100.208.26:63543 to >> 80.74.153.213:53 ulen 55 >> [9921282.691847] UDP: bad checksum. From 212.100.208.26:65016 to >> 80.74.153.213:53 ulen 55 >> [9921282.728186] UDP: bad checksum. From 212.100.208.26:27831 to >> 80.74.153.213:53 ulen 55 >> [9921284.948307] UDP: bad checksum. From 212.100.208.26:54007 to >> 80.74.153.213:53 ulen 57 >> [9921284.949209] UDP: bad checksum. From 212.100.208.26:46662 to >> 80.74.153.213:53 ulen 57 >> [10005170.262659] UDP: bad checksum. From 212.100.208.26:38483 to >> 80.74.153.213:53 ulen 55 >> [10005170.299580] UDP: bad checksum. From 212.100.208.26:58869 to >> 80.74.153.213:53 ulen 55 >> [10005170.619525] UDP: bad checksum. From 212.100.208.26:46438 to >> 80.74.153.213:53 ulen 55 >> [10005170.621082] UDP: bad checksum. From 212.100.208.26:25320 to >> 80.74.153.213:53 ulen 55 >> [10005170.649470] UDP: bad checksum. From 212.100.208.26:62981 to >> 80.74.153.213:53 ulen 55 >> [10005170.994612] UDP: bad checksum. From 212.100.208.26:56499 to >> 80.74.153.213:53 ulen 55 >> [10005170.995377] UDP: bad checksum. From 212.100.208.26:15236 to >> 80.74.153.213:53 ulen 55 >> [10005171.358151] UDP: bad checksum. From 212.100.208.26:31634 to >> 80.74.153.213:53 ulen 57 >> [10005173.617595] UDP: bad checksum. From 212.100.208.26:64246 to >> 80.74.153.213:53 ulen 57 >> [10090014.376687] UDP: bad checksum. From 212.100.208.26:21402 to >> 80.74.153.213:53 ulen 55 >> [10090014.446206] UDP: bad checksum. From 212.100.208.26:45526 to >> 80.74.153.213:53 ulen 55 >> [10090014.683909] UDP: bad checksum. From 212.100.208.26:4994 to >> 80.74.153.213:53 ulen 57 >> >> >> cat kern.log output (malformed) >> >> Feb 25 09:08:00 speernew kernel: 6[409.206 r:pr (ehhpoyr)etrn >> owrigsae<7>[9831345.731764] UDP: bad checksum. rom 21210282:42 o8.413235 ln5 >> Feb 25 09:08:00 speernew kernel: 7[814.380 D:bdceku.Fo >> 1.0.0.6443to8.413235 ln5 >> Feb 26 10:07:00 speernew kernel: [9909553.312026] br1: port 1(tap0) >> entering forwarding statec.Fo 1.0.0.6653t 07.5.1:3ue 5F21.0.6606t >> 07.5.1:3ue 5<7[992128.216 D:bdceku.Fo 1.0.0.6281t 07.5.1:3ue >> 5<7>[9921284.948307] UDP: bad checksum. From 212.100.208.26:54007 to >> 80.74.153.213:53 ulen 57 >> Feb 26 10:07:00 speernew kernel: [9921284.949209] UDP: bad checksum. >> From 212.100.208.26:46662 to 80.74.153.213:53 ulen 57 >> Feb 27 09:25:05 speernew kernel: [10005170.262659] UDP: bad checksum. >> From 212.100.208.26:38483 to 80.74.153.213:53 ulen 55 >> Feb 27 09:25:05 speernew kernel: [10005170.299580] UDP: bad checksum. >> From 212.100.208.26:58869 to 80.74.153.213:53 ulen 55 >> Feb 27 09:25:05 speernew kernel: [10005170.619525] UDP: bad checksum. >> From 212.100.208.26:4638 to8.413235ue5dekum rm2210282:52 o8.413235 ln5 >> Feb 27 09:25:06 speernew kernel: 7[0011385]UP a hcsm rm2210282:13 >> o8.413235 ln5 >> Feb 27 09:25:08 speernew kernel: [10005173.617595] UDP: bad checksum. >> From 212.100.208.26:64246 to 80.74.15.213:53 uln5 >> Feb 28 08:59:09 speernew kernel: [10090014.376687] UDP: bad checksum. >> From 212.100.208.26:21402 to 80.74.153.213:53 ulen 55 >> Feb 28 08:59:09 speernew kernel: [10090014.446206] UD: bad hcsm >> rm2210282:52 o8.413235 ln5 >> Feb 28 08:59:09 speernew kernel: [10090014.683909] UDP: bad checksum. >> From 212.100.208.26:4994 to 80.74.153.213:53 ulen 57 >> >> >> _______________________________________________ >> rsyslog mailing list >> http://lists.adiscon.net/mailman/listinfo/rsyslog >> http://www.rsyslog.com/professional-services/ >> What's up with rsyslog? Follow https://twitter.com/rgerhards >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of >> sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T >> LIKE THAT. > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of > sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T > LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
