Echo21bash

1.logs  2.yum https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng337/repo/epel-7/czanik-syslog-ng337-epel-7.repo 3.iconv version  4.OS 

Thank you. Let me test it

This bug seems to have been fixed, and the log is not broken  

I would like to know the reason for the code parsing error and the parameter log-msg-size(); Does it have anything to do with it?

I also want to give you the log, but I found that the log is missing seriously, and the faulty syslog input log cannot be located. This is the log...

10.76.230.114 device sends syslog log to UDP515 port, GB18030 encoding，10.76.230.50 device sends syslog logs to UDP514 port, encoding no. 

okay

 The original data is as follows 3c,39,30,31,3e,4a,75,6c,20,32,31,20,32,33,3a,31,30,3a,33,37,20,68,6f,73,74,20,57,41,47,3a,20,53,65,72,69,61,6c,4e,75,6d,3d,30,31,32,33,32,31,31,39,30,31,30,39,39,39,39,39,20,47,65,6e,54,69,6d,65,3d,22,32,30,32,32,2d,30,37,2d,32,31,20,32,33,3a,31,30,3a,33,37,22,20,4d,6f,64,75,6c,65,3d,54,43,50,5f,5a,6f,6f,4b,65,65,70,65,72,5f,ce,b4,ca,da,c8,a8,b7,c3,ce,ca,c2,a9,b6,b4,20,53,72,63,49,50,3d,31,30,2e,37,36,2e,32,33,30,2e,31,34,35,20,44,73,74,49,50,3d,34,37,2e,31,30,30,2e,33,36,2e,32,34,36,20,53,72,63,50,6f,72,74,3d,33,39,30,30,31,20,44,73,74,50,6f,72,74,3d,32,31,38,31,20,49,6e,3d,67,65,30,2f,32,20,4f,75,74,3d,67,65,30,2f,31,20,41,63,74,69,6f,6e,3d,64,72,6f,70,20,55,52,4c,3d,22,63,64,6d,65,74,72,6f,2e,63,6e,7a,68,69,79,75,61,6e,68,75,69,2e,63,6f,6d,2f,6f,70,2f,73,74,61,74,69,6f,6e,2d,74,69,6d,65,22,20,43,6f,6e,74,65,6e,74,3d,22,74,64,70,5f,64,70,6f,72,74,3d,32,31,38,31,3b,54,43,50,5f,44,61,74,61,3d,73,74,61,74,69,6f,6e,43,6f,64,65,22,3a,20,22,31,35,22,2c,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,22,74,72,61,6e,73,66,65,72,4c,69,6e,65,73,22,3a,20,22,30,33,22,2c,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,22,73,74,61,72,74,54,69,6d,65,22,3a,20,22,30,36,3a,31,36,22,2c,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,2022,65,6e,64,54,69,6d,65,22,3a,20,22,32,33,3a,32,31,22,2c,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,22,73,65,71,75,65,6e,63,65,22,3a,20,31,35,2c,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,22,73,74,61,74,69,6f,6e,4e,61,6d,65,5a,68,22,3a,20,22,e6,9d,8e,e5,ae,b6,e6,b2,b1,22,2c,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,22,73,74,61,74,69,6f,6e,43,6f,64,65,73,22,3a,20,5b,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,7b,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,22,6c,69,6e,65,4e,6f,22,3a,20,22,30,33,22,2c,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,22,73,74,61,74,69,6f,6e,43,6f,64,65,22,3a,20,22,31,35,22,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,7d,0a,20,20,20,20,20,20,20,20,20,20,20,20,20,20,5d,0a,20,20,20,20,20,20,20,20

Could this be the problem caused by the same device sending two different encodings? My test environment uses the UTF-8 encoded linux server to send syslog logs with Chinese characters...

I only have one device whose syslog log is sent to port 515 encoded by GB8030, and the rest of the devices are sent to port 514 without a specified...