[mrtg] MRTG and web page refresh
s.shipway at auckland.ac.nz
Sat Nov 7 03:17:13 CET 2009
Unless you have the 'paranoia=yes' option set, then if you look at the graph page HTML you will find at the end a comment block detailing the refresh and expiry information set for that frame.
Page refresh should always be set for the graph frame, if not showing and archived graph.
Your problem may instead be due to your web browser - sometimes, IE will cache web pages even when they are set to 'no cache' and can ignore expiry times. Also, if your web browser clock is out of synch with the web server clock you can get this problem.
1. Check your web browser and web server clocks are in synch to the second
2. Check you have 'check for newer versions' set to 'automatically' in your IE cache settings.
From: Patrick Topping [ptopping at pobox.com]
Sent: Saturday, 7 November 2009 9:37 a.m.
To: Steve Shipway
Cc: mrtg at lists.oetiker.ch
Subject: Re: [mrtg] MRTG and web page refresh
We are linking over the page via a 'naked' graph page. I have the
following enabled in the router2.conf file:
# set to +2d if you want all autorefresh pages to work
auth-expire = +2d
# Normally, graphs refresh automatically as soon as they become out of date.
# This is about every 5 mins for daily graphs. You may wish to make the
# minimum refresh time larger to prevent too-frequent updates
# integer in SECONDS, default is 0
minrefreshtime = 300
Am I missing anything here?
Steve Shipway wrote:
> The routers2 autorefresh depends very much on how the page is generated. How are you linking in to Routers2 from the external pages? If it is by using embedded images, or a 'naked' graph page (no header or menu) then the autorefresh is either not possible or is disabled. If you are using the URLs generated by clicking the 'bookmark' button, however, the generated HTML should autorefresh at the appropriate frequency (the refresh code is hidden in the HTTP headers of the graph pane). Otherwise, you'll need to code the HTML to refresh yourself.
> Another thing to note is that your web server must accept the refresh headers from the CGI but that shouldnt be an issue with most web servers.
> From: mrtg-bounces at lists.oetiker.ch [mrtg-bounces at lists.oetiker.ch] On Behalf Of Patrick Topping [ptopping at pobox.com]
> Sent: Friday, 6 November 2009 3:54 p.m.
> To: mrtg at lists.oetiker.ch
> Subject: [mrtg] MRTG and web page refresh
> I am using routers2 as my primary front end to MRTG. I have some other
> apps that use the links inside MRTG to populate web pages for the NOC
> and other departmental views. The issue I am having is these web pages
> are not refreshing themselves automatically. I did not add the Refresh
> option into the cfg files because the default is 300 seconds. I have
> added this option and set the refresh rate to be 300 seconds but no
> change. Anyone have any idea what could be causing the issue? Any help
> would be greatly appreciated.
> Thanks in advance.
> mrtg mailing list
> mrtg at lists.oetiker.ch
More information about the mrtg