Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1346 times and has 3 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
CEP2 PVer status almost 24 hrs after wingman returned

E210483_ 294_ C.32.C27H16N4S.01947906.3.set1d06_ 1-- 640 Pending Validation 11/20/12 11:22:33 11/21/12 04:48:30 6.21
E210483_ 294_ C.32.C27H16N4S.01947906.3.set1d06_ 0-- 640 Pending Verification 11/19/12 02:02:12 11/20/12 11:10:09 12.00


No "Try Validation" option, no other wu sent/waiting to be sent, nothing
----------------------------------------
[Edit 1 times, last edit by Former Member at Nov 21, 2012 10:18:41 PM]
[Nov 21, 2012 10:15:00 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 PVer status almost 24 hrs after wingman returned

48 hrs still same
[Nov 23, 2012 8:56:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 PVer status almost 24 hrs after wingman returned

Latest, when the original deadline passes, either the "try validation" button appears or the validation is pushed by token of the event that checks if an additional copy is needed. It's a bug for which there never was found the cause. Running a script to check the validation queue flagging too costly in load addition to run one on top, so the Try Validation was created, which itself occasionally does not appear.

It's that [funny] article I saw and cross posted in the quota thread [from the mother of all projects] claiming that user systems were too fast these days for the servers to be able to keep up at the transactional volume processed, and thus requiring the quadruple size up of tasks and here at WCG getting fire and flame when 20-40-90% ** is added to a task to prevent collapse of the scheduler. Suggest to be patient. The validators will get to them eventually.

Edit: ** Noting that this size-up was reversed after the cause of the server slow-downs was uncovered and fixes implemented [the over-sized directory structure and core memory size were a few of them]!
----------------------------------------
[Edit 1 times, last edit by Former Member at Nov 23, 2012 9:34:09 AM]
[Nov 23, 2012 9:30:18 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 PVer status almost 24 hrs after wingman returned

72 hrs no change, goes no reply in 9
[Nov 24, 2012 8:36:42 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread