reporting notification log issue

[Thierry Demogeot]

Hi Richard,

Thanks for the help and advice.

nagios.log was readable by http process.

problem has solved by itself: for any reason,
- Alert History start working the second day nagios was running (whereas
the first day it didn't work).
- Trends display start working the third day (this AM CET). whereas it
didn't work well the fisrt two days.

I guess various logging and parsing script of nagios only work well when
there is a few historical data (they  are "lost" when nagios has just
been configured and started?).


Thanks
Thierry

Richard NAGY wrote:

> Hello Thierry,
> 
> The nagios process was probably running under the nagios user, which is 
> good. Log files was owned by nagios as well. But these were probably not 
> readable by the group 'other', which was the group the apache user was 
> in. So apache (via CGI) could not read the files. The archives directory 
> (and its files) also must be readable by apache. Log files are important 
> for nagios as it use them to procuce graphs.
> 
> Hope this helps.
> 
> PS : seems you have problem with nagios.cfg. Where is it located? Does 
> nagios look for this file at the right place? ( " [1088238249] Error: 
> Cannot open main configuration file '/usr/local/nagios/bin/start' for 
> reading! ")
> 
> Thierry Demogeot a écrit :
> 
>> Hi
>>
>> I am a new nagios user.
>>
>> I have nagios installed, configured and running. Set up web interface
>> and monitoring a few hosts/routers.
>>
>> Monitoring itself and notification  via email
>> are both working fine as well as various Monitroing view from the web
>> interface.
>>
>> I am trying to use Reporting, Trends, Availability, ... and have some
>> issue. While trying to see Trends (for service that failed a couple of
>> time), I got the nice png with all zero (ok, warning, unkn.,crit.,int).
>>
>> Same if I try to see Alert History: there i can just see time of nagios
>> restart. No info regarding Alert history...whereas I received Alert by
>> email.
>>
>> Note:
>> In nagios.cfg I have turned on use_syslog=1 and
>> I can see that Alert are logged to syslog (/var/log/syslog).
>> My undestanding is that cgi scripts (like trends.cgi) look into
>> /usr/local/nagios/var/nagios.log to figure out what's the trend is ? But
>> I cannot see any Alert in nagios.log ( /usr/local/nagios/var/nagios.log)
>> ? Is this normal ?
>>
>>
>> Any idea what I could have missed during the installation to prebent 
>> me seeing history and trends displayed properly ?
>>
>> Thanks in advance
>> Cheers
>>
>> PS: below a couple of detailled information.
>>
>> --- Alert History result (via history.cgi):
>>
>> [26-06-2004 18:00:29] Nagios 1.2 starting... (PID=32323)
>>
>> [26-06-2004 15:24:57] Nagios 1.2 starting... (PID=2726)
>> [26-06-2004 15:09:54] Nagios 1.2 starting... (PID=31242)
>>
>> [26-06-2004 14:51:48] Nagios 1.2 starting... (PID=20014)
>>
>> [26-06-2004 14:40:25] Nagios 1.2 starting... (PID=19797)
>>
>> [26-06-2004 13:34:02] Nagios 1.2 starting... (PID=26090)
>>
>> [26-06-2004 11:59:06] Nagios 1.2 starting... (PID=30323)
>>
>> [26-06-2004 10:24:09] Bailing out due to one or more errors encountered
>> in the configuration files. Run Nagios from the command line with the -v
>> option to verify your config before restarting. (PID=27840)
>> [26-06-2004 10:24:09] Nagios 1.2 starting... (PID=27840)
>>
>>
>>
>> --- /usr/local/nagios/var/nagios.log
>> root# more /usr/local/nagios/var/nagios.log
>> [1088238249] Error: Cannot open main configuration file
>> '/usr/local/nagios/bin/start' for read
>> ing!
>> [1088238249] Nagios 1.2 starting... (PID=27840)
>> [1088238249] Bailing out due to one or more errors encountered in the
>> configuration files.  Ru
>> n Nagios from the command line with the -v option to verify your config
>> before restarting. (PI
>> D=27840)
>> [1088243946] Nagios 1.2 starting... (PID=30323)
>> [1088243946] Finished daemonizing... (New PID=30324)
>> [1088249642] Nagios 1.2 starting... (PID=26090)
>> [1088249642] Finished daemonizing... (New PID=26091)
>> [1088253625] Nagios 1.2 starting... (PID=19797)
>> [1088253625] Finished daemonizing... (New PID=19798)
>> [1088254308] Nagios 1.2 starting... (PID=20014)
>> [1088254308] Finished daemonizing... (New PID=20015)
>> [1088255394] Nagios 1.2 starting... (PID=31242)
>> [1088255394] Finished daemonizing... (New PID=31243)
>> [1088256297] Nagios 1.2 starting... (PID=2726)
>> [1088256297] Finished daemonizing... (New PID=2727)
>> [1088265629] Nagios 1.2 starting... (PID=32323)
>> [1088265629] Finished daemonizing... (New PID=32324)
>> toonlite:/home/thierry/d2/libpng-1.2.5#
>>
>> --- /var/log/syslog extract
>> Jun 26 18:03:49 toonlite nagios: SERVICE ALERT:
>> vip.msw.lnd.m2m;PING;OK;HARD;1;PING OK - Packet loss = 0%, RTA = 15.30 ms
>> Jun 26 18:46:09 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;1;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:46:19 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;2;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:46:29 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;3;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:46:39 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;4;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:46:49 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;5;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:46:59 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;6;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:47:09 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;7;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:47:19 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;8;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:47:29 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;SOFT;9;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:47:39 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;DOWN;HARD;10;CRITICAL - Plugin timed out after
>> 10 seconds
>> Jun 26 18:47:39 toonlite nagios: HOST NOTIFICATION:
>> nagios;ipphone.tdhome.val.ch.m2m;DOWN;host-notify-by-email;CRITICAL -
>> Plugin timed out after 10 seconds
>> Jun 26 18:47:39 toonlite nagios: SERVICE ALERT:
>> ipphone.tdhome.val.ch.m2m;PING;CRITICAL;HARD;1;CRITICAL - Plugin timed
>> out after 10 seconds
>> Jun 26 18:51:59 toonlite nagios: HOST ALERT:
>> ipphone.tdhome.val.ch.m2m;UP;HARD;1;PING OK - Packet loss = 0%, RTA =
>> 28.10 ms
>> Jun 26 18:51:59 toonlite nagios: HOST NOTIFICATION:
>> nagios;ipphone.tdhome.val.ch.m2m;UP;host-notify-by-email;PING OK -
>> Packet loss = 0%, RTA = 28.10 ms
>> Jun 26 18:51:59 toonlite nagios: SERVICE ALERT:
>> ipphone.tdhome.val.ch.m2m;PING;OK;HARD;1;PING OK - Packet loss = 0%, RTA
>> = 28.00 ms
>> Jun 26 19:00:29 toonlite nagios: Auto-save of retention data completed
>> successfully.
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email sponsored by Black Hat Briefings & Training.
>> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital 
>> self defense, top technical experts, no vendor pitches, unmatched 
>> networking opportunities. Visit www.blackhat.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
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital 
> self defense, top technical experts, no vendor pitches, unmatched 
> networking opportunities. Visit www.blackhat.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
> 
> 



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.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