Hello!
With no Ops meeting tomorrow due to the clash with the WLCG meeting I'll
just skim the tickets this week. Full review next week!
Although with 50 Open UK Tickets that's a lot of skimming!
org.bdii.GLUE2-Validate tickets
We have 8 sites with these tickets (7 as Bristol have slain theirs),
these are being discussed on TB-SUPPORT. A lot of these are still just
assigned though - even if the issue is not really our fault we still
need to handle the ticket proper. Rising above it all and all that.
If someone has submitted or knows of a counter-ticket for this issue
please let me know.
NGI
Talking about a pain in the Information System, the UK still has this
ticket to close (which has a similar root problem):
https://ggus.eu/?mode=ticket_info&ticket_id=118930
CMS Siteconf problems.
GLASGOW https://ggus.eu/?mode=ticket_info&ticket_id=119196
EDINBURGH https://ggus.eu/?mode=ticket_info&ticket_id=119195
OXFORD https://ggus.eu/?mode=ticket_info&ticket_id=119197
CMS have spotted a number of misconfigured T3s across the globe (on a
Friday afternoon)- the fix seems to be straightforward enough and
Glasgow look like they're done already. Proper job!
ATLAS CONSISTENCY CHECKS
We still have 8 tickets open on this issue, although a couple are
waiting for feedback from atlas. I'll bring this up in the Thursday UK
atlas meeting to see if we can't shimmy along the tickets waiting for
atlas feedback.
PILOTS
https://ggus.eu/?mode=ticket_info&ticket_id=117723
Whilst investigating pilot issues at QM Daniela reminds us of this page
that tells us what Dirac things should be going on at your site. Might
be handy to preempt problems:
http://www.hep.ph.ic.ac.uk/~dbauer/dirac/site_pilot_status.html
https://ggus.eu/?mode=ticket_info&ticket_id=118628
Whilst rolling out similar changes for LZ at RALPP Chris stumbled upon a
problem, for which he submitted a bug report to nordugrid:
http://bugzilla.nordugrid.org/show_bug.cgi?id=3529
AND FINALLY
QMUL
https://ggus.eu/?mode=ticket_info&ticket_id=118985 (21/1)
Biomed have got back to Dan suggesting that rather then ban them
altogether until he has a cgroup-corral to put their jobs in if he would
be willing and able to supply a list of the problem users. Of course
this requires that there be any non-problem users in the VO... On hold (1/2)
That's all folks, let me know if I missed anything!
Matt
|