...
Using the results from the Tulip log analysis script we can identify the hosts and their success percentages. We opted to disable all the hosts which were having success less than 20%, and to enable the ones with success rate greater than 20%. The above mentioned script is in /afs/slac.stanford.edu/package/pinger/tulip and it performs the listed functions. It uses the LWP package to access the webpage, downloads the analyzed tulip log file, saves it in a file and then parses the output to get: for option ability=1, the faulty (landmarks (i.e. the ones below 20% success rate by default) updating the database to disable such hosts; or option ability=0 the landmarks with a success rate greater than 20% and re-enables them in the database. It (tulip-tuning.pl) is run twice nightly (see the trscrontab) once to disable non working landmarks, once to enable landmarks that are now working again. The runs are before the sites.xml or sites-disabled.xml are created and specify using the tulip log file analyzed for the last 3 days.
The output generated by tulip-tuning.pl is placed at /afs/slac.stanford.edu/package/pinger/tulip/tuning_log. This log file, contains blocks of logs for each run. Each block starts with a unix time stamp, indicating, when tulip-tuning.pl ran, separated by hyphones
and ends with a series of hypons.
The log file, will go on increasing, unless it is rotated, from time to time.