We have experienced this with version 3.5.0 too - last night... But we didn´t get any segfaults anywhere - Nagios did just report (in it`s log) that it was shutdown at midnight - and nothing after that.

Archives logrotate gives SIGSEGV Signal to Nagios
DIstribution : Debian i686 version 7.
Nagios Core : 3.5.0 Installed by compilation of source .
There was no problem during 2 month and one day ...
I am having an issue with nagios and the archive/log rotation. I have
configured "log_rotation_method=d" and when it runs I see a SIGSEGV in the
nagios.log and nagios shutsdown. I can move it to =h and it will do it every
hour (crash). The logfile has nothing else to indicate why it is crashing.

Anyone have suggestions on how to trace down the real problem here? File
permissions on the archive dir are nagios:nagios as is the nagios.log file.

There is no new archive log since this crashdate.
I've set "log_rotation_method=n" because this server is on 24/7 production but i think it isn't the right way
Actually, 53 Day Logs rotate OK, 75% free space on disk.

Did you need any further informations (logs,...)?

(0000816)
awiddersheim (reporter)2013-09-23 14:00

I ran into this issue in conjunction with the livestatus NEB module after the 3.5.0 release of Nagios or whatever release finally implemented fixes for downtime notifications being resent.

If you aren't using livestatus and this is happening that I'm not sure what the problem is and you'll have to wait for devs to look into it.

(0000861)
hsmade (reporter)2013-10-08 04:38

That patch fixed it for me

(0001142)
PMDubuc (reporter)2014-03-10 16:38

I'm also seeing this with Nagios 3.5.1. It seems only to happen when there are services that have a downtime scheduled. I'm using livestatus 1.2.2p3. I haven't tried the patch to the nagios downtime struct. Is that patch safe to use where scheduled downtimes are concerned? Will that patch be incorporated into a future release of 3.5?

(0001143)
awiddersheim (reporter)2014-03-10 16:42

That patch works for me currently. Been using it in production for several months without any issues. As for it being added to 3.5.1, as far as I know there will no longer be any updates to the 3.x branch and it is encouraged for people to upgrade to 4.x.