Workunit 665233

Message boards : Number crunching : Workunit 665233
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Sajjad Imam*

Send message
Joined: 24 Nov 13
Posts: 3
Credit: 1,160,073
RAC: 0
Bangladesh
Message 871 - Posted: 27 Aug 2016, 8:47:17 UTC

This WU has been running for over 3 days + on a 6 core machine using 4 cores.
Nobody has completed this. So, should I continue running this?
https://yafu.myfirewall.org/yafu/workunit.php?wuid=665233
ID: 871 · 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: 734
Credit: 17,574,526
RAC: 759
Germany
Message 872 - Posted: 27 Aug 2016, 12:09:26 UTC - in response to Message 871.  

As long as the factor.log in the slot directory changes at least every hour, the workunit makes progress and should be continued.
ID: 872 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Sajjad Imam*

Send message
Joined: 24 Nov 13
Posts: 3
Credit: 1,160,073
RAC: 0
Bangladesh
Message 873 - Posted: 27 Aug 2016, 12:53:55 UTC - in response to Message 872.  

Hmm...
The last entry of factor.log was 2 days ago....

08/25/16 07:03:15 v1.34.5 @ CONTRA, nfs: commencing lattice sieving with 4 threads

So, abort?
ID: 873 · 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: 734
Credit: 17,574,526
RAC: 759
Germany
Message 874 - Posted: 27 Aug 2016, 13:37:57 UTC - in response to Message 873.  

If possible, restart boinc and check if it continues.
ID: 874 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Sajjad Imam*

Send message
Joined: 24 Nov 13
Posts: 3
Credit: 1,160,073
RAC: 0
Bangladesh
Message 875 - Posted: 27 Aug 2016, 13:50:34 UTC - in response to Message 874.  

Restarted BIONIC, now it is showing elapsed time as 1 day+ instead of 3 days+!
The latest entry of factor.log:

08/27/16 09:44:55 v1.34.5 @ CONTRA, nfs: previous data file found - commencing search for last special-q
ID: 875 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>FAH-Addict.net]toTOW

Send message
Joined: 9 May 16
Posts: 7
Credit: 6,347,725
RAC: 7,928
France
Message 880 - Posted: 18 Oct 2016, 22:54:01 UTC

This WU hit my machine and doesn't seem to make any progress anymore ... here is the factor.log file :

