***buffer overflow detected***: sidekiq 4.0.1 gitlab [0 of 10 busy] terminated
Created by: kesin
We‘re using sidekiq 4.0.1 in gitlab production mode but the sidekiq process was self terminated yesterday with errors below:
*** buffer overflow detected ***: sidekiq 4.0.1 gitlab [0 of 25 busy] terminated
Backtrace
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7338f)[0x7f39501b738f]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f395024ec9c]
/lib/x86_64-linux-gnu/libc.so.6(+0x109b60)[0x7f395024db60]
/lib/x86_64-linux-gnu/libc.so.6(+0x10abe7)[0x7f395024ebe7]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(+0x30a39)[0x7f3947101a39]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(+0x30ae1)[0x7f3947101ae1]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(+0xb5a6f)[0x7f3947186a6f]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(+0xb4601)[0x7f3947185601]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(+0xb70e8)[0x7f39471880e8]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(+0xb4b23)[0x7f3947185b23]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(git_remote_connect+0xa4)[0x7f394711ddf4]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/rugged-37cae2f6479d/ext/rugged/../../vendor/libgit2/build/libgit2.so.23(git_remote_fetch+0x71)[0x7f394711f1e1]
/home/zoker/gitlab/vendor/bundle/ruby/2.1.0/bundler/gems/extensions/x86_64-linux/2.1.0/rugged-37cae2f6479d/rugged/rugged.so(+0xd05b)[0x7f39473cc05b]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1cb144)[0x7f39506d4144]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1cfb64)[0x7f39506d8b64]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d370c)[0x7f39506dc70c]
/home/zoker/ruby/lib/libruby.so.2.1(rb_yield+0x26f)[0x7f39506e3e1f]
/home/zoker/ruby/lib/libruby.so.2.1(rb_ary_each+0x52)[0x7f3950536fa2]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d7c01)[0x7f39506e0c01]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d77b1)[0x7f39506e07b1]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d04a5)[0x7f39506d94a5]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d370c)[0x7f39506dc70c]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d69bf)[0x7f39506df9bf]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d69fa)[0x7f39506df9fa]
/home/zoker/ruby/lib/libruby.so.2.1(+0x86550)[0x7f395058f550]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1cb144)[0x7f39506d4144]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1cfb64)[0x7f39506d8b64]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d370c)[0x7f39506dc70c]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d45c4)[0x7f39506dd5c4]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d5247)[0x7f39506de247]
/home/zoker/ruby/lib/libruby.so.2.1(rb_method_call_with_block+0x10a)[0x7f39505917fa]
/home/zoker/ruby/lib/libruby.so.2.1(+0x88959)[0x7f3950591959]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d265f)[0x7f39506db65f]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d370c)[0x7f39506dc70c]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d69bf)[0x7f39506df9bf]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1d69fa)[0x7f39506df9fa]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1ec87d)[0x7f39506f587d]
/home/zoker/ruby/lib/libruby.so.2.1(+0x1ecbdb)[0x7f39506f5bdb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f394ff2e182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f395023e47d]I have to start it up manually.
queues on sidekiq is just ['post_receive', 'gitlab_shell', 'system_hook', 'common']
How does this crash happened and how can I prevent this crash happen again?
any help would be appreciated, thx