Area 51 的帖子

101) 留言板 : Number crunching : Are the servers down again? Not getting any new WU. (消息 1055347)
发表于:12 Dec 2010 作者: Profile Area 51
Post:
After finally getting my new system rebuilt tonight I am now no longer able to download any new CPU or GPU WU. I just waned to make sure it was not just me and some other mistake I had made.

Is there something wrong with the servers tonight in that they are not handling out new WU?


Thanks,

Adam




Yes there is/are a problem(s). No further information at this point in time though, other than you can upload/report completed work - if you can get any to process.
102) 留言板 : Number crunching : New server problems (Dec 11) ? (消息 1055333)
发表于:12 Dec 2010 作者: Profile Area 51
Post:
Then there's host 5293938, that was running the Fermi incompatible V12 Cuda app on Fermi GTX 480's in June, and still is almost six months later,

That owner at least has a posting history, and a profile. Having seen it, I'm not going to argue with him.


LMAO - "whatever you're doing its fine, no honest"!!!!!
103) 留言板 : Number crunching : Lunatics 0.37 issue (消息 1055329)
发表于:12 Dec 2010 作者: Profile Area 51
Post:

COuld it be that he's got too much work onboard? Didn't someone else have this problem before on the boards. Could just clicking on "show active tasks" prevent this from happening



1200 tasks total was my maximum. The issue surfaced before I hit that number.
104) 留言板 : Number crunching : Lunatics 0.37 issue (消息 1055328)
发表于:12 Dec 2010 作者: Profile Area 51
Post:
What I'm seeing for tasks reported by 5549084 at 11 Dec 2010 13:19:00 UTC and earlier is the expected "No heartbeat from core client for 30 sec - exiting". As usual, the cause is not apparent.

The change between 0.36 and 0.37 was primarily switching from Raistmer's V12 CUDA apps to Jason's x32f. The CPU applications are no different. A possible pattern to the intermittent failure to communicate heartbeats may be that it happens shortly after a new x32f task starts. The stderr info doesn't time-tag the heartbeat failures, so that's uncertain, but message logs could be searched to see if that guess is correct.

The BOINC API code used for Raistmer's V12 is likely earlier than that for Jason's x32f, and the affected host is running BOINC 6.10.56. I doubt that's significant, but if anyone else is running x32f successfully with BOINC 6.10.56 please say so.

That's all the available data suggests to me, but I'll ponder some more.
                                                                Joe



I have a copy of the entire BOINC sub-directory just before I rolled back to 0.36 - if there is likely to be anything of use in trouble shooting the problem, I'll be happy to do what I can.

<edit>Had a rummage around the slots directory, and here is the stderr.txt file for one of the tasks that was running - on and off - before I switched back to 0.37:


