RSV Troubleshooting Guide
About this Document
This document describes how to troubleshoot RSV v3 (part of OSG 3.0).
How to get Help?
To get assistance please use Help Procedure
The developers of a specific metric/probe may provide additional support channel, please check the specific troubleshooting document if your metric is listed in the table below.
RSV has a tool to collect information useful for troubleshooting. For most problems the RSV support team will ask you to generate a profile tarball to share information (including log and configuration files).
You can save some time by doing so with your original request:
$> rsv-control --profile
Running the rsv-profiler...
Making tarball (rsv-profiler.tar.gz)
Debugging errors from specific metrics
The RSV framework runs probes
, programs that perform tests and can measure one or more performances, metrics
Each probe can be developed by different developers. Each metric can fail for different reasons and there may be precise suggestions to fix the specific problem.
The following table will send you to the right page given the metric that you want to check.
Resending failed Gratia records
If RSV fails to send Gratia records, it will save a copy of the output into
. You will be notified if files are in this directory on your HTML status page.
If files appear here, you can attempt to determine why by looking at this log file:
. This file is rotated, so the error message may no longer be present.
Usually this error is spurious - there may have been a problem with the central collector being unavailable, or there may have been a network problem. The first step to fix this problem is to try to resend these files. To do so, move them back into the
directory and they will be resent the next time the gratia-script-consumer runs (about every 5 minutes):
mv /var/spool/rsv/failed-gratia-records/* /var/spool/rsv/gratia-consumer/
If you continue to have problems, please contact the GOC.