LHC@home

My fault, more news soonest. Eric.

---

Thanks for the feedback. I messed up. Will fix soonest. Eric.

---

Sadly this is NOT happening. Will fix soonest. Eric.

---

You should quote the post you're answering to ;)

No you are NOT on the list appended. There is a bit of a problem as I was
over-enthusiastic. Eric.

10405110
10452223
10454365
10480022
10482829
10484503
10484659
10484663
10484752
10485156
10485905
10485906
10485908
10485911
10485912
10485913
10486162

---

You should quote the post you're answering to ;)

Thanks I am not too good at the MBs. Sorry will do so in future.
Eric.

---

Sadly my fix has created too many inconclusive results.

I have doubts that there are special hosts or special OSs causing the high rate of inconclusive results.

Why? Because the rate of inconclusive results is >99.9 % as far as I can see.

My current sixtrack stats:
all (9502)
in progress (755)
validation pending (1708)
validation inconclusive (4527)
valid (1256) --- only 3 after the validator changed, see below
invalid (1)
error (1255)

Comments:

Before the validator change, I think I had only a handful inconclusive results. Browsing through my >4500 current inconclusives, they seem to be all from after the validator change.

The single invalid one is WU 69714861: 2x cancelled + 3x finished but with different results according to the validator (completed on June 3, June 10, and June 25, i.e. 2x with old validator and 1x with new validator). Therefore this invalid task really is more like inconclusive, because there were two guys who cancelled, and it remains unknown which of the three submitted results was the right one.

The errors are some user-aborted tasks, but typically "finish file present too long" errors.

Of the valid tasks, only 3 (three) have been validated by the new validator. All others had been validated before the new validator was brought online.

(BTW, all of my boxes are Xeon E5 and Xeon E3, all but one with ECC RAM, and they had earned my trust in their results before. Some of them are purpose-built compute nodes for engineering applications, doing Distributed Computing in downtimes. --- Edit: These are Linux boxes, except one Windows box which shows exactly the same picture as the Linux boxes.)

---

Rien a faire.Ma faute.

bonjour, j'ai ce soucis apparemment.
...
que dois-je faire ?

Pour résumer les messages du modérateur :
- Suite à des machines renvoyant systématiquement et massivement des résultats faux (des linux) il y a une grande file d'attente en validation peu concluante
- Patientez. Vos unités de travail seront renvoyées à d'autres machines pour recalcul et validation.
- L'attente peut être longue car ces unités sont en bas de la file d'envoi du serveur.

summarized trans : wait for a resend to another host of the WU / see msg 31064 and 31074

---

Rien a faire, ma faute. Eric.

bonjour, j'ai ce soucis apparemment.



que dois-je faire ?

---

oops

HIGHLY IMPORTANT
It looks as if my attempted fix is creating too many problems, MEA CULPA.
I expect we shall shortly withdraw it and return to the previous version of
the sixtrack_validator. Sorry for the hassle and I shall try and answer as many
of your posts to this thread as possible. The side effect seems to be I/we are
now NOT validating when we should, certainly my fault.

We shall return to a state where we will validate invalid empty results, but in this
case the attempted Cure is Worse than the Disease. ( I tried.)

Hope to try again soon. Eric.

Hi Eric,
Appreciate all your efforts in trying to solve this. I'm a bit of a layman sorry when it comes to the technical talk regarding all this...should I stop crunching sixtrack work?
I have 175 invalid WU's. Will I eventually get the credit or am I wasting time, power etc when I could crunch another project until resolved?

I only crunch 6track btw. No VB.

Kind regards
Andrew

---

Appreciate all your efforts in trying to solve this. I'm a bit of a layman sorry when it comes to the technical talk regarding all this...should I stop crunching sixtrack work?
I have 175 invalid WU's. Will I eventually get the credit or am I wasting time, power etc when I could crunch another project until resolved?

You don't have any invalids tasks, only valid ones and those that are currently inconclusive. Admins can easily trigger revalidation of all tasks as soon as they have the old validator in place.

