Nagios 3.2.0 process dies silently - help!

[Marc Powell]

Please always respond on list so that others now, and in the future, can benefit from your experience. More below...

On Feb 5, 2010, at 12:24 PM, Tony Johansson wrote:

> Nothing special with the install, everything in the same machine.
> Ran strace as suggested:
> strace -fFs512 /usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
> 
> [pid 32731] write(3, "[1265393566.503713] [016.2] [pid=32731] Processed service performance data file output: 1265393559||AHS||C: Drive Space||c:\\ - total: 15.86 Gb - used: 7.60 Gb (48%) - free 8.26 Gb (52%)||c:\\ Used Space=7.60Gb;14.27;15.54;0.00;15.86\n", 232) = 232
> [pid 32731] _llseek(3, 0, [657557], SEEK_CUR) = 0
> [pid 32731] write(6, "1265393559||AHS||C: Drive Space||c:\\ - total: 15.86 Gb - used: 7.60 Gb (48%) - free 8.26 Gb (52%)||c:\\ Used Space=7.60Gb;14.27;15.54;0.00;15.86\n", 144) = -1 EFBIG (File too large)
> [pid 32731] --- SIGXFSZ (File size limit exceeded) @ 0 (0) ---
> [pid 32732] +++ killed by SIGXFSZ +++
> 
> "File size limit exceeded" seems to be the cause, ideas to remedy this?

Looks like your performance data file has exceeded the size limit supported by your OS (probably 2GB). You need to remove it or truncate it. Look at the value of service_perfdata_file in nagios.cfg to determine what/were that file is.

--
Marc


------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
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