Nagios 2.0 problems starting [Resolved]

Justin Lambert justin.lambert at computility.com
Mon Nov 8 00:21:33 CET 2004


Unfotunatly after my elation of getting nagios running again I deleted 
the offending files.  In hindsight it would have made a lot more sense 
to keep them so hopefully others wouldn't have this problem.  Next time 
gadget... next time.

jl


Ethan Galstad wrote:
> Could you checkout the latest version from CVS and see if the problem 
> still occurs?  There were a number of segfault bugs the first day or 
> two after I initially introduced the mmap()'ed file I/O, which I have 
> fixed in the past few days.
> 
> 
> On 4 Nov 2004 at 14:39, Justin Lambert wrote:
> 
> 
>>I first tried running gdb on the "make install" version of the nagios
>>binary, gdb said there was no debugging symbols found, so I figure
>>that wouldn't be as useful.  Copied the pre-make install binary (md5
>>sums different) and ran gdb on that.  Here is the output:
>>
>>Program received signal SIGSEGV, Segmentation fault.
>>[Switching to Thread 1074195040 (LWP 32180)]
>>0x4207bfec in memcpy () from /lib/tls/libc.so.6
>>(gdb) where
>>#0  0x4207bfec in memcpy () from /lib/tls/libc.so.6
>>#1  0x0806e5a5 in mmap_fgets (temp_mmapfile=0x4036cffd) at
>>#utils.c:4696 2  0x080704fe in xrddefault_read_state_information (
>>     main_config_file=0x80b56e0 "/etc/nagios/nagios.cfg") at 
>>../xdata/xrddefault.c:393
>>#3  0x0806f7fb in read_initial_state_information (
>>     main_config_file=0x80b56e0 "/etc/nagios/nagios.cfg") at
>>     sretention.c:99
>>#4  0x080533a5 in main (argc=134960864, argv=0x80b56e0) at
>>#nagios.c:612 5  0x42015504 in __libc_start_main () from
>>#/lib/tls/libc.so.6
>>
>>
>>After seeing this I see lines about reading initial_state_information.
>>I tried moving the saved state files somewhere else and nagios appears
>>to be working now.  Thanks for your help guys
>>
>>jl
>>
>>
>>
>>Jason Martin wrote:
>>
>>>On Thu, Nov 04, 2004 at 08:46:13AM +0000, Matthew Kent wrote:
>>>
>>>
>>>>Which should run nagios in the foreground as you've been doing. When
>>>>it dies, just type 'where' or 'bt'. It should show exactly where it
>>>>crapped out. Send that here. Now type 'kill' to end your session.
>>>
>>>I've found that since the 'make install' also strip's the
>>>binary, it is helpful to manually copy the nagios binary out of the
>>>build tree so that extra debugging information is available to gdb.
>>>
>>>-Jason Martin
>>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by:
>>Sybase ASE Linux Express Edition - download now for FREE
>>LinuxWorld Reader's Choice Award Winner for best database on Linux.
>>http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
>>_______________________________________________ Nagios-devel mailing
>>list Nagios-devel at lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/nagios-devel
>>
>>
> 
> 
> 
> 
> Ethan Galstad,
> Nagios Developer
> ---
> Email: nagios at nagios.org
> Website: http://www.nagios.org
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click




More information about the Developers mailing list