Welcome to MilkyWay@home

Posts by Ensor

1) Message boards : Number crunching : Home page suggestion (Message 2736)
Posted 24 Mar 2008 by Ensor
Post:

Yeah, and what's with that truly ABYSMAL new logo...?

PLEASE GET RID OF IT AS SOON AS POSSIBLE, it makes me physically ill every time I see it!!!! :-(


TTFN - Pete (trying not to be sick).
2) Message boards : Number crunching : Error report (Message 1612)
Posted 27 Jan 2008 by Ensor
Post:

Another couple of oddities to report.

Firstly, WU #2755228 ended with a "Compute Error" on my host, though the next cruncher completed it without issue.

Secondly, WU #1545214 is causing problems for every host it's been assigned to. For most of us it's showing as a "No reply".

I notice it's name has a corrupted character in it, which might have something to do with it.


TTFN - Pete.
3) Message boards : Number crunching : Client errors (Message 1598)
Posted 26 Jan 2008 by Ensor
Post:
Hi,

I don't think it is individual workunits causing the freeze. I think it is the way the application communicates with the Boinc client....

There may well be something to this.

I should've mentioned this before, but about a week or so ago I had to restart my host, at the time BOINC was crunching a non Milkyway WU and had three Milkyway tasks queued up ready to run.

When BOINC restarted all three of the Milkyway WUs immediately "errored out" showing compute errors in the BOINC manager, even though, AFAIK, BOINC hadn't even attempted to run them yet....

[EDIT] These would be WUs #2486445, #2486167 and #2485667. If you look at my results page here you can see the three units in question.


TTFN - Pete.
4) Message boards : Number crunching : No work from project ... (Message 1564)
Posted 21 Jan 2008 by Ensor
Post:

Hi,

No work again :(

See this message from Travis.


TTFN - Pete.
5) Message boards : Number crunching : AMD64 (Message 1540)
Posted 20 Jan 2008 by Ensor
Post:

Hi,

....pretty sure our next version of the app will have a linux 64 bit binary.

More importantly, how about a Windows 64-bit app? ;-)


TTFN - Pete.
6) Message boards : Number crunching : WU just stops (Message 1425)
Posted 11 Jan 2008 by Ensor
Post:
Hi,

I got one of these yesterday too, WU #2090323....

Actually, I should have added that I tried suspending and restarting both the project and BOINC, with no joy, the WU simply refused to continue. Had no option but to abort it.


TTFN - Pete.
7) Message boards : Number crunching : WU just stops (Message 1410)
Posted 10 Jan 2008 by Ensor
Post:

I got one of these yesterday too, WU #2090323 just stopped running for no apparent reason....


TTFN - Pete.
8) Message boards : Number crunching : Error report (Message 1353)
Posted 5 Jan 2008 by Ensor
Post:
Just a quick note to report that it appears that Milkyway WUs don't appear to appreciate being suspended....

Earlier this evening BOINC on my host suspended WU #1883917 in order to run it's weekly benchmarks, said WU immediately errored out.

Here's the appropriate extract from BOINC's log:

04/01/2008 18:46:03||Running CPU benchmarks
04/01/2008 18:46:03||Suspending computation - running CPU benchmarks
04/01/2008 18:46:13|Milkyway@home|Deferring communication for 1 min 0 sec
04/01/2008 18:46:13|Milkyway@home|Reason: Unrecoverable error for result gs_90_1199516100_135551_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003))
04/01/2008 18:46:13|Milkyway@home|Computation for task gs_90_1199516100_135551_0 finished
04/01/2008 18:46:13|Milkyway@home|Output file gs_90_1199516100_135551_0_0 for task gs_90_1199516100_135551_0 absent


Not a big problem for me, but I just thought you should know.


TTFN - Pete.
9) Message boards : Number crunching : done WUs- now upload is failing (Message 1342)
Posted 4 Jan 2008 by Ensor
Post:

Hi,

....I'm fairly sure I was a victim of the permissions, but then the WUs still didn't want to send by themselves.
After I rebooted my system, I was able to 'retry' the uploads, and it worked.

Sounds you may have been a victim of the BOINC "DNS caching" bug, which keeps getting fixed but never quite has neeb....

Next time you have a problem uploading try just restarting BOINC and see if your uploads then start working. Works for me 9 times out of 10!


TTFN - Pete.
10) Message boards : Number crunching : download failing (Message 1286)
Posted 3 Jan 2008 by Ensor
Post:

Hi,

The 30% it gets is most likely the error page saying "403 forbidden" which is about 330 bytes in size.

....mutter, mutter....I never thought of that....mutter, mutter.... ;-)

I was forgetting how BOINC works "under the hood", you make a very good point.


TTFN - Pete.
11) Message boards : Number crunching : Hard to get new work ! (Message 1285)
Posted 3 Jan 2008 by Ensor
Post:

Hi,

....it wouldn’t ask for new work from anywhere until I aborted those transfers. However, a newer version of BOINC than mine (v5.4.9) might not have the same problem.

I'm running BOINC v5.10.13 (64-bit build) and can confirm it doesn't exhibit this problem; it'll carry on requesting work from and crunching other projects just fine when "Milkyway" transfers hang.


TTFN - Pete.
12) Message boards : Number crunching : download failing (Message 1274)
Posted 3 Jan 2008 by Ensor
Post:

Hi,

The problem appears to be with missing directories, or permissions....

I doubt that very much. The problematical files partially download and usually "stick" at around 30% or so....more likely file/filesystem corruption.

In any case, it really doesn't matter from our perspective. All that matters is that we can't get the file, speculating as to why is pretty pointless.

It'll get fixed in due course.


TTFN - Pete.
13) Message boards : Number crunching : Unit caught in a loop (Message 1244)
Posted 1 Jan 2008 by Ensor
Post:

Hi,

....If you get one abort the WU (Task Tab) and the transfer file (transfer tab in BOINC Manager).

You only actually need to abort the transfer, the WU will be automatically aborted when you do this.


TTFN - Pete.

14) Message boards : Number crunching : Hard to get new work ! (Message 1233)
Posted 1 Jan 2008 by Ensor
Post:

The only WU I've so far had refuse to download is #1741653.

I cancelled it after I noticed that a previous host had also found it impossible to download (though I left it for over a day before finally cancelling it). I'm assuming missing file(s) on the server...?


TTFN - Pete.
15) Message boards : Number crunching : Breakpoint Encountered (0x80000003) (Message 550)
Posted 23 Nov 2007 by Ensor
Post:
Hi,

I get these pop-ups all the time with this project....

....However, these pop-up errors are a real problem, because they impact other projects as well. Because the pops-ups do not release the thread/core until they are manually dismissed....

Hmm, not on my host they don't....

I've had my fair share of these pop-ups and *NOT ONCE* has BOINC failed to switch to the next task and continue on normally! In fact, the first time I saw these pop-ups I had 6 of them on the screen simultaneously....and BOINC was happily crunching away at Einstein....

Setup here is WinXP x64 and BOINC v5.10.13 64bit build (and I run BOINC the proper way - as a service! :-)).


TTFN - Pete.
16) Message boards : Number crunching : is this output correct ? (Message 451)
Posted 15 Nov 2007 by Ensor
Post:
Hi,

Odd, thought we had fixed all those. What OS/architecture are you running?

Whoops, I knew I'd forgotten something....sorry.

I'm running "Windows XP Pro, x64 Edition" SP1, on an AMD Athlon64. Also, BOINC v5.10.13, x64 build (official).


Also just noticed, although my results are being granted credit, their validate state is showing as "Initial"!?


TTFN - Pete.
17) Message boards : Number crunching : is this output correct ? (Message 427)
Posted 13 Nov 2007 by Ensor
Post:

Sorry for the large quote, but I see the following in all of my returned results:

<core_client_version>5.10.13</core_client_version>
<![CDATA[
<stderr_txt>
reading parameters file: parameters.txt
APP: astronomy reading volume from file: volume.txt
APP: astronomy reading integral checkpoint file
APP: astronomy read integral checkpoint finished
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy reading likelihood checkpoint file
APP: astronomy read likelihood checkpoint finished
APP: astronomy likelihood checkpointing
APP: astronomy likelihood checkpoint done


**********
**********

Memory Leaks Detected!!!

Memory Statistics:
0 bytes in 0 Free Blocks.
166 bytes in 4 Normal Blocks.
12916 bytes in 8 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 6413860 bytes.
Total allocations: 11300360 bytes.

Dumping objects ->
c:\research\boinc_samples\astronomy\parameters.c(168) : {400115} normal block at 0x02E851C0, 64 bytes long.
Data: < m5 ?| -@> 17 A0 6D 35 EB 8C E6 3F 7C 80 EE CB 99 05 2D 40
{55} normal block at 0x01D550F0, 12 bytes long.
Data: <X> C K > 58 3E D5 01 B8 43 D5 01 90 4B D5 01
c:\research\boinc\api\boinc_api.c(160) : {50} normal block at 0x01D52960, 4 bytes long.
Data: < > 00 00 EB 01
c:\research\boinc\lib\parse.c(142) : {49} normal block at 0x01D528D8, 86 bytes long.
Data: < <color_scheme>T> 0A 3C 63 6F 6C 6F 72 5F 73 63 68 65 6D 65 3E 54
Object dump complete.


</stderr_txt>
]]>


It's the "memory leaks detected" part which concerns me....


TTFN - Pete.




©2020 Astroinformatics Group