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 13853 times and has 1 reply Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
confused Wingman 0.0 time, 0.0 points claimed, PV status (Resolved)

one of my wingmen, mine is working should be back later today

E200910_ 119_ A.27.C22H15NOS2Si.532.2.set1d06_ 1-- 635 Pending Validation 12/31/10 19:16:06 12/31/10 20:24:14 0.00 0.0 / 0.0

his log:



Result Log

Result Name: E200910_ 119_ A.27.C22H15NOS2Si.532.2.set1d06_ 1--



<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
04:55:24 (1040): No heartbeat from core client for 30 sec - exiting
04:55:25 (1040): No heartbeat from core client for 30 sec - exiting
04:55:26 (1040): No heartbeat from core client for 30 sec - exiting
04:55:27 (1040): No heartbeat from core client for 30 sec - exiting
04:55:28 (1040): No heartbeat from core client for 30 sec - exiting
04:55:29 (1040): No heartbeat from core client for 30 sec - exiting
04:55:30 (1040): No heartbeat from core client for 30 sec - exiting
04:55:35 (1040): No heartbeat from core client for 30 sec - exiting
04:55:36 (1040): No heartbeat from core client for 30 sec - exiting
04:55:37 (1040): No heartbeat from core client for 30 sec - exiting
04:55:38 (1040): No heartbeat from core client for 30 sec - exiting
04:55:39 (1040): No heartbeat from core client for 30 sec - exiting
04:55:40 (1040): No heartbeat from core client for 30 sec - exiting
04:55:41 (1040): No heartbeat from core client for 30 sec - exiting
04:55:42 (1040): No heartbeat from core client for 30 sec - exiting
04:55:43 (1040): No heartbeat from core client for 30 sec - exiting
04:55:44 (1040): No heartbeat from core client for 30 sec - exiting
04:55:46 (1040): No heartbeat from core client for 30 sec - exiting
04:55:47 (1040): No heartbeat from core client for 30 sec - exiting
04:55:48 (1040): No heartbeat from core client for 30 sec - exiting
04:55:49 (1040): No heartbeat from core client for 30 sec - exiting
04:55:50 (1040): No heartbeat from core client for 30 sec - exiting
04:55:51 (1040): No heartbeat from core client for 30 sec - exiting
04:55:52 (1040): No heartbeat from core client for 30 sec - exiting
04:55:53 (1040): No heartbeat from core client for 30 sec - exiting
04:55:54 (1040): No heartbeat from core client for 30 sec - exiting
04:55:55 (1040): No heartbeat from core client for 30 sec - exiting
04:55:57 (1040): No heartbeat from core client for 30 sec - exiting
04:55:58 (1040): No heartbeat from core client for 30 sec - exiting
04:55:59 (1040): No heartbeat from core client for 30 sec - exiting
04:56:00 (1040): No heartbeat from core client for 30 sec - exiting
04:56:01 (1040): No heartbeat from core client for 30 sec - exiting
04:56:02 (1040): No heartbeat from core client for 30 sec - exiting
[04:56:03] Number of jobs = 16
[04:56:03] Starting job 0,CPU time has been restored to 0.000000.
No heartbeat: Exiting
[04:56:21] Number of jobs = 16
[04:56:21] Starting job 0,CPU time has been restored to 0.000000.
Application exited with RC = 0x1
[04:56:23] Finished Job #0
04:56:28 (5932): called boinc_finish
[04:58:26] Number of jobs = 16
[04:58:26] Starting job 1,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #1
[04:58:26] Starting job 2,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #2
[04:58:26] Starting job 3,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #3
[04:58:26] Starting job 4,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #4
[04:58:26] Starting job 5,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #5
[04:58:26] Starting job 6,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #6
[04:58:26] Starting job 7,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #7
[04:58:26] Starting job 8,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #8
[04:58:26] Starting job 9,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #9
[04:58:26] Starting job 10,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #10
[04:58:26] Starting job 11,CPU time has been restored to 0.156001.
[04:58:26] Skipping Job #11
[04:58:26] Starting job 12,CPU time has been restored to 0.156001.
[04:58:27] Skipping Job #12
[04:58:27] Starting job 13,CPU time has been restored to 0.156001.
[04:58:27] Skipping Job #13
[04:58:27] Starting job 14,CPU time has been restored to 0.156001.
[04:58:27] Skipping Job #14
[04:58:27] Starting job 15,CPU time has been restored to 0.156001.
[04:58:28] Skipping Job #15
04:58:34 (2716): called boinc_finish

</stderr_txt>
]]>
----------------------------------------
[Edit 1 times, last edit by Former Member at Jan 3, 2011 7:02:49 AM]
[Jan 2, 2011 6:39:24 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: Wingman 0.0 time, 0.0 points claimed, PV status

Got mine returned, inconclusive, wingman changed to error, repair sent
[Jan 3, 2011 7:02:10 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread