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

If you load two ganglia modules with the same name, gmond uses up 100% of available resources #44

Closed
ghost opened this issue Aug 7, 2012 · 1 comment

Comments

@ghost
Copy link

ghost commented Aug 7, 2012

The following configuration in Ganglia (3.4) will give you a really bad day, and cause Ganglia to sit in a loop where it consumes all available memory:

modules {
  module {
    name = "cpu_module"
    path = "/usr/lib/ganglia/modcpu.so"
  }
  module {
    name = "cpu_module"
    path = "/usr/lib64/ganglia/modcpu.so"
  }
}
@hawson
Copy link
Member

hawson commented May 3, 2016

Confirmed. That's pretty awful. However, it only happens if both the name and path are simultaneously duplicated. So if two modules have the same "name", but different "path" attributes, there's no crash. Likewise, different names, pointing to the same .so file also doesn't cause the same problem.

@vvuksan vvuksan closed this as completed in 92a5c12 May 5, 2016
vvuksan added a commit that referenced this issue May 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant