Cheshire Cat Computing

I upgraded from 2.15 to 2.17. Is there anyway to get the old functionality back to get the 6 hour graph to update the graph every min with new data? With the new version I have to wait until the graph updates every 5mins. The RRD graph time stamp (withdate = yes) is always in 5min intervals even though I'm viewing a 1min graph.

This functionality should not have changed.

Are you viewing the 6-hour graph? If you view the daily graph, it will only update every 5 mins because that is the granularity of the image you are seeing.

The 6-hour graph (only available if routers2 thinks you are looking at a 1-min interval RRD) should be cached for no more than 50 sec (depending on your .htaccess file if you are using Apache) and will be regenerated as soon as it is >60sec old.

If you are viewing a 6-hr graph, and it only refreshes every 5 mins, then please email me with your .cfg file, and details of your web server (Windows/UNIX, Apache/IIS) and a copy of your .htaccess file for the graphs directory if you are using Apache.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

The browser does actually refresh the page every 60 seconds and I see the 6 hour graph but I only see new graph plot data every 5 mins. The time stamp on the graph is always in 5min intervals. This is the case even if I use the Refresh icon.

I'm using the exact htaccess file that came with the tar. Under my htdocs directive in httpd.conf I have it set with "AllowOverride All" Below is an example of one of my mrtg configs. Thanks

WorkDir: /usr/local/mrtg/switches/sw-01
LogFormat: rrdtool
Interval: 1

Target[GigabitEthernet0_1]: \GigabitEthernet0/1:public@10.10.10.2
SetEnv[GigabitEthernet0_1]: MRTG_INT_IP="" MRTG_INT_DESCR="GigabitEthernet0/1"
Options[GigabitEthernet0_1]: bits
MaxBytes[GigabitEthernet0_1]: 125000000
Title[GigabitEthernet0_1]: GigabitEthernet0/1
PageTop[GigabitEthernet0_1]: <H3>GigabitEthernet0/1</H3>

It sounds as if RRDTool is not updating the graph although routers2 is refrshing at the required frequency.

The graph generation is done with --lazy set, so RRDTool will not do anything if it believes that the data interval > the age of the existing image. This would seem to indicate that your .rrd file is not in the correct data resolution?

Can you tell me (1) your RRDTool version (rrdtool -v), and (2) the output of 'rrdtool info xxx.rrd' for the RRD file corresponding to the target you are viewing? Look for the 'step =' line, which should be 60. If it is 300 then that's your problem.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

I'm using version 1.2.12. I upgraded to 1.2.18 (1.2.19 wouldn't compile) and no difference. My RRD files are all step 60

# rrdtool info gigabitethernet0_1.rrd
filename = "gigabitethernet0_1.rrd"
rrd_version = "0003"
step = 60
last_update = 1173195071
--- SNIP ---

If I go back to using version 2.15 of routers2.cgi I get the 1 min updates, everything works fine. Since the RRD's, RRD version, MRTG configs and routers2.conf are all the same I'm guessing the issue is within routers2.cgi. Thanks for your help.

I will look into this and try to duplicate the behaviour on our system. Since nothing in the caching time code changed since 2.15 I'm not sure what could have caused it... anyway, it will be easier to track when I can discover if the problem lies in

1) The browser caching of the image - is routers2 even run? The web server logs can show this.
2) the lazy mode - ie, is the image recreated by RRDTool? This can be tested by commenting out the '--lazy' line in routers2.
3) the interval calculations - is routers2 passing back the wrong caching information? This is shown in the HTML comment at the bottom of the graph page.

Also, you might want to check your IE settings (if you use IE). There is a 'feature' in IE where it ignores the caching information sent to the browser under some circumstances and caches longer than it should. Try setting the 'Temporary internet files' option settings to 'Check for newer versions every visit to the page' and see if things work again. This is not likely to be the problem but is always a possibility. Firefox is not affected by this problem.

It does sound, though, as if this problem is routers2 related since you say 2.15 works and 2.17 does not.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11