[Nagios-devel] external commands and segfault -- again

[David G. Schlecht]

> > 2. I've had this problem with Nagios 2.4, 2.5 and 2.6.  So, 
> "upgrading"
> > hasn't gotten rid of it.
> > 
> > 3. We are currently running Nagios 2.6 on a 64-bit Linux platform: 
> > SLES-9 x86-64, Kernel 2.6.5-7.267-smp
> > 
> 
> This is the culprit, I guess. As this isn't a widespread 
> problem, I wouldn't be surprised if it's related to 64-bit 
> archs (kernel-2.6.5 is fairly ancient too, but that shouldn't 
> matter as this is the only app you're seeing it in).
> 
> I'm guessing this actually is an SMP-system and that SuSE 
> doesn't install SMP kernels on all systems, correct? If so, 
> this could also be a source of problem for you. Nagios 
> doesn't follow the pthread guidelines very closely and does 
> some pretty inappropriate things post-fork() for being a 
> threaded application. This could be one of those problems 
> that doesn't happen on single-cpu systems because the only 
> cpu doesn't have anything to compete with when racing for the memory.
> 

I've seen this problem on every platform I've used, including z/os,
32-bit 64-bit, sles, RedHat...

I'll admit that the problems with the older platforms and Nagios
versions (v1.2 and up) may have been different though they all appeared
to fail the same to me. My first guess was SLES threading so I ported to
RH and still no happiness.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null