You'll probably get them since the new apps. We just found a bug in our validator that drops nearly every result done by the new apps. Don't worry about that, should be fixed soon and the results will then be re-validated.
Just for someone to take notice. I downloaded the 4.14 CC this morning - about 10 hours ago.
The one unit from E@H appl. 4.71 code H1_0072.4_00728_0.1_T00_Test 03_5 under analysis was showing at 16:20 (GMT+1) an advance of 35.63% however there is no reading in the CPU time --- nor in the until completion column, there also ---
Due to moving from Climate to Seti and then to Einstein, the E@H unit restarted at 17:50 (GMT+1) but... while still shoeing the 35.66% now advance, in the CPU time column it only shows 1' 35" and on the remaining time it says 00:03:16
Yhis is quite odd, so any suggestions are welcome.
By the way the other two projects are running under CC 4.14 without a problem.
> > This is quite odd, so any suggestions are welcome.
>
> If possible, take a look into stderr.txt in the slots directory where einstein
> is running in. Anything suspicious there?
>
> Please try to exit the client and start it again. Does this problem persist?
>
> BM
>
Bernd in the meantime I'll just wait to see what happens. Yesterday after watchin direct the NASA TV for 4 hours I had some 800million bytes received and my IE started giving me trouble so I disconnected my CPU until this morning.
Unit is still on its 43,48% advance but the times continue to be weird.
As I am not an informatics man, I just do not want to get into that slots directory, much less to know if there is anything suspicious over there :-)
What I have seen is that the download page of E@H does not have the CC 4.14 anymore. Any reason? Shall I go back and reinstall the 4.13 ?
> Apparently 4.14 may have been causing some problems with CPDN. I don't run
> CPDN, and I haven't had any problems with 4.14 yet.
>
Well, I do run CPDN and Seti, the only other ones running now and I have no problems with 4.14
My problem continues to be Einstein unit, when it stops it maintains the % of advance but the times gone to --- both time of CPU and time to completion. When it returns to this unit after two hours (one each for Seti/CPDN) it takes on from the previous percent, but starts counting time again. I will wait to see what happens if it reaches the 100% done, see if it loads and gets ready to be send.
I have been using CC4.14 with S@H on a dual cpu box running linux. So far it appears to be running better than 4.13 did on this box. I didn't add E@H yet to this box because it was a bit unstable rinning S@H and I was trying to eliminate one thing at a time.
Well, now I can inform what has happened to that unit that I was commenting before. It finnally finished, loaded and got ready to report - was reported - and the total time shown is 1/10 of the actual time it was working. It was one of those 8 hrs. units and normally all the previous ones I have had (when processed before) I have been granted credits on the line of 92 to 98 credits, and this time I am showing a credit request of 7 so there must be a bug somewhere in the units, and I say units, because the next one in analysis right now is behaving the same way as the previous one.
In results for user, I have: Success Done 4,320.37 13.17 pending (This is the very last one)
Previous 8 hrs units: Success Done 31,526.81 98.58 98.58 - There is a big difference.
I am using the CC 4.14 have a P4 - 2.66GHz WXP sp1 with 512 KBRAM.
Version 4.14 (released 13 Jan 2005)
)
since boinc 4.14 i get valdiation error on the results
You'll probably get them
)
You'll probably get them since the new apps. We just found a bug in our validator that drops nearly every result done by the new apps. Don't worry about that, should be fixed soon and the results will then be re-validated.
BM
BM
Just for someone to take
)
Just for someone to take notice. I downloaded the 4.14 CC this morning - about 10 hours ago.
The one unit from E@H appl. 4.71 code H1_0072.4_00728_0.1_T00_Test 03_5 under analysis was showing at 16:20 (GMT+1) an advance of 35.63% however there is no reading in the CPU time --- nor in the until completion column, there also ---
Due to moving from Climate to Seti and then to Einstein, the E@H unit restarted at 17:50 (GMT+1) but... while still shoeing the 35.66% now advance, in the CPU time column it only shows 1' 35" and on the remaining time it says 00:03:16
Yhis is quite odd, so any suggestions are welcome.
By the way the other two projects are running under CC 4.14 without a problem.
Patience is a virtue
> Yhis is quite odd, so any
)
> Yhis is quite odd, so any suggestions are welcome.
If possible, take a look into stderr.txt in the slots directory where einstein is running in. Anything suspicious there?
Please try to exit the client and start it again. Does this problem persist?
BM
BM
> > This is quite odd, so any
)
> > This is quite odd, so any suggestions are welcome.
>
> If possible, take a look into stderr.txt in the slots directory where einstein
> is running in. Anything suspicious there?
>
> Please try to exit the client and start it again. Does this problem persist?
>
> BM
>
Bernd in the meantime I'll just wait to see what happens. Yesterday after watchin direct the NASA TV for 4 hours I had some 800million bytes received and my IE started giving me trouble so I disconnected my CPU until this morning.
Unit is still on its 43,48% advance but the times continue to be weird.
As I am not an informatics man, I just do not want to get into that slots directory, much less to know if there is anything suspicious over there :-)
What I have seen is that the download page of E@H does not have the CC 4.14 anymore. Any reason? Shall I go back and reinstall the 4.13 ?
Patience is a virtue
> What I have seen is that
)
> What I have seen is that the download page of E@H does not have the CC 4.14
> anymore. Any reason? Shall I go back and reinstall the 4.13 ?
Apparently 4.14 may have been causing some problems with CPDN. I don't run CPDN, and I haven't had any problems with 4.14 yet.
> Apparently 4.14 may have
)
> Apparently 4.14 may have been causing some problems with CPDN. I don't run
> CPDN, and I haven't had any problems with 4.14 yet.
>
Well, I do run CPDN and Seti, the only other ones running now and I have no problems with 4.14
My problem continues to be Einstein unit, when it stops it maintains the % of advance but the times gone to --- both time of CPU and time to completion. When it returns to this unit after two hours (one each for Seti/CPDN) it takes on from the previous percent, but starts counting time again. I will wait to see what happens if it reaches the 100% done, see if it loads and gets ready to be send.
Patience is a virtue
I have been using CC4.14 with
)
I have been using CC4.14 with S@H on a dual cpu box running linux. So far it appears to be running better than 4.13 did on this box. I didn't add E@H yet to this box because it was a bit unstable rinning S@H and I was trying to eliminate one thing at a time.
Well, now I can inform what
)
Well, now I can inform what has happened to that unit that I was commenting before. It finnally finished, loaded and got ready to report - was reported - and the total time shown is 1/10 of the actual time it was working. It was one of those 8 hrs. units and normally all the previous ones I have had (when processed before) I have been granted credits on the line of 92 to 98 credits, and this time I am showing a credit request of 7 so there must be a bug somewhere in the units, and I say units, because the next one in analysis right now is behaving the same way as the previous one.
In results for user, I have: Success Done 4,320.37 13.17 pending (This is the very last one)
Previous 8 hrs units: Success Done 31,526.81 98.58 98.58 - There is a big difference.
I am using the CC 4.14 have a P4 - 2.66GHz WXP sp1 with 512 KBRAM.
Patience is a virtue
EDIT: THIS MAY NOT BE 4.14
)
EDIT: THIS MAY NOT BE 4.14 RELATED
Did some more digging,
http://einsteinathome.org/workunit/306551
That's one of my hosts running 4.13 and it has the same problem;
High (pending) = 41,511.00 sec, Low (pending) = 3,125.11 sec
---
Some more information on Liberto's report:
From the WU it's easy to see that something odd is going on;
http://einsteinathome.org/workunit/306114
High pending = 51,843.24 sec, Low pending = 4,320.37 sec
same here:
http://einsteinathome.org/workunit/306509
High pending = 20,791.03 sec, Low pending = 945.44 sec
- Marco
Team Canada