Message boards :
News :
CMS -- Please set "no new tasks"
Message board moderation
Author | Message |
---|---|
Send message Joined: 29 Aug 05 Posts: 1060 Credit: 7,737,455 RAC: 1,317 |
Hi to all CMS-ers. We need to drain the job queue so that a new version of the WMAgent can be installed. Can you please set No New Tasks so that your current tasks can run out and no new jobs start? If you have any tasks waiting to run, please suspend or abort them. Thanks, I'll let you know as soon as the change is done. |
Send message Joined: 24 Oct 04 Posts: 1173 Credit: 54,823,214 RAC: 15,936 |
I know there is no answer to this question BUT I sure would like to know how one of my pc's just got 3 CMS tasks here.......considering it didn't have that version d/l'd and none of my pc's have been running CMS here for a long time. I even had to check my pref. settings just to see how it happened and as expected ALL of them are set to only get Theory (and just the last 2 days some Sixtrack) I know the vdi will take hours so I will go abort them before they start. (hardly ever any free time doing this after all these VB years) |
Send message Joined: 29 Aug 05 Posts: 1060 Credit: 7,737,455 RAC: 1,317 |
|
Send message Joined: 15 Jun 08 Posts: 2534 Credit: 253,848,753 RAC: 37,872 |
Looks like CMS has no subtasks. |
Send message Joined: 29 Aug 05 Posts: 1060 Credit: 7,737,455 RAC: 1,317 |
Looks like CMS has no subtasks. Yes, I just noticed that myself -- well, it said 11 which is a lot less than normal. The running-jobs graph took a peak over the last few hours, and the number of failed jobs has fallen away. WMStats looks roughly the same as usual but it's also reporting that two of our agent's modules, JobStatusLite and CouchServer, have errors so maybe it's not reporting properly to Dashboard. I've e-mailed the two people who have the authority to start them up again. [Edit] Well, those two errors have now disappeared so either it fixed itself or our crew was on the ball within minutes. Let's see how it looks after a few hours. [/Edit] [Edit2] Yes, Alan was on hand to start them up again. The CouchDB exception was a new one, hopefully not connected to the Oracle/SQLAlchemy version upgrade that was part of the reason why this thread started in the first place. [/Edit2] |
©2024 CERN