Difference: ATLASADCoSShiftDiary (3 vs. 4)

Revision 42009-11-11 - ChrisCollins

Line: 1 to 1

META TOPICPARENT	name="WebHome"

ADCoS shift summary

Changed:

<
< Report from Alistair. 27/10/2009:

>
> Report from Alistair. 27/10/2009. Modified by ChrisCT on 11/11/2009:

See at the bottom of the page for general conclusions.

Line: 16 to 16

You should then know who your senior shifter and expert shifter are for the same date and time as your shift.

Changed:

<
< So, starting your shift: First, open the ADCoS TWiki, and go to the Checklist for things to do. Out of the list of links they ask you to open in your browser, I only really looked at the Production Dashboard, Production (PANDA), the DDM Dashboard and the ADC eLog. As the checklist says, switch to the cloud view on the Dashboards. Note that of those four, all refresh automatically apart from the ADC eLog. However, every time a new eLog entry is created, you'll get an e-mail, so there's not much to worry about there.

>
>

So, starting your shift: First, open the ADCoS TWiki

, and go to the Checklist

for things to do. Out of the list of links they ask you to open in your browser, I only really looked at the Production Dashboard

, Production (PANDA)

, the DDM Dashboard

and the ADC eLog

. As the checklist says, switch to the cloud view on the Dashboards. Note that of those four, all refresh automatically (with LARGE delays and possible problems!-see later) apart from the ADC eLog. However, every time a new eLog entry is created, you'll get an e-mail, so there's not much to worry about there.

ChrisCT got a reply from Graeme: apparently the dashboards do not really update very well at all- be careful! - If you go in to the cloud view and get a url like
http://dashb-atlas-prodsys.cern.ch/dashboard/request.py/overview?grouping=cloud&start-date=2009-11-11%2000:00:00&end-date=2009-11-11%2012:59:59&grouping=cloud
as opposed to:
http://dashb-atlas-prodsys.cern.ch/dashboard/request.py/overview?grouping=cloud
then you have a 'frozen' url which will NEVER update!

On the Panda monitor, look out for 'Waiting' jobs. These might come from jobs not able to get their input (e.g. AOD). you can tell this by

clicking on the waiting jobs
click on a panda job id
see the parent input dataset: your aim is to find failed jobs or problems
To find failed jobs, you can click on the TaskID of the input parent Dataset, and then there is a link to failed jobs.

In the ADC monitoring window https://sls.cern.ch/sls/service.php?id=ADC_CS if all is not green, the expert (Graeme) should be notified.

Then sign into the ADC Control Room (if at CERN, refer here for ways to set up your Skype)

Line: 24 to 38

Chris CT had problems - the instant messages were not being delivered so I emailed my senior shifter. After I added him as a contact, everything worked fine. Weird.

First thing you should probably do is read the previous eLog and shift summary.

Added:

>
>

Also have a look at the sheduled downtime for sites here: https://atlas-install.roma1.infn.it/atlas_install/list.php?sitename=AGLT2

or here:https://twiki.cern.ch/twiki///bin/view/Atlas/AtlasGridDowntime

. If you do raise GGUS tickets, check downtime. GGUS tickets are mainly for SITE problems. Other things (like datasets not being found because they weren't made properly) don't need GGUS tickets.

Raise GGUS tickets as "TEAM". This is important and easy to forget. You have to click the link at the top of the page to get TEAM tickets (as opposed to GGUS tickets!).
In your GGUS ticket, cc the list: "atlas-project-adc-operations-shiftsNOSPAMcern.ch"

Also, you will need to be able to edit eLogs; there is a simple (instantaneous!) registration process when you try to edit one.

Everyone seems friendly, and will try to answer any questions - I spotted a couple of things and mentioned them during my time on shift, and invariably the expert had already seen them, but was happy to explain that he'd already dealt with it, or why it wasn't important.

View topic | History: r26 < r25 < r24 < r23 | More topic actions...