Posts by Matthias Lehmkuhl

1) Message boards : Number crunching : When should a "stalled" task be aborted? (Message 1457)
Posted 25 Nov 2019 by Matthias Lehmkuhl
Post:
Hello,
I too have a result that looks like running forever
yafu_ali_2145600_L131_C124_1571470508_8_5
https://yafu.myfirewall.org/yafu/result.php?resultid=5325104

the result is running with one gnfs-lasieve4I13e.exe (one CPU) now at 114 hours

The first result was started at 19.10.2019, an no result finished so far.
2) Message boards : Number crunching : Too many total results (Message 647)
Posted 19 Mar 2014 by Matthias Lehmkuhl
Post:
I found a result marked as
errors Too many total results

http://yafu.dyndns.org/yafu/workunit.php?wuid=32617

Maybe it depends on the not meet deadline
Report deadline 18 Mar 2014, 22:16:56 UTC
Received 19 Mar 2014, 1:47:17 UTC

And I got credit for my result.
But it looks strange.

The boinc client (7.2.42) did not start the result near the/after deadline automatically, the progress time was over. But the result wasn't finished.
I'm using BoincTasks, so the view is a bit different.

Edit: add Boinc Client Version
3) Message boards : News : project shutdown (Message 589)
Posted 10 Sep 2013 by Matthias Lehmkuhl
Post:
Have a good time and trip :D
4) Message boards : News : Next level, C114, reached (Message 559)
Posted 11 Jun 2013 by Matthias Lehmkuhl
Post:
Core(TM) i5 @ 3.20GHz
Anzahl der Prozessoren 4

runtime
C113 = 31,684.50 sec
C114 = 35,582.69 sec
5) Message boards : Number crunching : Too Late To Validate (Message 491)
Posted 10 Oct 2012 by Matthias Lehmkuhl
Post:
I changed the timing of purging the wu from DB. Maybe this helps.
yoyo


Hi Yoyo,
looks good now, I was able to upload results after the deadline.

http://yafu.dyndns.org/yafu/result.php?resultid=916924
Empfangen 2 Oct 2012 | 19:39:55 UTC
Ablaufdatum 2 Oct 2012 | 17:37:57 UTC

http://yafu.dyndns.org/yafu/result.php?resultid=905084
Empfangen 28 Sep 2012 | 23:42:15 UTC
Ablaufdatum 28 Sep 2012 | 23:08:21 UTC
6) Message boards : Number crunching : Too Late To Validate (Message 488)
Posted 21 Sep 2012 by Matthias Lehmkuhl
Post:
I assume, that the Boinc server deletes the workunit because of my setting <delete_delay_hours>24</delete_delay_hours>. So the setting of <report_grace_period>240</report_grace_period> is ignored.

I changed now the delete_delay_hours to 240 h. This should improve the issue now.

yoyo

Hi Yoyo,
The problem is ongoing, got again one result that was canceled by the Server:
The WU is no more visible on the server.
yafu 18.09.2012 22:23:08 Restarting task yafu_C108_1347903921_236_0 using yafu version 13201
yafu 19.09.2012 00:06:22 Resuming task yafu_C108_1347903921_236_0 using yafu version 13201
yafu 19.09.2012 03:45:28 Resuming task yafu_C108_1347903921_236_0 using yafu version 13201
yafu 19.09.2012 17:34:52 Resuming task yafu_C108_1347903921_236_0 using yafu version 13201
yafu 20.09.2012 08:57:40 Result yafu_C108_1347903921_236_0 is no longer usable
yafu 20.09.2012 08:57:41 Computation for task yafu_C108_1347903921_236_0 finished
yafu 20.09.2012 08:57:51 Sending scheduler request: To report completed tasks.
yafu 132.01 YAFU (mt) yafu_C108_1347903921_236_0 15:40:06 (01:12:33) 20.09.2012 08:57:45 20.09.2012 08:59:46 2,00C 3,86 Durch Projekt abgebrochen
7) Message boards : Number crunching : Too Late To Validate (Message 483)
Posted 16 Aug 2012 by Matthias Lehmkuhl
Post:
I assume, that the Boinc server deletes the workunit because of my setting <delete_delay_hours>24</delete_delay_hours>. So the setting of <report_grace_period>240</report_grace_period> is ignored.

I changed now the delete_delay_hours to 240 h. This should improve the issue now.

yoyo

Hi Yoyo,
looks like it does not work as expected.
The result is no more visible in the tasks of the host.
http://yafu.dyndns.org/yafu/results.php?hostid=1397
Did not make a copy of the link to the result, so only a copy of the messages.
The deadline of the result was round 0:30 UTC

