Last night, the reverse proxy proxy-vip.cms stopped responding for 17 minutes. During this time, the DAQAggregator was delayed as it timed out accessing http://cmsdaqfff/prod/sc/php/cpuusage.php?setup=cdaq&intlen=30&int=1 (c.f. http://cmsonline.cern.ch/cms-elog/1072828). I would suggest to use the direct address at pt.5 (i.e. http://es-cdaq.cms/sc/php/cpuusage.php?setup=cdaq&intlen=30&int=1) to avoid issues like this in the future.
Last night, the reverse proxy proxy-vip.cms stopped responding for 17 minutes. During this time, the DAQAggregator was delayed as it timed out accessing http://cmsdaqfff/prod/sc/php/cpuusage.php?setup=cdaq&intlen=30&int=1 (c.f. http://cmsonline.cern.ch/cms-elog/1072828).
I would suggest to use the direct address at pt.5 (i.e. http://es-cdaq.cms/sc/php/cpuusage.php?setup=cdaq&intlen=30&int=1) to avoid issues like this in the future.