Heya guys,
Please find this week's ticket summary below, my apologies for being
late with it. Although I intend to send a summary out next week it won't
be until the 12th as Lancaster gives us a generous amount of time off
over Easter (my apologies for next week's meeting too, if there is one).
Cheers all,
Matt
24 tickets today
NGI
https://ggus.eu/ws/ticket_info.php?ticket=80800
Jon Perkin from t2k is having an odd experience approving new members. A
fresh ticket, but one to keep an eye on.
https://ggus.eu/ws/ticket_info.php?ticket=80535
VOMS team ticket from last week. Chris W added a request for Cern@School
access, which Robert Frank reports as having been done. Can we confirm
this & close the ticket (if things work)?
RAL Tier-1
https://ggus.eu/ws/ticket_info.php?ticket=80775
lhcb want the latest (and greatest?) lfc, ticket on hold until RAL can
upgrade.
https://ggus.eu/ws/ticket_info.php?ticket=80668
SNO+ requesting packages at the Tier-1. The real thing of interest is
why they still can't edit their VO card!
GLASGOW
https://ggus.eu/ws/ticket_info.php?ticket=80752
Ops test failures that may have been a Red Herring (we catch a lot of
those) caused by the dashboard not updating. Can it be closed?
DURHAM
https://ggus.eu/ws/ticket_info.php?ticket=80720
Some of Durham's recent problems can be explained by ongoing network
work at the University. would this explain the lhcb failures in
https://ggus.eu/ws/ticket_info.php?ticket=79880?
https://ggus.eu/ws/ticket_info.php?ticket=80407
It looks like the original errors were fleeting, the user reports no
repeats of the problem. I think this ticket can be put to bed.
MANCHESTER
https://ggus.eu/ws/ticket_info.php?ticket=80520
Did removing the problem node from the queue solve the lhcb failures?
From the "Solved Cases" file:
We had two tickets where the VO_ATLAS_SW_DIR was set incorrectly,
whacked by bad kickstarts or overzealous configuration managers. If you
use cvmfs it should be "/cvmfs/atlas.cern.ch/repo/sw". Watch out whilst
you installing your new kit!
https://ggus.eu/ws/ticket_info.php?ticket=80119
Turned out that the problem was most likely caused by differences in
Castor's rfio libraries. SNO+ managed to get a fix themselves by playing
with the "--disable-castor --disable-rfio" flags.
|