Difference: UCSDPhedexMonitoring (4 vs. 5)

Revision 52008/07/26 - Main.JamesLetts

Line: 1 to 1
 
META TOPICPARENT name="UCSDPhedex"

PhEDEx Monitoring

Line: 12 to 11
 
    • If there are no errors: SRM, dCache, Network are all probably healthy.
    • If there are errors, click on the number of errors in the table and see the details ... the error logs are sometimes very cryptic!
      • If the errors are on all links, we are probably the source of the problem.
Changed:
<
<
      • If the errors are on a particular link, then the source site or the network is most likely the culprit. Check the source sites other transfers.
>
>
      • If the errors are on a particular link, then the source site or the network is most likely the culprit. Check the source sites other transfers by replacing "UCSD" with the source site name (i.e. FNAL, CERN) in the "From" and "To" fields.
 
Added:
>
>
There may not be any production instance transfers if there is nothing subscribed to us. The first link shows the last hour of Prod transfers, and the second link shows whats in our transfer pipeline.
 
Deleted:
<
<
 
Added:
>
>

PhEDEx Agents

PhEDEx operates by running a set of "agents" on phedex-1.t2.ucsd.edu. These agents are responsible for file downloads, exports, deletion requests, etc. Agents that die are automatically restarted by a cron job every hour. However, agents can lose their connection to the central databases at CERN and appear to be down even if they are still running locally. To see the health of various data transfer links from the T1 sites to UCSD, follow the links below. They should ALL be green. If not an agent might be down either at UCSD or at the source T1. Click on the box to see the problem.

 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback