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

Nagios segmentation fault on miltiprocessor system #79

Closed
obm0rok opened this issue Aug 27, 2015 · 2 comments
Closed

Nagios segmentation fault on miltiprocessor system #79

obm0rok opened this issue Aug 27, 2015 · 2 comments

Comments

@obm0rok
Copy link

obm0rok commented Aug 27, 2015

Virtual Machine running on Win7 host with Virtualbox 5.0.0
OS: RHEL 6.6
Germand v 0.33
mod_gearman 2.1.2 / 2.1.3
Nagios Core 4.1.1 / 4.1.0 / 4.0.8

mod_gearman installed from rpm, builded using spec file from source.

When i set result_workers=10 on single-proccesor system and then restart nagios i get 10 check_results workers available. Good.
When i add another processor to virtual pc, then nagios crashes

$ tail /var/log/nagios/nagios.log
[1440595985] mod_gearman: initialized version 2.1.3 (libgearman 0.33)
[1440595985] Event broker module '/usr/lib64/mod_gearman2/mod_gearman2.o' initialized successfully.
[1440595986] Successfully launched command file worker with pid 27740
[1440595986] Caught SIGSEGV, shutting down...
[1440595986] Caught SIGSEGV, shutting down...

in this situation nagios works with mod_gearman only if result_workers=1 in mod-gearman2-module.conf
it is testing environment, also we have hardware server, with same setup and same problem.

@sni
Copy link
Owner

sni commented Aug 27, 2015

There is usually no need to set result_workers to anything but 1. I think i would just remove that option.

sni added a commit that referenced this issue Aug 28, 2015
it doesn't make things faster if higher than 1 because those
linked lists use locks anyway and can only be changed serially.
@sni sni closed this as completed Aug 28, 2015
@obm0rok
Copy link
Author

obm0rok commented Aug 28, 2015

Thanks for your answer, peace

sni added a commit that referenced this issue Aug 28, 2015
it doesn't make things faster if higher than 1 because those
linked lists use locks anyway and can only be changed serially.
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

2 participants