Re: Daily and weekly graph problem

Hi Marc,

 

I found out the root cause of the problem.

 

When I took the link from the html source and paste it in the browser, I
found that Daily and Weekly link could not open the graph because of
permission. Monthly and Yearly works fine.

 

This is the sample link for Daily Graph;

http://server_ip_address/cricket/mini-graph.cgi?type=png;target=%2Froute
r-interfaces%2FROUTER_NAME%2Ffastethernet1_0;inst=0;dslist=ifInOctets%2C
ifOutOctets;range=86400;rand=630

 

In Windows implementation of Cricket, when the link for router
interfaces utilization is viewed, mini-graph.cgi creates temp files in
Drive:\Windows\Temp\cricket-cache for that interface Daily, Weekly,
Monthly, and Yearly graph in the following format;

cricket-8_characters_of_numbers_and_letters.png

 

There was a permission problem with the Daily and Weekly PNG file. I
deleted all the files so that the new ones will inherit the parent
directory permission. Not deleting it, the update will inherit the
existing permission of the file.

 

Regards,

Dandy

 

-----Original Message-----
From: Marc Powell [mailto:[email protected]] 
Sent: Tuesday, January 06, 2009 11:01 AM
To: [email protected]
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

[email protected]

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

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword