[syslog-ng] Writes garbled kernel messages to logs

[shih dane]

2012/6/8 Gergely Nagy <algernon at balabit.hu>:
> shih dane <daneshih1125 at gmail.com> writes:
>
>> Lately I've setup syslog server on Fedora 12
>> l want to get iscsi connection log
>> but get some  garbled kernel messages
>> like this
>> Jun  8 09:56:12 F12DANE kernel: 6MxusadnRT      1
>> Jun  8 09:56:12 F12DANE kernel: 6DtPUnre:       Ys<>aaeunenre:     e
>> Jun  8 09:56:12 F12DANE kernel: 6Erreoeyee:     0<>esoTp:
>> oml<>---------------------------------<>AGTCR[SS] eitrdfbi_espr
>> ff82d810<>SS oi ucsflo I:1fo 7.66.4 o121.51736,
>> Jun  8 09:56:12 F12DANE kernel: 6IceetdiCICneto on o1fo oe q.910.o.irsf:aep
>> Jun  8 09:56:12 F12DANE kernel: 6EtbihdiCIssinfo oe q.910.o.irsf:aep
>> Jun  8 09:56:12 F12DANE kernel: 6Iceetdnme fatv SS esost  niCITre otlGop
>> Jun  8 09:56:15 F12DANE kernel: Received iSCSI login reques rm121.419o
>> C ewr otl121.51736
>> Jun  8 09:56:15 F12DANE kernel: tfo 7.66.4 nTPNtokPra
>> 7.66.7:20<>---------------------------------<>uhehd
>> oe<>edriet         oe<>aaiet          oe<>aRcDtSgetegh   53
>> Jun  8 09:56:15 F12DANE kernel: 6---------------------------------
>> Jun  8 09:56:15 F12DANE kernel: 6---------------------------------
>> Jun  8 09:56:15 F12DANE kernel: 6Iiitrae
>> in19-5cmmcootdn-c<>agtla:         I agt<>agtotlruTg
>> Jun  8 09:56:15 F12DANE kernel: 6DfutieWi:      2<>ealTm2ean
>> 0<>esoTp:         icvr
>> Jun  8 09:56:15 F12DANE kernel: 6---------------------------------
>> Jun  8 09:56:15 F12DANE kernel: 6TRE_OEiCI:Rgsee arcss_t:ff800208
>> Jun  8 09:56:15 F12DANE kernel: 6iCILgnscesu nCD  rm121.419t
>> 7.66.7:201<>nrmne SS oncincutt  rmnd:in19-5cmmcootdn-c<>salse SS eso
>> rmnd:in19-5cmmcootdn-c<>nrmne ubro cieiCIssin o1o SS agtPra
>> ru:1<>ermne SS onci
>
> Hrm... I have a suspicion, that this is due to a bug that was fixed in
> 3.3.4 or 3.3.5. Can you try upgrading your syslog-ng to 3.3.5, and see
> if the problem goes away?
>
> My other idea would be that iscsi is sending multiline messages, and
> that makes syslog-ng unhappy, but.. that should look a bit different, I
> believe.
>
> --
> |8]
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>

upgrade to 3.3.5, but still get garbled kernel messages

scsi message
printk (KERN_INFO, "xxxxxx\n")

or use another function(marco)  to show iscsi information and  avoid these issue

thanks for any advice
Best Regard