You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use 2 different transfer mechanisms in the CODEGEN generation via CMS Connect. The first uses XRootD to the OSG stash service. The second one relies on condor_chirp, which has been supported in CMS.
The XRootD service has undergone major changes in OSG, so it is not working at present. Also, last week, CMS shipped a new implementation of singularity in the Global Pool, which broke condor_chirp, not only for CMS Connect, but also other areas like production.
There will be a hotfix for condor_chirp, but in the meantime, I will be providing a quick workaround to still be able to create gridpacks by using the native condor transfer mechanism instead.
The text was updated successfully, but these errors were encountered:
Hello,
We use 2 different transfer mechanisms in the CODEGEN generation via CMS Connect. The first uses XRootD to the OSG stash service. The second one relies on
condor_chirp
, which has been supported in CMS.The XRootD service has undergone major changes in OSG, so it is not working at present. Also, last week, CMS shipped a new implementation of singularity in the Global Pool, which broke
condor_chirp
, not only for CMS Connect, but also other areas like production.There will be a hotfix for
condor_chirp
, but in the meantime, I will be providing a quick workaround to still be able to create gridpacks by using the native condor transfer mechanism instead.The text was updated successfully, but these errors were encountered: