Welcome to MilkyWay@home

Posts by aad

1) Message boards : News : New Separation Runs (Message 68529)
Posted 14 Apr 2019 by aad
Post:
They take more time to crunch.(AMD 480)
But also get more credits.
2) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68503)
Posted 10 Apr 2019 by aad
Post:
Another log;
10-4-2019 18:30:58 |  | [work_fetch] ------- start work fetch state -------
10-4-2019 18:30:58 |  | [work_fetch] target work buffer: 259200.00 + 0.00 sec
10-4-2019 18:30:58 |  | [work_fetch] --- project states ---
10-4-2019 18:30:58 | Milkyway@Home | [work_fetch] REC 119466.096 prio -38.414 can't request work: scheduler RPC backoff (8735.63 sec)
10-4-2019 18:30:58 |  | [work_fetch] --- state for CPU ---
10-4-2019 18:30:58 |  | [work_fetch] shortfall 1386459.51 nidle 0.00 saturated 28117.82 busy 0.00
10-4-2019 18:30:58 | Milkyway@Home | [work_fetch] share 0.000 blocked by project preferences
10-4-2019 18:30:58 |  | [work_fetch] --- state for AMD/ATI GPU ---
10-4-2019 18:30:58 |  | [work_fetch] shortfall 113602.96 nidle 0.00 saturated 144319.80 busy 0.00
10-4-2019 18:30:58 | Milkyway@Home | [work_fetch] share 0.000
10-4-2019 18:30:58 |  | [work_fetch] ------- end work fetch state -------
10-4-2019 18:30:58 |  | [work_fetch] No project chosen for work fetch
10-4-2019 18:31:01 |  | [work_fetch] Request work fetch: Backoff ended for Cosmology@Home
10-4-2019 18:31:04 |  | [work_fetch] ------- start work fetch state -------
10-4-2019 18:31:04 |  | [work_fetch] target work buffer: 259200.00 + 0.00 sec
10-4-2019 18:31:04 |  | [work_fetch] --- project states ---
10-4-2019 18:31:04 | Milkyway@Home | [work_fetch] REC 119466.096 prio -54.314 can't request work: scheduler RPC backoff (8730.30 sec)
10-4-2019 18:31:04 |  | [work_fetch] --- state for CPU ---
10-4-2019 18:31:04 |  | [work_fetch] shortfall 1386444.14 nidle 0.00 saturated 28125.51 busy 0.00
10-4-2019 18:31:04 | Milkyway@Home | [work_fetch] share 0.000 blocked by project preferences
10-4-2019 18:31:04 |  | [work_fetch] --- state for AMD/ATI GPU ---
10-4-2019 18:31:04 |  | [work_fetch] shortfall 113650.18 nidle 0.00 saturated 144237.46 busy 0.00
10-4-2019 18:31:04 | Milkyway@Home | [work_fetch] share 0.000
10-4-2019 18:31:04 |  | [work_fetch] ------- end work fetch state -------
10-4-2019 18:31:05 |  | [http_xfer] [ID#1] HTTP: wrote 2946 bytes
10-4-2019 18:31:05 |  | [work_fetch] Request work fetch: RPC complete
10-4-2019 18:31:10 |  | [work_fetch] ------- start work fetch state -------
10-4-2019 18:31:10 |  | [work_fetch] target work buffer: 259200.00 + 0.00 sec
10-4-2019 18:31:10 |  | [work_fetch] --- project states ---
10-4-2019 18:31:10 | Milkyway@Home | [work_fetch] REC 119466.096 prio -38.405 can't request work: scheduler RPC backoff (8723.90 sec)
10-4-2019 18:31:10 |  | [work_fetch] --- state for CPU ---
10-4-2019 18:31:10 |  | [work_fetch] shortfall 1386446.16 nidle 0.00 saturated 28124.50 busy 0.00
10-4-2019 18:31:10 | Milkyway@Home | [work_fetch] share 0.000 blocked by project preferences
10-4-2019 18:31:10 |  | [work_fetch] --- state for AMD/ATI GPU ---
10-4-2019 18:31:10 |  | [work_fetch] shortfall 113699.39 nidle 0.00 saturated 144155.11 busy 0.00
10-4-2019 18:31:10 | Milkyway@Home | [work_fetch] share 0.000
10-4-2019 18:31:10 |  | [work_fetch] ------- end work fetch state -------
10-4-2019 18:31:10 |  | [work_fetch] No project chosen for work fetch
10-4-2019 18:31:12 |  | [work_fetch] Request work fetch: Backoff ended for Cosmology@Home
10-4-2019 18:31:15 |  | [work_fetch] ------- start work fetch state -------
10-4-2019 18:31:15 |  | [work_fetch] target work buffer: 259200.00 + 0.00 sec
10-4-2019 18:31:15 |  | [work_fetch] --- project states ---
10-4-2019 18:31:15 | Milkyway@Home | [work_fetch] REC 119466.096 prio -54.303 can't request work: scheduler RPC backoff (8718.85 sec)
10-4-2019 18:31:15 |  | [work_fetch] --- state for CPU ---
10-4-2019 18:31:15 |  | [work_fetch] shortfall 1386446.17 nidle 0.00 saturated 28124.49 busy 0.00
10-4-2019 18:31:15 | Milkyway@Home | [work_fetch] share 0.000 blocked by project preferences
10-4-2019 18:31:15 |  | [work_fetch] --- state for AMD/ATI GPU ---
10-4-2019 18:31:15 |  | [work_fetch] shortfall 113741.79 nidle 0.00 saturated 144090.83 busy 0.00
10-4-2019 18:31:15 | Milkyway@Home | [work_fetch] share 0.000
10-4-2019 18:31:15 |  | [work_fetch] ------- end work fetch state -------
10-4-2019 18:31:15 |  | [work_fetch] No project chosen for work fetch
10-4-2019 18:32:00 | Milkyway@Home | Message from task: 0
10-4-2019 18:32:00 |  | [work_fetch] Request work fetch: application exited
10-4-2019 18:32:00 | Milkyway@Home | Computation for task de_modfit_82_bundle5_3s_NoContraintsWithDisk200_6_1554838388_240454_1 finished
10-4-2019 18:32:00 | Milkyway@Home | Starting task de_modfit_82_bundle5_3s_NoContraintsWithDisk200_6_1554838388_188776_1
10-4-2019 18:32:01 |  | [work_fetch] ------- start work fetch state -------
10-4-2019 18:32:01 |  | [work_fetch] target work buffer: 259200.00 + 0.00 sec
10-4-2019 18:32:01 |  | [work_fetch] --- project states ---
10-4-2019 18:32:01 | Milkyway@Home | [work_fetch] REC 119467.655 prio -54.178 can't request work: scheduler RPC backoff (8673.18 sec)
10-4-2019 18:32:01 |  | [work_fetch] --- state for CPU ---
10-4-2019 18:32:01 |  | [work_fetch] shortfall 1386531.14 nidle 0.00 saturated 28082.01 busy 0.00
10-4-2019 18:32:01 | Milkyway@Home | [work_fetch] share 0.000 blocked by project preferences
10-4-2019 18:32:01 |  | [work_fetch] --- state for AMD/ATI GPU ---
10-4-2019 18:32:01 |  | [work_fetch] shortfall 114107.80 nidle 0.00 saturated 143502.34 busy 0.00
10-4-2019 18:32:01 | Milkyway@Home | [work_fetch] share 0.000
10-4-2019 18:32:01 |  | [work_fetch] ------- end work fetch state -------
10-4-2019 18:32:01 |  | [work_fetch] No project chosen for work fetch
3) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68501)
Posted 10 Apr 2019 by aad
Post:
Hi Jake,
I get this;
10-4-2019 18:08:24 | Milkyway@Home | Sending scheduler request: Requested by project.
10-4-2019 18:08:24 | Milkyway@Home | Reporting 2 completed tasks
10-4-2019 18:08:24 | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
10-4-2019 18:08:24 | Milkyway@Home | [http] HTTP_OP::init_post(): http://milkyway.cs.rpi.edu/milkyway_cgi/cgi
10-4-2019 18:08:24 | Milkyway@Home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
10-4-2019 18:08:25 | Milkyway@Home | [http] [ID#1] Info:  Connection 14796 seems to be dead!
10-4-2019 18:08:25 | Milkyway@Home | [http] [ID#1] Info:  Closing connection 14796
10-4-2019 18:08:25 | Milkyway@Home | [http] [ID#1] Info:  timeout on name lookup is not supported
10-4-2019 18:08:25 | Milkyway@Home | [http] [ID#1] Info:  Hostname was NOT found in DNS cache
10-4-2019 18:08:25 | Milkyway@Home | [http] [ID#1] Info:    Trying 128.113.126.23...
10-4-2019 18:08:46 | Milkyway@Home | [http] [ID#1] Info:  connect to 128.113.126.23 port 80 failed: Timed out
10-4-2019 18:08:46 | Milkyway@Home | [http] [ID#1] Info:  Failed to connect to milkyway.cs.rpi.edu port 80: Timed out
10-4-2019 18:08:46 | Milkyway@Home | [http] [ID#1] Info:  Closing connection 14797
10-4-2019 18:08:46 | Milkyway@Home | [http] HTTP error: Couldn't connect to server
10-4-2019 18:08:47 | Milkyway@Home | Message from task: 0
10-4-2019 18:08:47 |  | Project communication failed: attempting access to reference site
10-4-2019 18:08:47 |  | [http] HTTP_OP::init_get(): http://www.google.com/
10-4-2019 18:08:47 |  | [http] HTTP_OP::libcurl_exec(): ca-bundle set
10-4-2019 18:08:47 | Milkyway@Home | Computation for task de_modfit_82_bundle5_3s_NoContraintsWithDisk200_6_1554838388_259291_0 finished
10-4-2019 18:08:47 | Milkyway@Home | Starting task de_modfit_82_bundle5_3s_NoContraintsWithDisk200_6_1554838388_259043_0
10-4-2019 18:08:47 | Milkyway@Home | Scheduler request failed: Couldn't connect to server
10-4-2019 18:08:47 |  | [http] [ID#0] Info:  Found bundle for host www.google.com: 0x420e9d0
10-4-2019 18:08:47 |  | [http] [ID#0] Info:  Re-using existing connection! (#14792) with host www.google.com
10-4-2019 18:08:47 |  | [http] [ID#0] Info:  Connected to www.google.com (172.217.168.196) port 80 (#14792)
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server: GET / HTTP/1.1
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.6.9)
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server: Host: www.google.com
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server: Accept: */*
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server: Accept-Encoding: deflate, gzip
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server: Content-Type: application/x-www-form-urlencoded
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server: Accept-Language: nl_NL
10-4-2019 18:08:47 |  | [http] [ID#0] Sent header to server:
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: HTTP/1.1 200 OK
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Date: Wed, 10 Apr 2019 16:08:44 GMT
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Expires: -1
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Cache-Control: private, max-age=0
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Content-Type: text/html; charset=ISO-8859-1
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Content-Encoding: gzip
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Server: gws
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Content-Length: 5391
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: X-XSS-Protection: 0
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: X-Frame-Options: SAMEORIGIN
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Set-Cookie: 1P_JAR=2019-04-10-16; expires=Fri, 10-May-2019 16:08:44 GMT; path=/; domain=.google.com
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server: Set-Cookie: NID=181=bwE86MbCUawsBGBqs_fbVtR-dbTSa4bch72lxHSb7KkM9bxznXqB3nk65g-EKFS_M1mB9LlYUDrSGlqc_-pq6UbxzZAeQxp9LgGNmFXK2NFqR3FjtVseMt_SDO5_oV-GaCnjzLZSwHAWyNtXGIKj_Is-PwPRUgugsACmhglVlDA; expires=Thu, 10-Oct-2019 16:08:44 GMT; path=/; domain=.google.com; HttpOnly
10-4-2019 18:08:47 |  | [http] [ID#0] Received header from server:
10-4-2019 18:08:47 |  | [http] [ID#0] Info:  Connection #14792 to host www.google.com left intact
10-4-2019 18:08:48 |  | Internet access OK - project servers may be temporarily down.

I will set some more debug logs to help you understand the problem
4) Message boards : Number crunching : Invalids Exit status 0 (0x0) after server came back (Message 68238)
Posted 8 Mar 2019 by aad
Post:
With two machines running;
5% invalid and the other 7% invalid...
Before it was 0% on both machines...
5) Message boards : News : Database Maintenance 9-4-2014 (Message 67785)
Posted 6 Sep 2018 by aad
Post:
Yep, all of my WUs are _0 as well, so it looks like _1 are kept behind for now.


+1
6) Message boards : News : New Separation Runs (Message 67742)
Posted 29 Aug 2018 by aad
Post:
You can check it with this machine;
http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=399761
Thanks for looking in to this.

I think you don't have to bother with calculating the credit.
There is (with this GPU)only 5 or 6 seconds between the 6-2 and 4-4 versions.

Aad
7) Message boards : News : New Separation Runs (Message 67731)
Posted 27 Aug 2018 by aad
Post:
As I investigated further;
Seems that only with ATI-cards the 'de_modfit_sim19fixed_bundle6_2s_NoContraintsWithDisk140' take longer to process and get less credit for it...
8) Message boards : News : New Separation Runs (Message 67729)
Posted 27 Aug 2018 by aad
Post:
The credit awarded should reflect the run time.

If you have any questions or issues, let me know.

Jake

de_modfit_sim19fixed_bundle6_2s_NoContraintsWithDisk140

take a few seconds longer, but get 203.92 credit instead of 227.62 credits....
This seems wrong to me.
Anyone else see this behavior...?
9) Message boards : Number crunching : no d/l od WU today after outage/no contact yesterday. (Message 66915)
Posted 1 Jan 2018 by aad
Post:
It looks like there is a daily problem with the database.
This morning my up/downloads went down again.
When I checked in my account, it didn't recognize me.
And the site said there was a database problem.
But a few hours later there is nothing wrong and no 'heads-up' from the crew in the news section....
Auto-repair....?
10) Message boards : Number crunching : no d/l od WU today after outage/no contact yesterday. (Message 66910)
Posted 31 Dec 2017 by aad
Post:
I think there was a database problem.
But it seems to be working well now.
11) Message boards : Number crunching : I have pages of completed work units but (Message 66898)
Posted 28 Dec 2017 by aad
Post:
· Validation inconclusive (6616) · Valid (11966) · Invalid (0) · Error (1)
I have reached over 1.5 million credits in Validation Inconclusive.
Could this be because a lot of people are not crunching over Xmas/New Year?

No, just click on a few of those inconclusive workunits you have crunched.
You see that it is not send to a wingman yet.....
Why......?.......we just don't know......but it is probably a bug serverside.
12) Message boards : Number crunching : I have pages of completed work units but (Message 66891)
Posted 27 Dec 2017 by aad
Post:
Something like this?;
 Validation inconclusive (1780) · Valid (1788) · Invalid (1) · Error (0) 

I think in a short while the database runs out of space this way.....
13) Message boards : News : New Runs 11/21 (Message 66797)
Posted 21 Nov 2017 by aad
Post:
And they run well!
Thanks for making sure it's allright before leaving work.

Happy Thanksgiving.
14) Message boards : News : New Runs 11/21 (Message 66795)
Posted 21 Nov 2017 by aad
Post:
And;
de_modfit_fast_19_3s_146_bundle5_ModfitConstraintsWithDiskandUpdateStreams_1_Rerun_3
de_modfit_fast_19_3s_146_bundle5_ModfitConstraintsWithDiskandUpdateStreams_1_Rerun_4
de_modfit_fast_19_3s_146_bundle5_ModfitConstraintsWithDiskandUpdateStreams_1_Rerun_5
de_modfit_fast_19_3s_146_bundle5_ModfitConstraintsWithDiskandUpdateStreams_1_Rerun_6
?
15) Message boards : News : Update on This Weeks Errors (Message 66742)
Posted 22 Oct 2017 by aad
Post:
State: All (825) · In progress (158) · Validation pending (1) · Validation inconclusive (62) · Valid (502) · Invalid (54) · Error (48) 


Mutch better.
It probably takes some more time to clear the emty errorous 'Error' state.....;-)
16) Message boards : News : Update on This Weeks Errors (Message 66740)
Posted 22 Oct 2017 by aad
Post:
I will try a single load of wu's to help things sorted out.

{edit}
Numbers are looking better now.
There are wu's validated now
State: All (828) · In progress (318) · Validation pending (1) · Validation inconclusive (59) · Valid (346) · Invalid (56) · Error (48) 
17) Message boards : News : Clearing the Queue (Message 66739)
Posted 22 Oct 2017 by aad
Post:
But when none from the Top 5 participants do Not complain on hundreds of thousands and more.. faulty,valid but no count , or no validated units they produced in last days... so it's very strange. strange philosophy of donating..
it might be good to leave them here alone in the production of zeros))


I think their riggs are unattended....
18) Message boards : News : Clearing the Queue (Message 66708)
Posted 19 Oct 2017 by aad
Post:
All the work I did today is in the state of 'invalid'(Completed, can't validate)
or 'Validation inconclusive'(Completed, validation inconclusive)
Not a single wu is validated today!
State: All (2124) · In progress (159) · Validation pending (1) · Validation inconclusive (528) · Valid (393) · Invalid (554) · Error (489)


I stop doin' work for the wastebasket....
19) Message boards : News : Transitioner Down (Message 66696)
Posted 18 Oct 2017 by aad
Post:
Thanks for working on this issue, Jake...
Wu's are flowing again.

Can you tell that work was lost in dealing with this problem?
In my account I can see lots of errors.
On this one machine there were no errors and now there are many;
State: All (1954) · In progress (160) · Validation pending (183) · Validation inconclusive (443) · Valid (679) · Invalid (0) · Error (489)


But when I click on it; "No tasks to display"

{edit} In the time typing above there is a message in new thread (Message 66695)
20) Message boards : Number crunching : 454 credits ??? (Message 66662)
Posted 24 Sep 2017 by aad
Post:
Since last weeks errors on "de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk-fixed_Bouncy" the wu's take allmost twice as long to crunch and get 454 credits.
"de_modfit_fast_19_3s_146_bundle5_ModfitConstraintsWithDiskandUpdateStreams_Bouncy","de_modfit_fast_20_3s_146_bundle5_ModfitConstraintsWithDisk-fixed_Bouncy", get the normal amout of 227credits.
There is no explanation at all in 'news'.

Why is that or is it another bug?

If science is not in question you can leave it this way.
There is less overhead in the crunching, so more wu's/time...


Next 20

©2020 Astroinformatics Group