Re: [cricket-users] Daily and weekly graph problem

[Danilo C. D. N. <dc...@nc...>]

Hi Marc,

 

As mentioned, I enabled cricket-conf.pl and use "$gLogLevel = "debug";"
the results;

-          no log in cricket

-          in IIS HTTPERR, the logs shows "- Timer_ConnectionIdle -"

 

I'm going to research what the IIS HTTPERR means.

 

Regards,

Dandy

________________________________

From: Danilo Castro Dy NCS 
Sent: Tuesday, January 06, 2009 11:09 AM
To: 'Marc Powell'; cri...@li...
Subject: RE: [cricket-users] Daily and weekly graph problem

 

Hi Marc,

 

I just enabled it, but its not showing any error in the cricket logs and
web server logs.

 

Additional info regarding the graph problem; For the FastEthernet1_0 the
Daily Graph and Weekly Graph for Octets is not shown but the Daily Graph
and Weekly Graph for UcastPackets and Errors are shown

 

Thanks,

Dandy

 

-----Original Message-----
From: Marc Powell [mailto:ma...@en...] 
Sent: Tuesday, January 06, 2009 11:01 AM
To: cri...@li...
Subject: Re: [cricket-users] Daily and weekly graph problem

 

 

On Jan 5, 2009, at 8:35 PM, Danilo Castro Dy NCS wrote:

 

> I'm not using cricket-conf.pl

 

I think you have to be unless you're using a very old version of  

cricket. It's the main cricket configuration file used by the grapher,  

collector, etc to know what their run-time options are. It's found in  

the same directory as those scripts.

 

> 

> Here is the Web Server Log

 

> 2009-01-06 01:44:23 W3SVC1694684274 192.168.2.13 GET /cricket/ 

> grapher.cgi target=%2Frouter-interfaces 

> %2FNCSAMKCRT1%2Ffastethernet1_0;view=Octets 80 - 202.6.167.136  

> Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1) 200 0 0

> 2009-01-06 01:44:23 W3SVC1694684274 192.168.2.13 GET /cricket/mini- 

> graph.cgi type=png;target=%2Frouter-interfaces 

> %2FNCSAMKCRT1%2Ffastethernet1_0;inst=0;dslist=ifInOctets 

> %2CifOutOctets;range=86400;rand=569 80 - 202.6.167.136 Mozilla/4.0+ 

> (compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1) 200 0 64

> 2009-01-06 01:44:23 W3SVC1694684274 192.168.2.13 GET /cricket/mini- 

> graph.cgi type=png;target=%2Frouter-interfaces 

> %2FNCSAMKCRT1%2Ffastethernet1_0;inst=0;dslist=ifInOctets 

> %2CifOutOctets;range=604800;rand=933 80 - 202.6.167.136 Mozilla/4.0+ 

> (compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1) 200 0 64

> 2009-01-06 01:44:27 W3SVC1694684274 192.168.2.13 GET /cricket/mini- 

> graph.cgi type=png;target=%2Frouter-interfaces 

> %2FNCSAMKCRT1%2Ffastethernet1_0;inst=0;dslist=ifInOctets 

> %2CifOutOctets;range=86400;rand=569 80 - 202.6.167.136 Mozilla/4.0+ 

> (compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1) 502 2 0

 

This looks like an access log. What you're looking for is the error  

log. If this is IIS6, I believe it's called HTTPERR based on some  

google searches (but I don't use IIS).

 

Typically what you're seeing is caused by a specifying a view that  

doesn't have a definition or using named DS's that don't match what's  

in the RRD file. Again, the web servers error logs should detail  

exactly what's wrong, especially if you increase the loglevel.

 

--

Marc

 

 

------------------------------------------------------------------------
------

_______________________________________________

cricket-users mailing list

cri...@li...

https://lists.sourceforge.net/lists/listinfo/cricket-users