Cheshire Cat Computing

Hey there

I have installed the 2.1 Bundle and I have the following problem.

I cannot get the Apache to show the homepage of an Interface from any Client PC other than the server were MRTG bundle is installed on.
The files ****.PNG ( Picture files are updating and seems to work as intended )
Anyone have an idea what needs to be done ?

The following things are working as intended.
Perl, seems to work as intended
Cron is reporting
23.04.2008 14:25 c:\mrtg\perl\bin\perl c:/mrtg/mrtg/bin/mrtg --logging=c:/mrtg/mrtg.log c:/mrtg/mrtg/bin/localhost.cfg
The times in this log are updating as expected.

The problem is that the bundle, has not created the index.html and I am running out of Ideas on what needs to be done. I made the "myrouters.txt" with the SNMPstring@routerIP - I did not added any option

If I try perl indexmaker, it allways give my an error Linie 614 in BEP ??

I can give any information needed, but I am lagging out of ideas on what to be done.

I can write a very detalied explanation on how the installation have been made, I will make it upon request.

BRG
Origa

The MRTG bundle uses routers2 and RRDTool, and so you do not get an index.html at all. The indexmaker script is not used as it is no longer required, and MRTG does not generate any image files or html files, only the .rrd database files.

Instead, you get the routers2 interface, which gives a dynamically created menu and creates the graph images on demand only, speeding things up considerably.

With the MRTG bundle, I think you go to http://yourserver:9191/ and it will run the index.cgi page, which is a link to or copy of the routers2.cgi script. This shows you the routers2 menu, which looks something like this:
http://www.steveshipway.org/cgi-bin/routers2.pl

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

Hey Steve

Thanks for clearing up what the bundle does, I think I will upgrade MRTG to the latest build, and see what happens.

The two links you showed, this is excactly what I have here on my screen.

The HTML files, I will make an IIS and do a little of basic HTML with the pictures generated from the RRDTool.

A Big thanks from my part.

BRG
Origa

If you can see the index from the server on which the softeware is installed, but not from other clients on the network, check the following:

1) Are you using the correct URL? Remember 'localhost' means 'this machine'. You will need to give a DNS-resolveable name or IP address for the server when you try to access it remotely.
2) Check for firewalls that might be blocking port 9191
3) Make sure you actually have network connectivity. Can you ping the server?

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

routers2 noly updates the png files when you request the page, which means you cannot link to them directly as you would with native MRTG, they will not update.

Instead, you have 2 different options.

1) Use the routers2.cgi user defined summary page option. This allows you to define a custom summary page (or pages) which can have the subset(s) of interfaces you are interested in. Then, you display these summary pages via routers2 on your screens; this means you do not need to create any custom HTML files at all.
To define a custom summary page, put
routers.cgi*Summary[targetname]: summaryname
for each of the targetnames you want on the summaryname page. You can use this multiple times. Then you can use the 'Bookmark' button to get the URL of the summary page, and append '&page=graph' to get just the central frame.

2) Define your own custom HTML page, with IMG tags to point to the graph images. However, do not give the URLs of the PNG files, but instead use the 'Bookmark' button to get the URL for the graph you are interesting in and append '&page=image' to get just the PNG file. Use this as the URL for the IMG tag, and routers2 will (re)generate the graph image each time it is updated and requested.

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

It is worth mentioning as well that the URL parameter xgtype=d gives the daily graph, and the xgstyle parameter allows you to specify exactly what size graph image you get (otherwise it uses the system default which can be overridden on a per-user basis).

The graph images are correctly cached on the web server disk so they are only regenerated when they are requested and the data has updated; so, for example, the yearly graph images have a 'cache for 1 day' tag, plus the RRD will not regenerate the images if they are less than a day old.

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