30356 yafu 15.08.2012 23:17:24 Sending scheduler request: Requested by project.
30357 yafu 15.08.2012 23:17:24 Not reporting or requesting tasks
30358 yafu 15.08.2012 23:17:27 Scheduler request completed
30514 yafu 16.08.2012 04:17:32 Sending scheduler request: Requested by project.
30515 yafu 16.08.2012 04:17:32 Not reporting or requesting tasks
30516 yafu 16.08.2012 04:17:35 Scheduler request completed
30517 yafu 16.08.2012 04:17:35 Result yafu_C108_1344851412_387_0 is no longer usable
30518 yafu 16.08.2012 04:17:36 Computation for task yafu_C108_1344851412_387_0 finished
30519 yafu 16.08.2012 04:17:45 Sending scheduler request: To report completed tasks.
30520 yafu 16.08.2012 04:17:45 Reporting 1 completed tasks, not requesting new tasks
30521 yafu 16.08.2012 04:17:49 Scheduler request completed
8) Message boards : News : C112 reached (Message 479)
Posted 3 Aug 2012 by Matthias Lehmkuhl
Post:
It`s no problem for me when you use several cores for the project, but Yafu stops all GPU applications immediately. Sry, unacceptable.


This problem is solved with boinc core client 7.0.31

"Ein Hinweis für Nutzer der neuesten BOINC-Versionen (7.0.2x): Aufgrund eines BOINC-Bugs ist es nicht möglich, gleichzeitig Multithread-WUs (z.B. eben YAFU) und GPU-WUs anderer Projekte laufen zu lassen. Sobald in diesen BOINC-Versionen eine Multithread-WU gestartet wird, werden sämtliche GPU-WUs angehalten. Das Problem ist in BOINC 7.0.31 behoben."
from Seti-Germany forum
http://www.seti-germany.de/forum/das-hauptforum/6331-teamwork-2012-gemeinsam-bewegen-speg-2nd-wave-bei-yafu.html#post221955
9) Message boards : News : C113 reached (Message 478)
Posted 3 Aug 2012 by Matthias Lehmkuhl
Post:
yafu 132.01 YAFU (mt) yafu_C113_1343505628_364_0 12:13:12 (02:42:12) 31.07.2012 04:59:55 31.07.2012 05:01:02 2,00C Gemeldet: OK *
yafu 132.01 YAFU (mt) yafu_C111_1342844413_415_0 11:01:09 (02:28:01) 21.07.2012 23:23:55 21.07.2012 23:24:25 2,00C Gemeldet: OK *

runtime (CPU time) is marked red

on Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2 Prozessoren)
10) Message boards : Number crunching : Too Late To Validate (Message 476)
Posted 31 Jul 2012 by Matthias Lehmkuhl
Post:

here is eventually the next
http://yafu.dyndns.org/yafu/result.php?resultid=810109
deadline 31 Jul 2012 | 17:13:19 UTC
yafu_C113_1343505628_468_0


Got it, finished right before the deadline at 31 Jul 2012 | 17:01:16 UTC
11) Message boards : Number crunching : Too Late To Validate (Message 475)
Posted 31 Jul 2012 by Matthias Lehmkuhl
Post:
According to my settings you should have 10 days time to report the wu after the deadline. Lets see what happens.

yoyo


Hi yoyo,
the result is deleted on server side.
1365 yafu 31.07.2012 17:54:21 Result yafu_C113_1343505628_370_0 is no longer usable
1366 yafu 31.07.2012 17:54:23 Computation for task yafu_C113_1343505628_370_0 finished
1367 yafu 31.07.2012 17:54:23 Starting task yafu_C102_1343605809_130_0 using yafu version 13201 (mt) in slot 1
edit: "http://yafu.dyndns.org/yafu/result.php?resultid=810011
Shows: Verarbeitung der Anfrage nicht möglich"

here is eventually the next
http://yafu.dyndns.org/yafu/result.php?resultid=810109
deadline 31 Jul 2012 | 17:13:19 UTC
yafu_C113_1343505628_468_0
12) Message boards : Number crunching : Too Late To Validate (Message 473)
Posted 31 Jul 2012 by Matthias Lehmkuhl
Post:
Hi Yoyo,
I think this is the next one where I'm not able to meet the deadline.
http://yafu.dyndns.org/yafu/result.php?resultid=810011
yafu_C113_1343505628_370_0
After 12 hours runtime, it has done only 4 times "nfs: commencing lattice sieving with 2 threads"
I need to hibernate the computer till near the deadline 31 Jul 2012 | 15:16:12 UTC
13) Message boards : Number crunching : Too Late To Validate (Message 464)
Posted 25 Jul 2012 by Matthias Lehmkuhl
Post:
Hi Yoyo,
got the next one:
24-Jul-2012 23:03:19 [yafu] Starting task yafu_C111_1342991414_32_0 using yafu version 13201 (mt) in slot 2
25-Jul-2012 17:47:41 [yafu] Restarting task yafu_C111_1342991414_32_0 using yafu version 13201 (mt) in slot 2
25-Jul-2012 17:47:54 [yafu] Sending scheduler request: Requested by project.
25-Jul-2012 17:47:54 [yafu] Not requesting tasks: project is not highest priority
25-Jul-2012 17:48:02 [yafu] Scheduler request completed
25-Jul-2012 17:48:02 [yafu] Result yafu_C111_1342991414_32_0 is no longer usable
25-Jul-2012 17:48:04 [yafu] Computation for task yafu_C111_1342991414_32_0 finished
25-Jul-2012 17:48:17 [yafu] Sending scheduler request: To report completed tasks.
25-Jul-2012 17:48:17 [yafu] Reporting 1 completed tasks
25-Jul-2012 17:48:17 [yafu] Not requesting tasks: project is not highest priority
25-Jul-2012 17:48:23 [yafu] Scheduler request completed

The result was deleted on the server/my host immediately after the deadline
The deadline was between 08 and 09 o'clock today.
I've checked this today morning.
Forgot to save the link to the result/WU number.
14) Message boards : Number crunching : Too Late To Validate (Message 460)
Posted 19 Jul 2012 by Matthias Lehmkuhl
Post:
Was the workunit already running or not?
If it was not yet running it is ok to abort it after the deadline.
yoyo

The workunit was running, otherwise I had not posted this message. ;-)
43702 yafu 19.07.2012 09:11:14 Starting task yafu_C111_1342495527_6_0 using yafu version 13201
15) 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
16) 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?
17) 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
18) 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 :(
19) 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.
20) 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


Next 20




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