WU 9 days over deadline

Message boards : Number crunching : WU 9 days over deadline
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile rebel9

Send message
Joined: 6 Sep 11
Posts: 8
Credit: 4,017,800
RAC: 141
Australia
Message 841 - Posted: 26 Apr 2016, 19:08:19 UTC
Last modified: 26 Apr 2016, 19:09:19 UTC

Hi,

I have this WU, which is 9 days over its deadline. I've been waiting on it patiently and avoided killing it but I now see that is says it's "Timed out - no response". What's going on here? This WU has been hogging my machine for the last week. What should I do with it?

Thanks.
ID: 841 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile yoyo_rkn
Volunteer moderator
Project administrator
Project developer
Project tester
Volunteer developer
Volunteer tester
Project scientist

Send message
Joined: 22 Aug 11
Posts: 722
Credit: 16,445,605
RAC: 189
Germany
Message 842 - Posted: 26 Apr 2016, 19:51:05 UTC - in response to Message 841.  

This wu is long over its deadline, you should kill it.
ID: 842 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
hsdecalc

Send message
Joined: 3 Apr 16
Posts: 3
Credit: 2,729,728
RAC: 0
Germany
Message 843 - Posted: 27 Apr 2016, 18:21:10 UTC
Last modified: 27 Apr 2016, 18:58:56 UTC

I check the running WU as follows:
- Open file factor.log from folder Boinc\slots\nn
- check if new lines are generated at regular intervals
- check taskmanager, details, if programs active with filename like: gnfs-lasieve4I13e.exe.

The Boinc Function "Show Graphic" show you the type of sequence. If it is a Open End then it take a long time to find the next number.
When the job is finished I check the factordb.com for the new result.

Sample of factor.log:
...
04/27/16 14:24:30 v1.34.5 @ CRUNCHER, nfs: commencing nfs on c126: 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323
04/27/16 14:24:30 v1.34.5 @ CRUNCHER, nfs: commencing poly selection with 4 threads
04/27/16 14:24:30 v1.34.5 @ CRUNCHER, nfs: setting deadline of 8047 seconds
04/27/16 16:37:08 v1.34.5 @ CRUNCHER, nfs: completed 32 ranges of size 250 in 7958.5150 seconds
04/27/16 16:37:08 v1.34.5 @ CRUNCHER, nfs: best poly = # norm 5.506486e-012 alpha -7.112219 e 1.450e-010 rroots 3
04/27/16 16:37:08 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 16:53:09 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 17:09:19 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 17:37:45 v1.34.5 @ CRUNCHER,
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, ****************************
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, Starting factorization of 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, using pretesting plan: normal
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, no tune info: using qs/gnfs crossover of 95 digits
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, ****************************
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: previous data file found - commencing search for last special-q
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: parsing special-q from .dat file
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: commencing nfs on c126: 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: resuming with filtering
04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 17:53:33 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 18:08:40 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 18:24:16 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 18:40:11 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 18:56:06 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 19:12:18 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 19:26:06 v1.34.5 @ CRUNCHER,
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, ****************************
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, Starting factorization of 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, using pretesting plan: normal
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, no tune info: using qs/gnfs crossover of 95 digits
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, ****************************
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: previous data file found - commencing search for last special-q
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: parsing special-q from .dat file
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: commencing nfs on c126: 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: resuming with filtering
04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 19:42:07 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads
04/27/16 19:58:36 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads....
ID: 843 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : WU 9 days over deadline




Datenschutz / Privacy Copyright © 2011-2024 Rechenkraft.net e.V. & yoyo