Posts by Matthias Lehmkuhl

21) Message boards : Number crunching : Long running work units (Message 458) Posted 19 Jul 2012 by Matthias Lehmkuhl Post: Late again, there where no changes to the files in the slot dir round the last 12 hours. And the CPU time of the process was growing. here the requested factor.log 07/07/12 23:35:04 v1.30 @ host ID: 1397 , 07/07/12 23:35:04 v1.30 @ host ID: 1397 , ************************** 07/07/12 23:35:04 v1.30 @ host ID: 1397 , Starting factorization of 8938861779072390809014308542579704644988289566455519966972540828521729483117056503398097479159550310460743973 07/07/12 23:35:04 v1.30 @ host ID: 1397 , using pretesting plan: normal 07/07/12 23:35:04 v1.30 @ host ID: 1397 , no tune info: using qs/gnfs crossover of 95 digits 07/07/12 23:35:04 v1.30 @ host ID: 1397 , ************************ 07/07/12 23:35:04 v1.30 @ host ID: 1397 , pp1: starting B1 = 20K, B2 = gmp-ecm default on C109 07/07/12 23:35:04 v1.30 @ host ID: 1397 , pp1: starting B1 = 20K, B2 = gmp-ecm default on C109 07/07/12 23:35:04 v1.30 @ host ID: 1397 , pp1: starting B1 = 20K, B2 = gmp-ecm default on C109 07/07/12 23:35:04 v1.30 @ host ID: 1397 , pm1: starting B1 = 100K, B2 = gmp-ecm default on C109 07/07/12 23:35:05 v1.30 @ host ID: 1397 , current ECM pretesting depth: 0.00 07/07/12 23:35:05 v1.30 @ host ID: 1397 , scheduled 30 curves at B1=2000 toward target pretesting depth of 33.54 07/07/12 23:35:06 v1.30 @ host ID: 1397 , Finished 30 curves using Lenstra ECM method on C109 input, B1 = 2K, B2 = gmp-ecm default 07/07/12 23:35:06 v1.30 @ host ID: 1397 , current ECM pretesting depth: 15.18 07/07/12 23:35:06 v1.30 @ host ID: 1397 , scheduled 74 curves at B1=11000 toward target pretesting depth of 33.54 07/07/12 23:35:22 v1.30 @ host ID: 1397 , Finished 74 curves using Lenstra ECM method on C109 input, B1 = 11K, B2 = gmp-ecm default 07/07/12 23:35:22 v1.30 @ host ID: 1397 , current ECM pretesting depth: 20.24 07/07/12 23:35:22 v1.30 @ host ID: 1397 , scheduled 214 curves at B1=50000 toward target pretesting depth of 33.54 07/07/12 23:37:04 v1.30 @ host ID: 1397 , Finished 214 curves using Lenstra ECM method on C109 input, B1 = 50K, B2 = gmp-ecm default 07/07/12 23:37:04 v1.30 @ host ID: 1397 , pp1: starting B1 = 1250K, B2 = gmp-ecm default on C109 07/07/12 23:37:09 v1.30 @ host ID: 1397 , pp1: starting B1 = 1250K, B2 = gmp-ecm default on C109 07/07/12 23:37:13 v1.30 @ host ID: 1397 , pp1: starting B1 = 1250K, B2 = gmp-ecm default on C109 07/07/12 23:37:18 v1.30 @ host ID: 1397 , pm1: starting B1 = 2500K, B2 = gmp-ecm default on C109 07/07/12 23:37:24 v1.30 @ host ID: 1397 , current ECM pretesting depth: 25.33 07/07/12 23:37:24 v1.30 @ host ID: 1397 , scheduled 430 curves at B1=250000 toward target pretesting depth of 33.54 07/07/12 23:49:58 v1.30 @ host ID: 1397 , Finished 430 curves using Lenstra ECM method on C109 input, B1 = 250K, B2 = gmp-ecm default 07/07/12 23:49:58 v1.30 @ host ID: 1397 , pp1: starting B1 = 5M, B2 = gmp-ecm default on C109 07/07/12 23:50:16 v1.30 @ host ID: 1397 , pp1: starting B1 = 5M, B2 = gmp-ecm default on C109 07/07/12 23:50:33 v1.30 @ host ID: 1397 , pp1: starting B1 = 5M, B2 = gmp-ecm default on C109 07/07/12 23:50:51 v1.30 @ host ID: 1397 , pm1: starting B1 = 10M, B2 = gmp-ecm default on C109 07/07/12 23:51:19 v1.30 @ host ID: 1397 , current ECM pretesting depth: 30.45 07/07/12 23:51:19 v1.30 @ host ID: 1397 , scheduled 559 curves at B1=1000000 toward target pretesting depth of 33.54 07/08/12 01:56:09 v1.30 @ host ID: 1397 , Finished 560 curves using Lenstra ECM method on C109 input, B1 = 1M, B2 = gmp-ecm default 07/08/12 01:56:09 v1.30 @ host ID: 1397 , final ECM pretested depth: 33.55 07/08/12 01:56:09 v1.30 @ host ID: 1397 , scheduler: switching to sieve method 07/08/12 01:56:09 v1.30 @ host ID: 1397 , nfs: commencing gnfs on c109: 8938861779072390809014308542579704644988289566455519966972540828521729483117056503398097479159550310460743973 07/08/12 01:56:09 v1.30 @ host ID: 1397 , nfs: commencing poly selection with 2 threads 07/08/12 01:56:09 v1.30 @ host ID: 1397 , nfs: setting deadline of 1641 seconds 07/08/12 02:22:36 v1.30 @ host ID: 1397 , nfs: completed 14 ranges of size 250 in 1587.4484 seconds 07/08/12 02:22:36 v1.30 @ host ID: 1397 , nfs: best poly = # norm 5.590786e-015 alpha -4.665071 e 3.341e-009 rroots 4 07/08/12 02:22:36 v1.30 @ host ID: 1397 , nfs: commencing lattice sieving with 2 threads 07/08/12 03:15:33 v1.30 @ host ID: 1397 , nfs: commencing lattice sieving with 2 threads 07/08/12 05:26:45 v1.30 @ host ID: 1397 , nfs: commencing lattice sieving with 2 threads 07/08/12 06:19:52 v1.30 @ host ID: 1397 , nfs: commencing lattice sieving with 2 threads 07/08/12 07:37:05 v1.30 @ host ID: 1397 , nfs: commencing lattice sieving with 2 threads 07/08/12 14:36:32 v1.30 @ host ID: 1397 , nfs: commencing msieve filtering 07/08/12 14:38:21 v1.30 @ host ID: 1397 , nfs: commencing lattice sieving with 2 threads 07/08/12 21:27:12 v1.30 @ host ID: 1397 , 07/08/12 21:27:12 v1.30 @ host ID: 1397 , ************************ 07/08/12 21:27:12 v1.30 @ host ID: 1397 , Starting factorization of 8938861779072390809014308542579704644988289566455519966972540828521729483117056503398097479159550310460743973 07/08/12 21:27:12 v1.30 @ host ID: 1397 , using pretesting plan: normal 07/08/12 21:27:12 v1.30 @ host ID: 1397 , no tune info: using qs/gnfs crossover of 95 digits 07/08/12 21:27:12 v1.30 @ host ID: 1397 , ************************** 07/08/12 21:27:12 v1.30 @ host ID: 1397 , pp1: starting B1 = 20K, B2 = gmp-ecm default on C109 07/08/12 21:27:12 v1.30 @ host ID: 1397 , pp1: starting B1 = 20K, B2 = gmp-ecm default on C109 07/08/12 21:27:12 v1.30 @ host ID: 1397 , pp1: starting B1 = 20K, B2 = gmp-ecm default on C109 07/08/12 21:27:12 v1.30 @ host ID: 1397 , pm1: starting B1 = 100K, B2 = gmp-ecm default on C109 07/08/12 21:27:13 v1.30 @ host ID: 1397 , current ECM pretesting depth: 0.00 07/08/12 21:27:13 v1.30 @ host ID: 1397 , scheduled 30 curves at B1=2000 toward target pretesting depth of 33.54 07/08/12 21:27:14 v1.30 @ host ID: 1397 , Finished 30 curves using Lenstra ECM method on C109 input, B1 = 2K, B2 = gmp-ecm default 07/08/12 21:27:14 v1.30 @ host ID: 1397 , current ECM pretesting depth: 15.18 07/08/12 21:27:14 v1.30 @ host ID: 1397 , scheduled 74 curves at B1=11000 toward target pretesting depth of 33.54 07/08/12 21:27:30 v1.30 @ host ID: 1397 , Finished 74 curves using Lenstra ECM method on C109 input, B1 = 11K, B2 = gmp-ecm default 07/08/12 21:27:30 v1.30 @ host ID: 1397 , current ECM pretesting depth: 20.24 07/08/12 21:27:30 v1.30 @ host ID: 1397 , scheduled 214 curves at B1=50000 toward target pretesting depth of 33.54 07/08/12 21:29:10 v1.30 @ host ID: 1397 , Finished 214 curves using Lenstra ECM method on C109 input, B1 = 50K, B2 = gmp-ecm default 07/08/12 21:29:10 v1.30 @ host ID: 1397 , pp1: starting B1 = 1250K, B2 = gmp-ecm default on C109 07/08/12 21:29:15 v1.30 @ host ID: 1397 , pp1: starting B1 = 1250K, B2 = gmp-ecm default on C109 07/08/12 21:29:20 v1.30 @ host ID: 1397 , pp1: starting B1 = 1250K, B2 = gmp-ecm default on C109 07/08/12 21:29:24 v1.30 @ host ID: 1397 , pm1: starting B1 = 2500K, B2 = gmp-ecm default on C109 07/08/12 21:29:30 v1.30 @ host ID: 1397 , current ECM pretesting depth: 25.33 07/08/12 21:29:30 v1.30 @ host ID: 1397 , scheduled 430 curves at B1=250000 toward target pretesting depth of 33.54 07/08/12 21:41:58 v1.30 @ host ID: 1397 , Finished 430 curves using Lenstra ECM method on C109 input, B1 = 250K, B2 = gmp-ecm default 07/08/12 21:41:58 v1.30 @ host ID: 1397 , pp1: starting B1 = 5M, B2 = gmp-ecm default on C109 07/08/12 21:42:17 v1.30 @ host ID: 1397 , pp1: starting B1 = 5M, B2 = gmp-ecm default on C109 07/08/12 21:42:34 v1.30 @ host ID: 1397 , pp1: starting B1 = 5M, B2 = gmp-ecm default on C109 07/08/12 21:42:52 v1.30 @ host ID: 1397 , pm1: starting B1 = 10M, B2 = gmp-ecm default on C109 07/08/12 21:43:20 v1.30 @ host ID: 1397 , current ECM pretesting depth: 30.45 07/08/12 21:43:20 v1.30 @ host ID: 1397 , scheduled 559 curves at B1=1000000 toward target pretesting depth of 33.54 07/08/12 22:46:27 v1.30 @ host ID: 1397 , Finished 560 curves using Lenstra ECM method on C109 input, B1 = 1M, B2 = gmp-ecm default 07/08/12 22:46:27 v1.30 @ host ID: 1397 , final ECM pretested depth: 33.55 07/08/12 22:46:27 v1.30 @ host ID: 1397 , scheduler: switching to sieve method 07/08/12 22:46:27 v1.30 @ host ID: 1397 , nfs: commencing gnfs on c109: 8938861779072390809014308542579704644988289566455519966972540828521729483117056503398097479159550310460743973 07/08/12 22:46:27 v1.30 @ host ID: 1397 , nfs: commencing NFS restart 07/08/12 22:46:27 v1.30 @ host ID: 1397 , nfs: previous data file found - commencing search for last special-q 07/08/12 22:46:38 v1.30 @ host ID: 1397 , nfs: parsing special-q 07/08/12 22:46:38 v1.30 @ host ID: 1397 , nfs: found 4689644 relations, continuing job at specialq = 1980301 07/08/12 22:46:38 v1.30 @ host ID: 1397 , nfs: commencing msieve filtering
22) Message boards : Number crunching : Too Late To Validate (Message 457) Posted 19 Jul 2012 by Matthias Lehmkuhl Post: had today again a not more known WU by the server http://yafu.dyndns.org/yafu/results.php?hostid=1398 43755 yafu 19.07.2012 12:37:22 Sending scheduler request: Requested by project. 43756 yafu 19.07.2012 12:37:22 Not reporting or requesting tasks 43757 yafu 19.07.2012 12:37:24 Scheduler request completed 43758 yafu 19.07.2012 12:37:24 Result yafu_C111_1342495527_6_0 is no longer usable 43759 yafu 19.07.2012 12:37:25 Computation for task yafu_C111_1342495527_6_0 finished The Deadline was round 10 o'clock today. Normally these should not happen so fast. The WU isn't visible on the host. As the message says. Yoyo, did you change something?
23) Message boards : News : wrapper update (Message 444) Posted 11 Jul 2012 by Matthias Lehmkuhl Post: Hello Yoyo, reset does it. The WU runs without error. Now the newer wrapper is downloaded . http://yafu.dyndns.org/yafu/result.php?resultid=767043
24) Message boards : Number crunching : Long running work units (Message 441) Posted 11 Jul 2012 by Matthias Lehmkuhl Post: Will it help, if I send you the 3 Log-files (factor.log, ggnfs.log, nfs.log)? From these I made a copy before reseting the project. Sorry, was a little bit to early yesterday :(
25) Message boards : News : wrapper update (Message 440) Posted 11 Jul 2012 by Matthias Lehmkuhl Post: OK I'll do it and check the filesize. But first I need to finish my WU that is in work with the old wrapper.
26) Message boards : News : wrapper update (Message 437) Posted 11 Jul 2012 by Matthias Lehmkuhl Post: Thanks yoyo, had the same problem. (Ubuntu 11.10) with the old version it's working again. Hello Yoyo, got the same error again. <core_client_version>6.12.33</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255) </message> <stderr_txt> ../../projects/yafu.dyndns.org_yafu/yafuwrapper_25825_x86_64-linux-gnu: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ../../projects/yafu.dyndns.org_yafu/yafuwrapper_25825_x86_64-linux-gnu) </stderr_txt> ]]> The new version is again active. Linux running on an AMD x86_64 or Intel EM64T CPU 130.03 (mt) 10 Jul 2012 \| 22:43:08 UTC
27) Message boards : Number crunching : How much crunching left? (Message 435) Posted 10 Jul 2012 by Matthias Lehmkuhl Post: Got my first 2 C110 results, one was a short runner.
28) Message boards : Number crunching : Long running work units (Message 434) Posted 10 Jul 2012 by Matthias Lehmkuhl Post: Had a very long running result. Did cancel it today after 1 day without updating the log files or other files. http://yafu.dyndns.org/yafu/result.php?resultid=752333 Looks like it did not survive the d**** "no heartbeat" on Sunday 08.07.2012. 17:50:19 (2904): No heartbeat from core client for 30 sec - exiting
29) Message boards : News : wrapper update (Message 427) Posted 8 Jul 2012 by Matthias Lehmkuhl Post: Thanks yoyo, had the same problem. (Ubuntu 11.10) with the old version it's working again.
30) Message boards : Number crunching : long cpu times (Message 381) Posted 15 Mar 2012 by Matthias Lehmkuhl Post: I have the same http://yafu.dyndns.org/yafu/forum_thread.php?id=87&nowrap=true#376 only on my Win x86 system and when the result stops calculation early. runtime round 2000 sec. http://yafu.dyndns.org/yafu/results.php?hostid=1397 for calculation is running over full time, the CPU Time value is shown in a normal way. Or only some result have this behavior on Win x86 systems.
31) Message boards : Number crunching : app reporting negative CPU (Message 376) Posted 8 Mar 2012 by Matthias Lehmkuhl Post: Have the same on my Win 32bit system 5261 yafu 08.03.2012 08:50:12 app reporting negative CPU: -1.000000 5262 yafu 08.03.2012 08:50:13 app reporting negative CPU: -1.000000 5263 yafu 08.03.2012 08:50:15 app reporting negative CPU: -1.000000 5264 yafu 08.03.2012 08:50:16 app reporting negative CPU: -1.000000 5265 yafu 08.03.2012 08:50:17 app reporting negative CPU: -1.000000 5266 yafu 08.03.2012 08:50:19 app reporting negative CPU: -1.000000 5267 yafu 08.03.2012 08:50:21 app reporting negative CPU: -1.000000 (Source BoincTasks 1.30) and additional the CPU time from this Clients http://yafu.dyndns.org/yafu/show_host_detail.php?hostid=1397 looks odd: 49,608,850,000,000,002,062,079,553,705,230,327,939,012,244,050,246,630,076,053,444,726,129,259,448,365,759,310,372,025,402,006,571,171,104,113,704,985,190,252,068,262,607,526,028,929,981,786,202,945,530,141,718,177,165,791,531,672,456,687,243,103,819,024,234,355,563,543,094,541,295,064,874,358,731,130,323,253,196,581,666,553,856.00 I've seen this only for the 32Bit App YAFU v130.02 (mt) The results are validated with credit. Edit: the shown runtime is normal.
32) Message boards : Number crunching : Server Out Of Disk Space (Message 228) Posted 20 Oct 2011 by Matthias Lehmkuhl Post: Upload works for me now http://yafu.dyndns.org/yafu/result.php?resultid=412016 result is uploaded an reported.
33) Message boards : Number crunching : WU's at 100% for hours (Message 221) Posted 20 Oct 2011 by Matthias Lehmkuhl Post: You see that the progress is still 0%. These WUs are C103 which will need (depending on your hardware) up to 10h-14h. I heard already from other users that they were running WUs up to 24h. But at the end they finished and validated. yoyo From my viewing the Problem is the remaining time with "---". Here the boinc client doesn't see, that the result has not finished yet. When I had a result with a long running time, than this behavior will appear very late, so most of the results have finished before time is decreased to "---". The start time for Elapsed will increase to the maximum time I had on that machine.
34) Message boards : Number crunching : WU's at 100% for hours (Message 220) Posted 20 Oct 2011 by Matthias Lehmkuhl Post: I got credit for a result after deadline, as long as the result is visible. Maybe I'm wrong, by reviewing my results, I found no sample. But also I had long runners, that finished more than 24 hours after deadline, where I got no credit. These where deleted on server side before I could upload and report them.
35) Message boards : Number crunching : Too Late To Validate (Message 204) Posted 13 Oct 2011 by Matthias Lehmkuhl Post: Hi Yoyo, Result shows sometimes 100% Progress when yafu is finished and gnfs-lasieve should run. Boinc ignores the deadline for e.g. "high priority mode", when the result is at 100% progress and not finished yet. http://yafu.dyndns.org/yafu/result.php?resultid=349690 Project: yafu Application: 128.06 YAFU Result name: yafu_C101_1318234240_115_0 elapsed time: 13:03:35 (04:32:33) Progress: 100,000 Remaining time: - Deadline: 12.10.2011 13:44:34 Is it possible to reach 100% progress only when the result is ready for uploading?

Previous 20