Message boards : CMS Application : Upcoming disruptions to CERN infrastructure
Message board moderation
Author | Message |
---|---|
![]() ![]() Send message Joined: 20 Jan 15 Posts: 1141 Credit: 8,310,612 RAC: 0 ![]() |
For some reason I could'nt post this to the CMS@Home message board: There seems to be a problem at CERN. Several WMAgents, including ours, are showing error status and I don't think we are generating jobs. A polite e-mail has been sent. Further communication from WMCore: it looks like we might have disruptions for a little while yet (vocms0267 is our current WMAgent node). 😢 We have recently migrated CERN nodes to Alma9, as a result of the WMAgent containerization effort. With that said, we would like to upgrade vocms0267 as well. We already have another node in Alma9, named vocms267, but I believe we will have to change its condor setup. Once we have the new node (vocms267) properly configured, we would like to upgrade the agent as well and start adopting the docker container solution for CMS@Home project as well. There is work in progress with the cmsweb(-testbed) frontends, and depending on how that investigation goes, it might be that we will have to make a speedy transition, as apparently CouchDB replication does not work with the new frontends replacing Apache. ![]() |
![]() ![]() Send message Joined: 8 Apr 15 Posts: 797 Credit: 14,007,534 RAC: 8,976 ![]() ![]() ![]() |
Thank You Sir |
![]() ![]() Send message Joined: 8 Apr 15 Posts: 797 Credit: 14,007,534 RAC: 8,976 ![]() ![]() ![]() |
For some reason I couldn't post this to the CMS@Home message board: This reminds me of when that started happening to Eric McIntosh and he would email me with his posts so I could post them for him over at production. I hope this doesn't mean you and I are so old we get from semi-retired to forced retired......but then you still have Brunel University ![]() |
![]() ![]() Send message Joined: 20 Jan 15 Posts: 1141 Credit: 8,310,612 RAC: 0 ![]() |
We need to upgrade the WMAgent, but we can't wait for the current workflow to finish. So, we will force-stop the workflow tomorrow (Thursday 08/05). Please set your machines to "No new tasks" to give current tasks a chance to finish before the stoppage. ![]() |
![]() ![]() Send message Joined: 20 Jan 15 Posts: 1141 Credit: 8,310,612 RAC: 0 ![]() |
Intervention is over and I've submitted a new batch of jobs. They should be available soon. ![]() |
©2025 CERN