Windows optimized S@H Enhanced application by Alex Kan
Version info: SSE3x (AMD/Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSE3x Win32 Build 76 , Ported by : Jason G, Raistmer, JDWhale

CPUID: AMD Phenom(tm) II X6 1090T Processor
Speed: 1 x 3199 MHz
Cache: L1=64K L2=512K
Features: MMX SSE SSE2 SSE3

Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 0.421312
No heartbeat from core client for 30 sec - exiting
Windows optimized S@H Enhanced application by Alex Kan
Version info: SSE3x (AMD/Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSE3x Win32 Build 76 , Ported by : Jason G, Raistmer, JDWhale

CPUID: AMD Phenom(tm) II X6 1090T Processor
Speed: 1 x 3200 MHz
Cache: L1=64K L2=512K
Features: MMX SSE SSE2 SSE3

Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 0.421312
No heartbeat from core client for 30 sec - exiting
Windows optimized S@H Enhanced application by Alex Kan
Version info: SSE3x (AMD/Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSE3x Win32 Build 76 , Ported by : Jason G, Raistmer, JDWhale

CPUID: AMD Phenom(tm) II X6 1090T Processor
Speed: 1 x 3198 MHz
Cache: L1=64K L2=512K
Features: MMX SSE SSE2 SSE3

Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 0.421312
No heartbeat from core client for 30 sec - exiting
Windows optimized S@H Enhanced application by Alex Kan
Version info: SSE3x (AMD/Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSE3x Win32 Build 76 , Ported by : Jason G, Raistmer, JDWhale

CPUID: AMD Phenom(tm) II X6 1090T Processor
Speed: 1 x 3198 MHz
Cache: L1=64K L2=512K
Features: MMX SSE SSE2 SSE3

Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 0.421312
No heartbeat from core client for 30 sec - exiting
Restarted at 4.92 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 4.92 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 10.38 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 10.38 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 16.58 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 16.58 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 16.58 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 16.58 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 22.75 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 22.75 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 29.73 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 29.73 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 35.46 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 35.46 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 41.18 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 41.18 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 41.18 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 48.24 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 55.67 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 55.67 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 55.67 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 55.67 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 55.67 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 64.26 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 64.26 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 72.26 percent.
No heartbeat from core client for 30 sec - exiting
Restarted at 72.26 percent.
</edit>

<edit2> And here are the corresponding entries from stdoutdae.txt for that task (edited to remove the lines about re-setting the project):

11-Dec-2010 10:24:19 [SETI@home] Starting 13ja10ab.18716.15609.7.10.167_1
11-Dec-2010 10:24:20 [SETI@home] Starting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 10:31:37 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 10:31:41 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 10:34:44 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 10:34:49 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 10:35:55 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 10:35:55 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 10:50:59 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 10:50:59 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 10:51:54 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 10:51:54 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:04:02 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:04:02 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:04:49 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:04:49 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:17:20 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:17:20 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:18:02 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:18:02 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:23:27 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:23:27 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:30:37 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:30:39 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:42:45 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:42:45 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:43:35 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:43:35 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:55:24 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:55:25 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 11:56:13 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 11:56:13 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:08:05 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:08:05 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:09:06 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:09:06 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:21:22 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:21:22 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:22:05 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:22:05 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:26:14 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:26:15 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:39:08 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:39:08 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:51:31 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:51:31 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:52:20 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:52:20 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:53:47 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:53:47 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 12:55:23 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 12:55:23 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 13:02:34 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 13:02:34 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 13:14:36 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 13:14:36 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 13:15:25 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 13:15:25 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 13:26:53 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 13:26:54 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603
11-Dec-2010 13:27:46 [SETI@home] Task 13ja10ab.18716.15609.7.10.167_1 exited with zero status but no 'finished' file
11-Dec-2010 13:27:46 [SETI@home] Restarting task 13ja10ab.18716.15609.7.10.167_1 using setiathome_enhanced version 603

</edit2>
105) 留言板 : Number crunching : Lunatics 0.37 issue (消息 1055103)
发表于:11 Dec 2010 作者: Profile Area 51
Post:
I was getting tasks re-starting, at random times during processing.

How random were those times? The restarting can be triggered by adjusting the system clock in the "wrong" direction. Since I have my clock set to be synchronised via Internet every twelve hours, I see those restarts quite regularly (depending on the games I play:-).

Gruß,
Gundolf



Well, just checked and I'm set to 'time synch' once a week. No dice there!
106) 留言板 : Number crunching : Lunatics 0.37 issue (消息 1055101)
发表于:11 Dec 2010 作者: Profile Area 51
Post:

How random were those times? The restarting can be triggered by adjusting the system clock in the "wrong" direction. Since I have my clock set to be synchronised via Internet every twelve hours, I see those restarts quite regularly (depending on the games I play:-).


Very random!
Sometimes, I would get 3-4 minutes processing done - other times 18 or so minutes. There really was no obvious pattern.


What are you using for an antivvirus? Has it changed lately?

AVG. The only thing that has changed are the virus definitions.



I have the same CPU and used the same installer without a problem.
I dont think its the installer though.

Useful - thanks. At least I know there is a possibility I can get it to run. I think I'll see about the time-synching and see if I get anywhere with that idea.
107) 留言板 : Number crunching : Lunatics 0.37 issue (消息 1055078)
发表于:11 Dec 2010 作者: Profile Area 51
Post:
I seem to have run into a compatibility issue with the 0.37 installer/binaries.

During 'the great outage', I upgraded my CPU from a 955 to a 1090, and thought I might as well upgrade to the latest and greatest lunatics app.

When the project came back up, my client started asking for, and getting work. Everything looked good - all 9 cylinders firing fine (6CPU+3GPU). Then I looked at the messages my client was pumping out. I was getting tasks re-starting, at random times during processing. All processing tasks would re-start together (not from zero), at the same time - not just a couple. The re-starts were accompanied by the :

......exited with zero status but no 'finished' file

message.

After digging back through previous occurrences of this message via Google, I checked through all my 'green' settings both at BIOS level and OS level. Nothing was set to go to sleep - ever. I tried various combinations of ncpu values in the app_info.xml file, and adjusting the write to disk interval. I made sure anti-virus scans weren't touching the BOINC directory at all, or that any file indexing was going on there either. Nothing fixed it.

I then re-installed the Lunatics app using the 0.36 installer/binaries, and haven't had the problem re-occur in 6 hours - so far. My conclusion is that 0.37 doesn't want to work with my OS/CPU/BIOS combination. Is anybody else getting similar behaviour?

<edit>OS=Win 7 Professional, CPU=AMD 1090T (stock speed/volts), BIOS=1.D</edit>
108) 留言板 : Number crunching : Astropulse: Why am I not getting work? (消息 1055047)
发表于:11 Dec 2010 作者: Profile Area 51
Post:
Area 51,

Dugh. And here I thought a mix of CUDA_10, high priority, "<count>.33</count>", good living and nothing else running removed a mysterious bottleneck that took me from 1 GPU WU in 8 minutes to 3 GPU WUs in 4 minutes. I even advanced my clock to force SETI back to "high priority". Sigh.

