August 2021 - Gridpp-Dirac-Users

Sandbox retrieval
by Daniela Bauer 23 Aug '21

23 Aug '21

******************* This email originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address. ******************* Dear All, For people who are members of multiple groups or VOs: Please ensure that you use the same group/VO to manage your jobs that you used to submit the jobs. Up until now you were able to e.g. get your Sandbox submitted from a different group (e.g user/prod) back without switching between groups, this is no longer possible. Regards, Daniela -- Sent from my guinea pig enhanced living room ----------------------------------------------------------- daniela.bauer(a)imperial.ac.uk HEP Group/Physics Dep Imperial College London, SW7 2BW Tel: Working from home, please use email. http://www.hep.ph.ic.ac.uk/~dbauer/

1 0

Singularity container issue on `CLOUD.UKI-LT2-IC-HEP-lz.uk`
by Andrew S Naylor 06 Aug '21

06 Aug '21

******************* This email originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address. ******************* Hi, I'm running a local singularity image in a dirac job, this job runs fine on `LCG.UKI-LT2-IC-HEP.uk` but when on `CLOUD.UKI-LT2-IC-HEP-lz.uk` I get a container creation failed: Error message: ``` INFO: Converting SIF file to temporary sandbox... FATAL: while extracting hyper_lite__0_1.sif: root filesystem extraction failed: extract command failed: FATAL: container creation failed: multiple devpts instances unsupported and /dev/pts configured : exit status 255 ``` This is my singularity command (mounting current working directory, x509 proxy location and cvmfs): ``` $SINGULARITY_BIN run --contain --env X509_USER_PROXY=${X509_USER_PROXY} \ -B $PWD -B $X509_USER_PROXY -B /cvmfs \ $LOCAL_IMAGE /bin/sh -l $JOB_SCRIPT ``` Also by default i'm using `/cvmfs/ oasis.opensciencegrid.org/mis/singularity/current/bin/singularity` for the singularity binary, unless user namespaces aren't enabled on that system and then it uses the local singularity instead. I wonder if the issue is with something i'm mounting or is it something else? Thanks, Andrew -- ____________________________ *Andrew Naylor* Astroparticle Physics PhD Student Department of Physics and Astronomy The University of Sheffield *Office*:E18a, Hicks Building, Hounsfield Road, Sheffield S3 7RH, UK *Email*:andrew.naylor@sheffield.ac.uk

2 1

How to update "application status" in dirac job monitor?
by Anna Scaife 04 Aug '21

04 Aug '21

Hello I was wondering I there is a way for a general user (i.e. me) to dynamically change what is displayed under “Application status” in the Job monitor when an application is running? At the moment it just says “Unknown” for my applications and I was wondering if I could change it to be a bit more informative since the applications can be quite long and the StdOut peek doesn’t always make it obvious how far things have got. Is there something I can add to the run script to update that field? Cheers Anna

2 1