10/15/16 02:36:57 v1.34.5 @ TALYN, 
10/15/16 02:36:57 v1.34.5 @ TALYN, ****************************
10/15/16 02:36:57 v1.34.5 @ TALYN, Starting factorization of 105477169960132837205975873926114604807951411895692657057922898665242377518763966282669255025070571114964556095309362452523270463
10/15/16 02:36:57 v1.34.5 @ TALYN, using pretesting plan: normal
10/15/16 02:36:57 v1.34.5 @ TALYN, no tune info: using qs/gnfs crossover of 95 digits
10/15/16 02:36:57 v1.34.5 @ TALYN, ****************************
10/15/16 02:36:57 v1.34.5 @ TALYN, rho: x^2 + 3, starting 1000 iterations on C129
10/15/16 02:36:57 v1.34.5 @ TALYN, rho: x^2 + 2, starting 1000 iterations on C129
10/15/16 02:36:57 v1.34.5 @ TALYN, rho: x^2 + 1, starting 1000 iterations on C129
10/15/16 02:36:57 v1.34.5 @ TALYN, pm1: starting B1 = 150K, B2 = gmp-ecm default on C129
10/15/16 02:36:57 v1.34.5 @ TALYN, current ECM pretesting depth: 0.00
10/15/16 02:36:57 v1.34.5 @ TALYN, scheduled 30 curves at B1=2000 toward target pretesting depth of 39.69
10/15/16 02:36:58 v1.34.5 @ TALYN, Finished 30 curves using Lenstra ECM method on C129 input, B1=2K, B2=gmp-ecm default
10/15/16 02:36:58 v1.34.5 @ TALYN, current ECM pretesting depth: 15.18
10/15/16 02:36:58 v1.34.5 @ TALYN, scheduled 74 curves at B1=11000 toward target pretesting depth of 39.69
10/15/16 02:37:04 v1.34.5 @ TALYN, Finished 74 curves using Lenstra ECM method on C129 input, B1=11K, B2=gmp-ecm default
10/15/16 02:37:04 v1.34.5 @ TALYN, current ECM pretesting depth: 20.24
10/15/16 02:37:04 v1.34.5 @ TALYN, scheduled 214 curves at B1=50000 toward target pretesting depth of 39.69
10/15/16 02:37:40 v1.34.5 @ TALYN, Finished 216 curves using Lenstra ECM method on C129 input, B1=50K, B2=gmp-ecm default
10/15/16 02:37:40 v1.34.5 @ TALYN, pm1: starting B1 = 3750K, B2 = gmp-ecm default on C129
10/15/16 02:37:43 v1.34.5 @ TALYN, current ECM pretesting depth: 25.34
10/15/16 02:37:43 v1.34.5 @ TALYN, scheduled 430 curves at B1=250000 toward target pretesting depth of 39.69
10/15/16 02:41:06 v1.34.5 @ TALYN, Finished 432 curves using Lenstra ECM method on C129 input, B1=250K, B2=gmp-ecm default
10/15/16 02:41:06 v1.34.5 @ TALYN, pm1: starting B1 = 15M, B2 = gmp-ecm default on C129
10/15/16 02:41:15 v1.34.5 @ TALYN, current ECM pretesting depth: 30.46
10/15/16 02:41:15 v1.34.5 @ TALYN, scheduled 904 curves at B1=1000000 toward target pretesting depth of 39.69
10/15/16 03:08:00 v1.34.5 @ TALYN, Finished 904 curves using Lenstra ECM method on C129 input, B1=1M, B2=gmp-ecm default
10/15/16 03:08:00 v1.34.5 @ TALYN, current ECM pretesting depth: 35.56
10/15/16 03:08:00 v1.34.5 @ TALYN, scheduled 1946 curves at B1=3000000 toward target pretesting depth of 39.69
10/15/16 05:45:08 v1.34.5 @ TALYN, Finished 1948 curves using Lenstra ECM method on C129 input, B1=3M, B2=gmp-ecm default
10/15/16 05:45:08 v1.34.5 @ TALYN, final ECM pretested depth: 39.70
10/15/16 05:45:08 v1.34.5 @ TALYN, scheduler: switching to sieve method
10/15/16 05:45:08 v1.34.5 @ TALYN, nfs: commencing nfs on c129: 105477169960132837205975873926114604807951411895692657057922898665242377518763966282669255025070571114964556095309362452523270463
10/15/16 05:45:08 v1.34.5 @ TALYN, nfs: commencing poly selection with 4 threads
10/15/16 05:45:08 v1.34.5 @ TALYN, nfs: setting deadline of 11435 seconds
10/15/16 08:53:00 v1.34.5 @ TALYN, nfs: completed 23 ranges of size 250 in 11271.8597 seconds
10/15/16 08:53:00 v1.34.5 @ TALYN, nfs: best poly = # norm 3.240702e-012 alpha -7.253759 e 1.077e-010 rroots 5
10/15/16 08:53:00 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 09:23:17 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 09:55:07 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 10:25:02 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 10:57:02 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 11:26:47 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 11:56:46 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 12:27:32 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 12:58:06 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 13:29:05 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 14:01:25 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 14:34:15 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 15:05:18 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 15:36:37 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 16:08:00 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 16:38:55 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 17:10:18 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 17:42:23 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 18:13:37 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/15/16 18:45:22 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 07:15:53 v1.34.5 @ TALYN, 
10/16/16 07:15:53 v1.34.5 @ TALYN, ****************************
10/16/16 07:15:53 v1.34.5 @ TALYN, Starting factorization of 105477169960132837205975873926114604807951411895692657057922898665242377518763966282669255025070571114964556095309362452523270463
10/16/16 07:15:53 v1.34.5 @ TALYN, using pretesting plan: normal
10/16/16 07:15:53 v1.34.5 @ TALYN, no tune info: using qs/gnfs crossover of 95 digits
10/16/16 07:15:53 v1.34.5 @ TALYN, ****************************
10/16/16 07:15:53 v1.34.5 @ TALYN, nfs: previous data file found - commencing search for last special-q
10/16/16 07:15:56 v1.34.5 @ TALYN, nfs: parsing special-q from .dat file
10/16/16 07:15:56 v1.34.5 @ TALYN, nfs: commencing nfs on c129: 105477169960132837205975873926114604807951411895692657057922898665242377518763966282669255025070571114964556095309362452523270463
10/16/16 07:15:56 v1.34.5 @ TALYN, nfs: resuming with filtering
10/16/16 07:15:56 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 07:46:36 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 08:17:02 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 08:48:44 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 09:21:11 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 09:53:07 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 10:24:53 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 10:56:53 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 11:28:26 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 12:01:09 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 12:33:48 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 13:06:17 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 13:38:51 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 14:11:01 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 14:43:13 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 15:16:09 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 15:47:40 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 16:20:15 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 16:51:57 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 17:24:22 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 17:56:18 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 18:28:12 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 19:00:30 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 19:32:43 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 20:06:06 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 20:39:28 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 21:12:29 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 21:45:01 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
10/16/16 22:15:48 v1.34.5 @ TALYN, nfs: commencing lattice sieving with 4 threads
ID: 880 · 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: 734
Credit: 17,574,526
RAC: 759
Germany
Message 881 - Posted: 19 Oct 2016, 4:17:43 UTC - in response to Message 880.  

The log stops at 16.. Try to stop Boinc and check if the wu continues and the log is written again. The wu should continue from where it is. If not abort the wu.
ID: 881 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>FAH-Addict.net]toTOW

Send message
Joined: 9 May 16
Posts: 7
Credit: 6,347,725
RAC: 7,928
France
Message 882 - Posted: 19 Oct 2016, 21:47:18 UTC

It resumed from checkpoint (I guess) ... let's see if it can go to the end this time ...
ID: 882 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>FAH-Addict.net]toTOW

Send message
Joined: 9 May 16
Posts: 7
Credit: 6,347,725
RAC: 7,928
France
Message 883 - Posted: 21 Oct 2016, 21:05:11 UTC

The WU stalled again almost immediately after BOINC restart, so something is wrong with it, you can pull it off distribution ... :(
ID: 883 · 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: 734
Credit: 17,574,526
RAC: 759
Germany
Message 884 - Posted: 22 Oct 2016, 7:36:42 UTC - in response to Message 883.  

I canceled this workunit.

I was computing this composite on my Linux system without Boinc without problems.
ID: 884 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Workunit 665233




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