The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
•Error Message when Viewing a Report
Apparent Error Message: viewing a report returns with an error message.
Error opening <RRD archive name>.rrd: No such file or directory
MRTG did not create RRD DB files. Verify that your <RTM Folder>/sce_<SCE IP>does not contain *.rrd files.
There are two possible reasons that MRTG did not create the RRD DB files:
1. MRTG execution failed and you should check the following settings are correct:
2. Verify the SCE is accessible, for example ping.
3. Verify the SCE SNMP agent is enabled.
4. Verify the SCE community string is configured correctly in the RTM user configuration file.
5. Verify the RTM directory is configured correctly in the user configuration file. The path cannot contain white space.
Note Use slash or '\\' as the path delimiter.
6. Verify the RRDTool bin directory is configured correctly in the user configuration file.
Note Use slash or '\\' as the path delimiter.
7. Run MRTG from a command prompt and verify that it completes with no errors:
perl <MRTG bin folder>/mrtg<RTM folder>/mrtg-cfg/<SCE address>_scabb_mrtg.cfg
8. Cron did not invoke MRTG
a. Verify Cron is configured correctly—Check the MRTG invocation command for the specific SCE platform is correct.
b. If using PyCron, try running MRTG from PyCron GUI and verify it completes with return code 0
Apparent Error Message: viewing a report returns with an error message The server encountered an internal error or misconfiguration and was unable to complete your request.
This error message appears on Unix/Linux systems if the web server user does not have execution permissions on the SCE platform's report CGI files.
Add execution permissions to all users to all.cgi files.
Apparent Error Message: viewing a report returns with an error message
ERROR: Opening <report image filename>.png' for write: Permission denied.
This error message appears on Unix/Linux systems if the web server user does not have writing permissions on the SCE platform's directory in the RTM directory.
Add write permissions to all users to all SCE directories in the RTM directory.
Apparent Error Message: viewing a report returns with an error message
ERROR: opening <RRD archive name>.rrd': Permission denied.
This error message appears on Unix/Linux systems if the web server user does not have reading permissions on RRD archive files in the SCE platform's directory.
Add read permissions to all users to all RRD archive files. Note that the example crontab.txt file created by the rtmcmd for Unix/Linux systems contains a permissions change command for each monitored SCE. The permissions change command follows the MRTG invocation.
Reports missing data. There is a sheer drop in reported traffic.
Cron has stopped invoking MRTG
1. Verify the *.rrd files in the folder sce_<SCE IP> haven't been modified during the past 5 minutes.
2. Verify Cron is configured as a service and that the service active.
3. Run MRTG from a command line and verify that it completes with no errors.
perl <MRTG bin folder>/mrtg<RTM folder>/mrtg-cfg/<SCE address>_scabb_mrtg.cfg
4. Check that Cron settings are correct.