-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/10/08 01:26 PM, Tim Pushor wrote: > Hello everyone, > > While not specifically a nagios issue, I am setting up a nagios > installation to monitor a server that is used to run an interactive > application by several users at once (> 50). The problem is, > occasionally the application dumps core, and the users don't always > notify us when this happens. We'd like to trigger a passive alarm to > nagios on our application dumping core. > > On other OS's (specifically FreeBSD IIRC) the kernel logs coredumps and > end up in the system log so watching the logfiles with swatch or > something similar would do the trick. > > On my Linux system (CentOS 5.2) it appears that coredumps don't log. > Does anyone have any ideas how I can trigger an event on coredump on Linux?
This is not really a nagios issue... AFAIK segfaults are logged in Linux; have you looked at the kernel messages (dmesg)? If it shows in dmesg output but not on your logs, make sure syslog is configured properly to retrieve those messages. You could also log kern.* to a specific files to be sure. I think log levels can also be tuned with /proc/sys/kernel/printk; see "man 5 proc". - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI7GQp6dZ+Kt5BchYRAu8TAJ98E5xxKIRDZh8l/gFPd50uZeNM+QCggpct r7QppHPqVgdZTMZKtgPJYgU= =Ta0T -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Nagios-users mailing list Nagios-users@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
