{"action":"created","issue":{"url":"https://api.github.com/repos/rsyslog/rsyslog/issues/2067","repository_url":"https://api.github.com/repos/rsyslog/rsyslog","labels_url":"https://api.github.com/repos/rsyslog/rsyslog/issues/2067/labels{/name}","comments_url":"https://api.github.com/repos/rsyslog/rsyslog/issues/2067/comments","events_url":"https://api.github.com/repos/rsyslog/rsyslog/issues/2067/events","html_url":"https://github.com/rsyslog/rsyslog/issues/2067","id":275637582,"number":2067,"title":"rsyslog/omkafka segfaults when communicating with Kafka cluster over longer distance","user":{"login":"oysteila","id":18593885,"avatar_url":"https://avatars0.githubusercontent.com/u/18593885?v=4","gravatar_id":"","url":"https://api.github.com/users/oysteila","html_url":"https://github.com/oysteila","followers_url":"https://api.github.com/users/oysteila/followers","following_url":"https://api.github.com/users/oysteila/following{/other_user}","gists_url":"https://api.github.com/users/oysteila/gists{/gist_id}","starred_url":"https://api.github.com/users/oysteila/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oysteila/subscriptions","organizations_url":"https://api.github.com/users/oysteila/orgs","repos_url":"https://api.github.com/users/oysteila/repos","events_url":"https://api.github.com/users/oysteila/events{/privacy}","received_events_url":"https://api.github.com/users/oysteila/received_events","type":"User","site_admin":false},"labels":[{"id":760595807,"url":"https://api.github.com/repos/rsyslog/rsyslog/labels/potential%20bug","name":"potential bug","color":"ea96bd","default":false},{"id":234228732,"url":"https://api.github.com/repos/rsyslog/rsyslog/labels/waitingOnResponse","name":"waitingOnResponse","color":"fef2c0","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2017-11-21T09:18:56Z","updated_at":"2017-12-08T13:38:41Z","closed_at":null,"author_association":"NONE","body":"I am pushing messages to a Kafka cluster in another location in this city. Normally we only do this within sites. Intermittently, rsyslog will segfault: \r\n\r\n```\r\n[8902665.158154] rs:main Q:Reg[19145]: segfault at 0 ip 00007fcf30e66c20 sp 00007fcee4ff8818 error 6 in libc-2.19.so[7fcf30dcc000+1be000]\r\n[8902665.419698] init: rsyslog main process (18123) killed by SEGV signal\r\n[8902665.419726] init: rsyslog main process ended, respawning\r\n```\r\nHere is the omkafka action configuration: \r\n\r\n```\r\n            action(\r\n                name=\"MyLogsOmkafkaKafkaprodRemote\"\r\n                type=\"omkafka\"\r\n                broker=[\"kafka-server1-remote:9092\",\"kafka-server2-remote:9092\",\"kafka-server3-remote:9092\",\"kafka-server4-remote:9092\"]\r\n                partitions.auto=\"on\"\r\n                topic=\"mytopic\"\r\n                confparam=[\"compression.codec=snappy\", \"socket.keepalive.enable=true\", \"queue.buffering.max.messages=200000\", \"queue.buffering.max.ms=1000\"]\r\n                resubmitOnFailure=\"on\"\r\n                template=\"mytemplate-json\"\r\n                action.resumeRetryCount=\"-1\"\r\n            )\r\n\r\n\r\n```\r\nIs the issue here that omkafka is not at all designed for higher-latency network links? Or is there some underlying error that could appear also in our local topologies given, for instance, increased load? \r\n\r\nIf you need any other debug runs, but ask and I shall provide."},"comment":{"url":"https://api.github.com/repos/rsyslog/rsyslog/issues/comments/350265134","html_url":"https://github.com/rsyslog/rsyslog/issues/2067#issuecomment-350265134","issue_url":"https://api.github.com/repos/rsyslog/rsyslog/issues/2067","id":350265134,"user":{"login":"oysteila","id":18593885,"avatar_url":"https://avatars0.githubusercontent.com/u/18593885?v=4","gravatar_id":"","url":"https://api.github.com/users/oysteila","html_url":"https://github.com/oysteila","followers_url":"https://api.github.com/users/oysteila/followers","following_url":"https://api.github.com/users/oysteila/following{/other_user}","gists_url":"https://api.github.com/users/oysteila/gists{/gist_id}","starred_url":"https://api.github.com/users/oysteila/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oysteila/subscriptions","organizations_url":"https://api.github.com/users/oysteila/orgs","repos_url":"https://api.github.com/users/oysteila/repos","events_url":"https://api.github.com/users/oysteila/events{/privacy}","received_events_url":"https://api.github.com/users/oysteila/received_events","type":"User","site_admin":false},"created_at":"2017-12-08T13:38:41Z","updated_at":"2017-12-08T13:38:41Z","author_association":"NONE","body":"In setting up the test server, I just used a simple imfile input connected to an omrelp output, and was actually able to make it segfault quite quickly. The attached Valgrind Memcheck log file should provide you with more detail than the previous log. I'll produce an omkafka run more closely representing our production environment, but this is at least something for now - hopefully it's not simply due to a poorly set up rsyslog installation, since I had to build from source. \r\n[rsyslog-8.32-valgrind-memcheck-imfile-omrelp-segfault.log](https://github.com/rsyslog/rsyslog/files/1542765/rsyslog-8.32-valgrind-memcheck-imfile-omrelp-segfault.log)\r\n"}}
{"actor":{"display_login":"oysteila"}}