{"action":"closed","issue":{"url":"https://api.github.com/repos/balabit/syslog-ng/issues/1056","repository_url":"https://api.github.com/repos/balabit/syslog-ng","labels_url":"https://api.github.com/repos/balabit/syslog-ng/issues/1056/labels{/name}","comments_url":"https://api.github.com/repos/balabit/syslog-ng/issues/1056/comments","events_url":"https://api.github.com/repos/balabit/syslog-ng/issues/1056/events","html_url":"https://github.com/balabit/syslog-ng/issues/1056","id":155511417,"number":1056,"title":"Problems parsing PROGRAM with TCP","user":{"login":"jguillouf","id":18213520,"avatar_url":"https://avatars.githubusercontent.com/u/18213520?v=3","gravatar_id":"","url":"https://api.github.com/users/jguillouf","html_url":"https://github.com/jguillouf","followers_url":"https://api.github.com/users/jguillouf/followers","following_url":"https://api.github.com/users/jguillouf/following{/other_user}","gists_url":"https://api.github.com/users/jguillouf/gists{/gist_id}","starred_url":"https://api.github.com/users/jguillouf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jguillouf/subscriptions","organizations_url":"https://api.github.com/users/jguillouf/orgs","repos_url":"https://api.github.com/users/jguillouf/repos","events_url":"https://api.github.com/users/jguillouf/events{/privacy}","received_events_url":"https://api.github.com/users/jguillouf/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-05-18T14:11:31Z","updated_at":"2016-05-23T12:46:13Z","closed_at":"2016-05-23T12:46:13Z","body":"Hi,\r\n\r\nI have my syslog-ng server listen on UDP port but we lost many lines each days.\r\n\r\nSo I decided to send logs in TCP.\r\n\r\nIt works well but I have a strange behavior with one rule :\r\n```\r\nsource s_all {\r\n        udp(ip(10.0.0.14));\r\n        tcp(ip(10.0.0.14) max_connections(50));\r\n};\r\n\r\ndestination d_service {\r\n        file(\"/var/log/test/$HOST/$YEAR/$MONTH/$DAY/$PROGRAM\"\r\n                create_dirs(yes)\r\n        );\r\n};\r\n\r\nlog { source(s_all); destination(d_service);  };\r\n```\r\n\r\n\r\nThe rule works fine with UDP, it creates the expected files:\r\n\r\n> - kernel\r\n> - sshd\r\n> - CRON\r\n> - rsyslogd\r\n> etc.\r\n\r\nBut with TCP it writes the same files but also some files like : \r\n\r\n> - 1_choice_0\\\"                                                                 \r\n> - \\\">\\n\r\n> - 1e7172676h38195a_17_1\"                                                          \r\n> - 459edzqd7pl6a777_8_1_choice_2\\\"                                          \r\n> - class=\\\"status                                                                \r\n> - pqzdkqodzq-99001bloirc-problem-36d458sf78788d8d6sfsefee144afc4_4_1\r\n\r\nI looks like HTML code but I don't understand why it creates these files with TCP.\r\n\r\nThe client configuration is the same... I just add a 2nd \"@\" to tell rsyslog to send TCP packets.\r\n\r\nVersion:\r\nsyslog-ng server : 3.3.4.dfsg-2ubuntu1\r\nrsyslod clients : 5.8.6-1ubuntu8.7\r\n\r\nPlease tell me how to solve my problem.\r\n\r\nBest regards,"}}
{"actor":{"display_login":"jguillouf"}}