I am sure you will get credits but a bit patience is needed for the moment.

I concour, my invalid rate has jumped from 8.8% to 51.3%.

Before I was paired with a few rouge host now it would seem random.

Maybe you just need to boot the servers... what size shoe do you wear? :)

(Hey, it worked for Chief O'Brien on DS9... maybe the Cardissans were running Windows...)

---

Computer 10388131 shown also a lot of unresolved tasks.

Is it possible to find those Computer with the duration-time of the tasks in the detail list of the Computer,
when this is lower than maybe 0.1 day?

Appreciate all your efforts in trying to solve this. I'm a bit of a layman sorry when it comes to the technical talk regarding all this...should I stop crunching sixtrack work?
I have 175 invalid WU's. Will I eventually get the credit or am I wasting time, power etc when I could crunch another project until resolved?

You don't have any invalids tasks, only valid ones and those that are currently inconclusive. Admins can easily trigger revalidation of all tasks as soon as they have the old validator in place.

I am sure you will get credits but a bit patience is needed for the moment.

Hi Juha,

Thanks for the clarification. I think you misunderstood me though. I have plenty of patience but the WU's on my old Q9550 are taking around 12 hrs to complete. That would have been a lot of wasted time if it was all for nought.

I crunch more than just LHC ;)

---

We have updated the tasks that were got the validation set to "inconclusive" in the database and set them to be validated again. It will take some time for the validator to chew through the backlog, so please be patient with this.

The bottom line is that we do not want you to loose any credit, as we really appreciate your efforts crunching for LHC@home. Thanks again for your contributions!

<< EDIT >>
Original post written while your message about revalidation inconclusives. Looking forward to seeing how that will end. In the meantime, here is my original information...

<< END EDIT >>
=====
My current list show 5 valid results, 12 inconclusive and 9 in process, a single pending validation, no invalid or errors. These numbers only cover those that are not purged from the database, so relative comparison over my whole LHC career is not possible.

I hope this information can be useful in narrowing down some of the problems.

The few times I have checked my result list under the current system, I have also not observed any invalid or errored tasks. Neither did I have errored or invalid tasks under the old system when LHC was split in two separate projects.

If the current system could keep a running total of all tasks for each host (and keep those numbers after work units and tasks get deleted from database), we would have probably a much better basis for seeing which hosts have problems with their results?


Now, back to my current list of inconclusive and pending results...


Host ID; 10236061 (Intel Core2 Duo E8500 @ 3.16GHz, not overclocked)
4 GB RAM (2x Corsair CM2X2048-6400C4PRO, not overclocked)
Motherboard: ASUSTeK Maximus Formula II
Windows 10 Pro x64, version 1607 (build 14393.1358)


Common to all listed below is that all results from the other participants were short runs, also ending with inconclusive result.

All work units have also listed a third task that is ready to send. Given the inconclusive status of all tasks in those work units, I doubt the third one will succeed, but there's always hope.. :-)

I hope this situation with inconclusive and bad results will come to and end. Nothing hurts a project more than hundreds or thousands of bad or potentially bad results that need to be manually checked... I wish all the best of luck finding a solution to this!

-----

My inconclusive results with short run times:
WU 71637755, task 148057184
WU 71637757, task 148057188
WU 71637758, task 148057190
WU 70954146, task 146755417
WU 70746028, task 146334441
WU 70605235, task 146049158
WU 70605236, task 146049159


My inconclusive results with long run times:
WU 70894751, task 146635362
WU 70894759, task 146635378
WU 70746026, task 146334437
WU 70541544, task 145918243
WU 70502221, task 145842412


Pending validation:
WU 70928940, task 146704351
In this case, my partner's task timed out with no response.

Common to all listed below is that all results from the other participants were short runs,

My >4500 inconclusives were across the board with runtimes.

I suspect the fact that yours (or your wingmen's) were all short was probably mere coincidence, and a likely coincidence anyway because the SixTrack project generates so many of those. :-(

I have many inconclusive results on this host:
https://lhcathome.cern.ch/lhcathome/results.php?hostid=10478836