Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

collectd is killed by collectdmon while running java org.collectd.java.GenericJMX plugin #2321

Closed
anryko opened this issue Jun 20, 2017 · 7 comments

Comments

@anryko
Copy link

anryko commented Jun 20, 2017

  • Version of collectd: 5.4.0, 5.5.2
  • Operating system / distribution: Ubuntu 14.04 LTS

Expected behavior

java org.collectd.java.GenericJMX plugin is working.

Actual behavior

collectd process is killed by collectdmon

2017-06-20T19:50:20.172523+02:00 hostname collectdmon[16225]: Warning: collectd was terminated by signal 11 (core dumped)
2017-06-20T19:50:20.172532+02:00 hostname collectdmon[16225]: Error: collectd is respawning too fast - disabled for 300 seconds

Steps to reproduce

Update Ubuntu 14.04 LTS to latest version and run collectd with example plugin configuration

LoadPlugin java

<Plugin java>
    JVMArg "-verbose:jni"
    JVMArg "-Djava.class.path=/usr/share/collectd/java/collectd-api.jar:/usr/share/collectd/java/generic-jmx.jar"
    LoadPlugin "org.collectd.java.GenericJMX"
</Plugin>
@ennioj
Copy link

ennioj commented Jun 21, 2017

Hi,
same problem here(same versions as above), I wanted to add a hint:
On systems with:
$ uname -r
3.13.0-119-generic
Works
the update to 3.13.0-121-generic brakes it

strace collectd -C /etc/collectd/collectd.conf -f show that we got a segfault:

--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7ffe507e21e0} ---
rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], ~[KILL STOP RTMIN RT_1], 8) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7ffe507e2ff0} ---
+++ killed by SIGSEGV +++
Segmentation fault 

@nanjj
Copy link

nanjj commented Jun 26, 2017

Looks it's caused by kernel issues here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

@pcummins
Copy link

I can second this bug impacts CentOS 7.3 with CollectD 5.7.1 and Sun Java 8u131. Introduced with 3.10.0-514.21.2.el7 and resolved by rolling back to 3.10.0-514.21.1.el7.x86_64.

@iwan41
Copy link

iwan41 commented Jun 28, 2017

Use: -Xss1280k to workaround this issue until kernel patch will be release (workaround is in @nanjj link).

Try

LoadPlugin java

<Plugin java>
    JVMArg "-verbose:jni"
   JVMArg "-Xss1280k"
    JVMArg "-Djava.class.path=/usr/share/collectd/java/collectd-api.jar:/usr/share/collectd/java/generic-jmx.jar"
    LoadPlugin "org.collectd.java.GenericJMX"
</Plugin>

@rubenk
Copy link
Contributor

rubenk commented Jun 29, 2017

Closing since this is not a collectd issue.

@rubenk rubenk closed this as completed Jun 29, 2017
@jbehrends
Copy link

jbehrends commented Jul 13, 2017

After upgrading a CentOS 6.x system to latest 6, I just ran into this issue.
Here are my versions:

CentOS release 6.9 (Final)
kernel: 2.6.32-696.3.2.el6.x86_64
java version "1.8.0_92"
collectd 5.7.2

https://access.redhat.com/solutions/3091371

@rubenk
Copy link
Contributor

rubenk commented Jul 14, 2017

@jbehrends there's a newer kernel for CentOS 6 that should solve it:

  • [mm] allow JVM to implement its own stack guard pages (Larry Woodman) [1466667 1464237]
  • [mm] enlarge stack guard gap (Larry Woodman) [1466667 1464237]
  • Revert: [mm] enlarge stack guard gap (Larry Woodman) [1466667 1464237]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants