Re: [Nagios-devel] Bug in Performance Data

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] Bug in Performance Data

Post by Guest »

--0-1623851967-1281048317=:33542
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Thank you, Ethan for your response. =0AThe CGI reads status.dat. =0A=0AHere=
are some lines from one of the blocks:=0Aservicestatus {=0A=A0=A0=A0=A0=A0=
=A0=A0 host_name=3Dwtf3a=0A=A0=A0=A0=A0=A0=A0=A0 service_description=3Dchec=
k_ses=0A=A0=A0=A0=A0=A0=A0=A0 modified_attributes=3D0=0A=A0=A0=A0=A0=A0=A0=
=A0 check_command=3Dcheck_ddnfaults_ses=0A=A0=A0=A0=A0=A0=A0=A0 check_perio=
d=3D24x7=0A=A0=A0=A0=A0=A0=A0=A0 notification_period=3D24x7=0A=A0=A0=A0=A0=
=A0=A0=A0 check_interval=3D5.000000=0A=A0=A0=A0=A0=A0=A0=A0 retry_interval=
=3D1.000000=0A=A0=A0=A0=A0=A0=A0=A0 event_handler=3D=0A=A0=A0=A0=A0=A0=A0=
=A0 has_been_checked=3D1=0A=A0=A0=A0=A0=A0=A0=A0 should_be_scheduled=3D1=0A=
=A0=A0=A0=A0=A0=A0=A0 check_execution_time=3D46912587.078=0A=A0=A0=A0=A0=A0=
=A0=A0 check_latency=3D0.399=0A=A0=A0=A0=A0=A0=A0=A0 check_type=3D0=0A=A0=
=A0=A0=A0=A0=A0=A0 current_state=3D0=0A=A0=A0=A0=A0=A0=A0=A0 last_hard_stat=
e=3D0=0A=A0=A0=A0=A0=A0=A0=A0 last_event_id=3D87848=0A=A0=A0=A0=A0=A0=A0=A0=
current_event_id=3D87862=0A=A0=A0=A0=A0=A0=A0=A0 current_problem_id=3D0=0A=
=A0=A0=A0=A0=A0=A0=A0 last_problem_id=3D43437=0A=A0=A0=A0=A0=A0=A0=A0 curre=
nt_attempt=3D1=0A=A0=A0=A0=A0=A0=A0=A0 max_attempts=3D3=0A=A0=A0=A0=A0=A0=
=A0=A0 state_type=3D1=0A=A0=A0=A0=A0=A0=A0=A0 last_state_change=3D128072532=
3=0A=A0=A0=A0=A0=A0=A0=A0 last_hard_state_change=3D1280082023=0A=A0=A0=A0=
=A0=A0=A0=A0 last_time_ok=3D1281047224=0A=A0=A0=A0=A0=A0=A0=A0 last_time_wa=
rning=3D0=0A=A0=A0=A0=A0=A0=A0=A0 last_time_unknown=3D1280725253=0A=A0=A0=
=A0=A0=A0=A0=A0 last_time_critical=3D1280081723=0A=A0=A0=A0=A0=A0=A0=A0 plu=
gin_output=3DCHECK_DDN_ENCLOSURE OK - No errors were found.=0A***=0A=0APlea=
se notice the check_execution time as more than a year in seconds. =0A=0AI =
don't see anything time-change related in the logs. After I filter out =0Ah=
ost/service alerts/notifications, nothing but auto-saves and start/stop =0A=
information remain as follows: =0A=0A=0A[1281028702] Auto-save of retention=
data completed successfully.=0A[1281028706] Caught SIGTERM, shutting down.=
..=0A[1281028706] Successfully shutdown... (PID=3D6509)=0A[1281028706] Even=
t broker module '/usr/local/nagios/modules/dnxServer.so' =0Adeinitialized s=
uccessfully.=0A[1281028727] Nagios 3.2.1 starting... (PID=3D28820)=0A[12810=
28727] Local time is Thu Aug 05 10:18:47 PDT 2010=0A[1281028727] LOG VERSIO=
N: 2.0=0A[1281028727] Event broker module '/usr/local/nagios/modules/dnxSer=
ver.so' =0Ainitialized successfully.=0A[1281028728] Finished daemonizing...=
(New PID=3D28821)=0A[1281028763] EXTERNAL COMMAND: =0ASCHEDULE_FORCED_SVC_=
CHECK;nagios06;check_app_java_cluster;1281028760=0A[1281029029] Auto-save o=
f retention data completed successfully.=0A=0A=0AHere is the detail from th=
e =0Ahttps://nagios06.internal.shutterfly.com/nagios/cgi-bin/extinfo.cgi?ty=
pe=3D4=0A=0AMetric=0AMin.=0AMax.=0AAverage=0ACheck Execution Time:=A0=A0 0.=
00 sec 46912714.32 sec 26955114.505 sec =0ACheck Latency: 0.00 sec 3.40 sec=
0.277 sec =0APercent State Change: 0.00% 37.43% 0.33% =0A=0A=0AIf I stop =
Nagios and remove retention.dat and status.dat and restart fresh, =0ANagios=
looks normal for about 2 minutes and then reports the 1.5 year execution =
=0Atime. =0A=0A=0AAny idea on how to investigate and fix this bug? =0A=0ATh=
ank you!=0A=0A-Larry Findley=0A=0ASr. Systems Engineer =0AShutterfly=0A=0Al=
[email protected] =0A=0A=0A________________________________=0AFrom: Et=
han Galstad =0ATo: Nagios Developers List =0ASent: Wed, August 4, 2010 6:22:10 PM=0ASubject: =
Re: [Nagios-devel] Bug in Performance Data=0A=0AAre there any message in th=
e Nagios log file that relate to detected =0Atime changes?=0A=0AThe (stated=
) execution time for these checks is approx 542 days, which =0Ais strange.=
=A0 Most time issues would show just a few hours offset, not =0Aalmost 2 ye=
ars time.=0A=0AWhat times are reflected in the status.dat file?=A0

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked