{"action":"closed","issue":{"url":"https://api.github.com/repos/elastic/puppet-logstash/issues/216","labels_url":"https://api.github.com/repos/elastic/puppet-logstash/issues/216/labels{/name}","comments_url":"https://api.github.com/repos/elastic/puppet-logstash/issues/216/comments","events_url":"https://api.github.com/repos/elastic/puppet-logstash/issues/216/events","html_url":"https://github.com/elastic/puppet-logstash/issues/216","id":78248137,"number":216,"title":"Should the latest version work with LS 1.5.0-1?","user":{"login":"cwneal","id":5016796,"avatar_url":"https://avatars.githubusercontent.com/u/5016796?v=3","gravatar_id":"","url":"https://api.github.com/users/cwneal","html_url":"https://github.com/cwneal","followers_url":"https://api.github.com/users/cwneal/followers","following_url":"https://api.github.com/users/cwneal/following{/other_user}","gists_url":"https://api.github.com/users/cwneal/gists{/gist_id}","starred_url":"https://api.github.com/users/cwneal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cwneal/subscriptions","organizations_url":"https://api.github.com/users/cwneal/orgs","repos_url":"https://api.github.com/users/cwneal/repos","events_url":"https://api.github.com/users/cwneal/events{/privacy}","received_events_url":"https://api.github.com/users/cwneal/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-05-19T20:57:35Z","updated_at":"2015-06-04T16:42:51Z","closed_at":"2015-06-04T16:42:51Z","body":"I'm having issues with it that I cannot explain.  I'm using the latest puppet-logstash module, and give it a package_url pointing to the 1.5.0-1 RPM, and everything installs fine, but when the service is started, after initializing everything and starting the flow, no events are processed.\r\n\r\nI'm have an input of some Apache access/error logs, use the APACHECOMBINED filter, and output to Kafka and ES.\r\n\r\nThe interesting thing is that if I run logstash from the CLI with the same config file, events are processed fine.  So there seems to be *something* related to the way the service is set up perhaps that is causing issues?\r\n\r\nCan I provide any more information?\r\nI'm seriously stumped on this one.\r\nThank you!\r\nChris"}}