{"action":"opened","issue":{"url":"https://api.github.com/repos/logstash-plugins/logstash-input-beats/issues/259","repository_url":"https://api.github.com/repos/logstash-plugins/logstash-input-beats","labels_url":"https://api.github.com/repos/logstash-plugins/logstash-input-beats/issues/259/labels{/name}","comments_url":"https://api.github.com/repos/logstash-plugins/logstash-input-beats/issues/259/comments","events_url":"https://api.github.com/repos/logstash-plugins/logstash-input-beats/issues/259/events","html_url":"https://github.com/logstash-plugins/logstash-input-beats/issues/259","id":262058756,"number":259,"title":"Logstash-input-beats connections still doesn’t close properly","user":{"login":"amirvaza","id":25140441,"avatar_url":"https://avatars2.githubusercontent.com/u/25140441?v=4","gravatar_id":"","url":"https://api.github.com/users/amirvaza","html_url":"https://github.com/amirvaza","followers_url":"https://api.github.com/users/amirvaza/followers","following_url":"https://api.github.com/users/amirvaza/following{/other_user}","gists_url":"https://api.github.com/users/amirvaza/gists{/gist_id}","starred_url":"https://api.github.com/users/amirvaza/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amirvaza/subscriptions","organizations_url":"https://api.github.com/users/amirvaza/orgs","repos_url":"https://api.github.com/users/amirvaza/repos","events_url":"https://api.github.com/users/amirvaza/events{/privacy}","received_events_url":"https://api.github.com/users/amirvaza/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-02T11:44:15Z","updated_at":"2017-10-02T11:44:15Z","closed_at":null,"author_association":"NONE","body":"- Version: 5.0.1 / 3.1.24\r\n- Operating System: ec2 linux\r\n- Config File: follow\r\n- Sample Data:\r\n- Steps to Reproduce: every run\r\n\r\nI have around 50 filebeats with this configuration:\r\n\r\n`output:\r\n  logstash:\r\n    hosts: [\"******:10200\"]\r\nshipper:\r\nlogging:\r\n  level: warning\r\n  to_files: true\r\n  to_syslog: false\r\n  files:\r\n    path: /var/log/filebeat\r\n    name: filebeat.log\r\n    rotateeverybytes: 1000000\r\n    keepfiles: 5\r\nfilebeat:\r\n  prospectors:\r\n    - paths:\r\n        - ******\r\n      encoding: utf-8\r\n      input_type: log\r\n      fields:\r\n        type: \"***\"\r\n        component: \"***\"\r\n      fields_under_root: true\r\n      multiline:\r\n        pattern: ^[0-9][0-9][0-9][0-9]-[0-9][0-9]\r\n        negate: true\r\n        match: after`\r\n\r\nAnd my logstash configuration:\r\n`input {\r\n beats {\r\n    port => 10200\r\n  }\r\n}\r\n\r\noutput\r\n{\r\n  elasticsearch {\r\n    hosts => [\"localhost\"]\r\n  }\r\n`\r\n\r\nAfter a day or two the logstash service stops working since it has too many opened connection and I have to restart the service.\r\nThe output of netstat -p shows 16k lines of CLOSE_WAIT\r\nAfter a search I saw in github a fix related to this issue in version 3.1.24 (and 5.0.1), both versions didn't seem to fix it for me.\r\nIt seems that the plugin still doesn't close the connections properly.\r\nOr maybe I am doing something wrong?\r\n\r\nMy Logstash version is 5.6.2\r\n\r\nThanks."}}
{"actor":{"display_login":"amirvaza"}}