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: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1606 times and has 1 reply Next Thread
Falconet
Master Cruncher
Portugal
Joined: Mar 9, 2009
Post Count: 3315
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
problem...

Hi all!

I have a problem with HCMD2.I went to the result status page to see the status of wu's and saw that an HCMD2 that ran yesterday said 6 hours of runtime.And in the result log it says:

Result Log


Result Name: CMD2_ 0217-2AR7_ B.clustersOccur-2QQ2_ A.clustersOccur_ 0_ 1--



<core_client_version>6.2.28</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
INFO: No state to restore. Start from the beginning.
Finishing early because max runtime has been exceeded.21603.015000
called boinc_finish

</stderr_txt>
]]>

However I remember that it ran for 5 hours and 30 something minutes.It went to 100%.It was over 60% when it got to the 6 hours(of course) and it took less than 12 hours.And I have boinc 6.2.28 wich shows CPU time.
It is the second time this happends in this computer.

Ideas?
----------------------------------------


- AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W
- AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W
- AMD Ryzen 7 7730U 8C/16T 3.0 GHz
----------------------------------------
[Edit 1 times, last edit by Falconet at Dec 20, 2009 5:57:51 PM]
[Dec 20, 2009 5:55:12 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: problem...

What's the in the problem? WCG servers out, burning, snowed under, no work for no one available?

Seriously, whatever you saw and think to remember, the log says the standard 21603 seconds cutoff.. 6 hours. A tool like BoincTasks would log the actual CPU and wallclock time to confirm what you observed.

Sometimes when a job goes gunky, it restarts from the point it was and only seems to recognize the remainder of the time, seeds in RICE e.g. , so with those 2 entries "No State to Restore" your job, my guess, only recorded the last 6 hours. Sometimes it fails to resume after a disturbance from the last checkpoint i.e reverts to start. Your client message log could have an entry. See the stadoutdae.txt file in the BOINC data_dir [open with notepad e.g.]

What's the wingman saying?
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 2 times, last edit by Sekerob at Dec 20, 2009 6:39:01 PM]
[Dec 20, 2009 6:12:09 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread