Another part of the problem is the timezone as defined in routers2 and as defined in MRTG. They both use different ways to identify the timezone and sometimes they can go out of synch.
To fix the mouseover time, try the following:
1. Make sure that your MRTG server has the correct time. This means the correct Timezone as well, since the offset is important. If it gives the correct time but says GMT then you need to fix it.
2. If you monitored device has an explicit timezone set in the .cfg file, then make sure it is in a format compatible with the local server. This may mean giving it as '+12' or 'GMT+12' rather than 'NZDT' or 'Pacific/Auckland'.
3. Check your workstation is configured for the correct timezone. This should not affect things, but sometimes it can for some odd reason.
4. You may need to explicitly set the timezone offset of your MRTG server from GMT in the routers2.conf. See the commented out line for details, and give the offset in hours from GMT.
If all else fails, you can disable the mouseover time in the routers2.conf if you want to. However this will also disable the popup entirely, including the optional values if you've enabled them.Statistics: Posted by stevesh — Wed Aug 15, 2007 10:33 am
]]>