Well that reminds me of a comic slide: http://xkcd.com/530/.

Thanks for helping me get back to my life, already in progress.

Rich Seyfert
Now Late for the Post Office



Not quite sure what I did - sometimes its difficult to spot the obvious!
109) 留言板 : Number crunching : Astropulse: Why am I not getting work? (消息 1055017)
发表于:11 Dec 2010 作者: Profile Area 51
Post:
Perhaps you picked up a batch of shorties.......they do come by sometimes. Not every task is exactly the same length.
110) 留言板 : Number crunching : Panic Mode On (41) Server problems (消息 1054793)
发表于:10 Dec 2010 作者: Profile Area 51
Post:
I feel PANIC coming, because I do not have anything to complain about this Friday afternoon. All my computers are busy crunching, they all have enough WU's.

Something is wrong, because this is going too easy :-)

PANIC feelings...



ahhhh, but your are complaining about having nothing to complain about - which is a complaint in its own right; therefore, you do have something to complain about......! :-)

<edit>so stop complaining!!!!!</edit>
111) 留言板 : Number crunching : Not connecting and getting units to work (消息 1054791)
发表于:10 Dec 2010 作者: Profile Area 51
Post:
What makes a project run at "high priority"?
Whenever I enable any other project it takes over and runs at high priority and seti is stopped.



What are the deadlines like on the other projects? SAH is normally 6 weeks....

Look at the task deadlines.....any clues there?
112) 留言板 : Number crunching : whilst SETIs been off.... (消息 1053240)
发表于:5 Dec 2010 作者: Profile Area 51
Post:
Bounced out the old 955, and slid in a 1090 - two more cores!
113) 留言板 : Number crunching : Closed *SETI/BOINC Milestones [ v2.0 ] - XXI* Closed (消息 1051645)
发表于:28 Nov 2010 作者: Profile Area 51
Post:
Triple millionaire...!
114) 留言板 : Number crunching : Are the download servers running? (消息 1046306)
发表于:5 Nov 2010 作者: Profile Area 51
Post:
Spooky stuff!!!

I did a detach/attach to clear ghosts before the downloads were re-enabled yesterday, so I assume that worked (difficult to tell since we have no visibility of the task listings for our clients ATM). I had almost run out of tasks to process in the queue clearing that's currently going on - and bam, 20 lost tasks got re-sent!

So, for those that have run out of work, its probably worth leaving your client connected and asking for work, just in case you have created some new ghosts.......
115) 留言板 : Number crunching : Are the download servers running? (消息 1046059)
发表于:4 Nov 2010 作者: Profile Area 51
Post:
Got about 50 GPU tasks, and now I'm hitting http errors! Still, good to see some work is flowing, even though it is likely to be short lived. Not going to loose any sleep over it - I'll just get through what I get and then go back to other things 'till the situation returns to normal.
116) 留言板 : Number crunching : New Computers (消息 1045764)
发表于:3 Nov 2010 作者: Profile Area 51
Post:
Occasionally things get broken with the merge script. When it tells there are no computers eligible for merging it has a link called "Show Details".

Your posting the contents of that would help to trouble shoot it.

Regards




There is no 'Show Details' option after attempting the merge - just the message that the computers are incompatible.
117) 留言板 : Number crunching : New Computers (消息 1044987)
发表于:30 Oct 2010 作者: Profile Area 51
Post:
Good luck, but unfortunately merging doesn't always work. My machine has two identities courtesy of the recent server issues. I tried to merge them earlier today, and was told that the 'machines were incompatible' ???!!!! Bizarre really since both IDs relate to the same physical machine - which hasn't been updated/changed for a long time - and both IDs have the same name. Shame really, as I would really like to have kept the machine stats square. Still, worse things happen at sea.....
118) 留言板 : Number crunching : Emergency fund drive for the project............. (消息 1041223)
发表于:11 Oct 2010 作者: Profile Area 51
Post:
11%


<edit>Too slow!!!</edit>
119) 留言板 : Number crunching : Emergency fund drive for the project............. (消息 1041212)
发表于:11 Oct 2010 作者: Profile Area 51
Post:
Ooopps, looks like I gave again:


We received your gift of $20.00 via Visa on 10/11/2010.

If you have any questions or concerns, please contact us at
1-888-815-8885 or by e-mail at gahelp@berkeley.edu.

Your confirmation number is 63521.


Not intentional - guess its the cheap beer for a little longer!!!!!
120) 留言板 : Number crunching : Emergency fund drive for the project............. (消息 1040501)
发表于:10 Oct 2010 作者: Profile Area 51
Post:
I guess I'll be on cheap beer for a few days:

Thank you for your gift of $20.00 via Visa on 10/10/2010.
Your gift was assigned to the following areas:

SETI@home - $20.00

Your confirmation number is:
63540

Spend it wisely :-) !!!!


前 20 · 后面 20


 
©2020 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.