| log in |
|
21)
Message boards :
Number crunching :
What causes this error message...
(Message 5464)
Posted 26 Sep 2019 by Dr Who Fan What causes the error message highlighted in RED below and should I continue or abort task? Task has been running for about 3.5 hours and estimated to run about 28.25 hours total based on whats been completed. Application: Sierpinski / Riesel Base - average3 0.22 Name: S789_350-400k_wu_1863_1 Info from the stderr.txt file in the slots directory: 20:48:12 (5792): wrapper (7.5.26012): starting 20:48:12 (5792): wrapper: running llr.exe ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999) Base factorized as : 3*263 Base prime factor(s) taken : 263 Starting N-1 prime test of 96*789^367162+1 Using all-complex AMD K8 FFT length 480K, Pass1=384, Pass2=1280, a = 3 Iter: 1/3533521, ERROR: ROUND OFF (0.4995842595) > 0.4 Continuing from last save file. Starting N-1 prime test of 96*789^367162+1 Using all-complex AMD K8 FFT length 480K, Pass1=384, Pass2=1280, a = 3 Iter: 1/3533521, ERROR: ROUND OFF (0.4995842595) > 0.4 Unrecoverable error, Restarting with next larger FFT length... Continuing from last save file. Starting N-1 prime test of 96*789^367162+1 Using all-complex AMD K8 FFT length 512K, Pass1=512, Pass2=1K, a = 3 96*789^367162+1, bit: 50000 / 3533521 [1.41%]. Time per bit: 28.756 ms. 96*789^367162+1, bit: 100000 / 3533521 [2.83%]. Time per bit: 28.391 ms. 96*789^367162+1, bit: 150000 / 3533521 [4.24%]. Time per bit: 28.861 ms. 96*789^367162+1, bit: 200000 / 3533521 [5.66%]. Time per bit: 28.475 ms. 96*789^367162+1, bit: 250000 / 3533521 [7.07%]. Time per bit: 28.199 ms. 96*789^367162+1, bit: 300000 / 3533521 [8.49%]. Time per bit: 28.728 ms. 96*789^367162+1, bit: 350000 / 3533521 [9.90%]. Time per bit: 29.261 ms. 96*789^367162+1, bit: 400000 / 3533521 [11.32%]. Time per bit: 32.842 ms. ******* I had a task http://srbase.my-firewall.org/sr5/result.php?resultid=379954726 that ran to completion but was marked invalid with similar error messages. |
|
22)
Message boards :
Number crunching :
must be a bad data file
(Message 5062)
Posted 21 Mar 2019 by Dr Who Fan So far two PC'S including mine have errored out this task http://srbase.my-firewall.org/sr5/workunit.php?wuid=359622416 |
|
23)
Message boards :
Number crunching :
Web site is VERY SLOW to load & CANNOT UPLOAD completed work
(Message 4602)
Posted 18 Sep 2018 by Dr Who Fan For past 30 to 40 minutes Web site has been VERY SLOW to load or unreachable. Also having problems UPLOAD completed work - keep getting error/back-off messages. Seems a bit better suddenly as I am typing but web site is still sluggish to respond. |
|
24)
Message boards :
Number crunching :
computation errors
(Message 3854)
Posted 25 Sep 2017 by Dr Who Fan UPDATE >> Appears the problems I am having are related to Universe@home corrupting ALL BOINC projects for some reason... Did a RESET on BOTH SR5 & Universe with tasks still failing. Uninstalled & reinstalled the two projects with same results. Finally suspended & set No New Work for Universe & everything started working fine again on SR5. |
|
25)
Message boards :
Number crunching :
computation errors
(Message 3853)
Posted 25 Sep 2017 by Dr Who Fan Had 2 in a ROW now that FAILED the same way... but the stderr rpt says "application BHspin2 missing" Link to tasks: 261966891 & 261955442 Stderr output |
|
26)
Message boards :
Number crunching :
Slot directory error
(Message 2475)
Posted 12 Apr 2016 by Dr Who Fan [error] exceeded limit of 1800 slot directories This is MOST LIKELY a BOINC error not a SRBase project error. I believe you will find a solution here: https://boinc.berkeley.edu/dev/forum_thread.php?id=10560&postid=64881 If possible update to a later BOINC version. 7.6.11 has a fix: |
|
27)
Message boards :
Number crunching :
Problem with Riesel Base Short on Dual-Xeon
(Message 1657)
Posted 14 Jul 2015 by Dr Who Fan This problem sounds a bit similar to what they have been discussing over at SETI and Milkyway in the Number Crunching forums. SETI is down for it's usual weekly maintenance but I found the topic at Milkyway. Richard Haselgrove posted this at Milkyway > Message 63799 in Message boards : Number crunching : What is the cause of these 'validate errors' < "After intensive work with Keith Myers and others (mainly in the SETI message board thread Stderr Truncations), I think I've finally traced and recorded the full life-cycle of these little beasties. |
|
28)
Message boards :
Number crunching :
Scheduler request failed: HTTP file not found
(Message 1609)
Posted 29 Jun 2015 by Dr Who Fan Hmm, perhaps you have reached the max WUs in progress and the limit of your connections (upload/download). Also if you only running small WUs (7-12s) the server cannot send out enough WUs per RPC request. Error message still showing up on just about every work request in BOINC log. Last one about 10 minutes ago. My settings for Host ID 102 are Minimum Work Buffer: 0.05 / Additional Work Buffer: 0.00. Task settings:
Riesel Base: no Sierpinski Base: no Sierpinski / Riesel Base - short: yes Sierpinski / Riesel Base - long: no Sierpinski / Riesel Base - average: yes Riesel Base - short: yes Sierpinski Base - short: yes Sierpinski / Riesel Base - average2: no Sierpinski / Riesel Base - average3: no
|
|
29)
Message boards :
Number crunching :
Scheduler request failed: HTTP file not found
(Message 1607)
Posted 29 Jun 2015 by Dr Who Fan I am not always getting new tasks sent when requesting more work. Receiving error message: Scheduler request failed: HTTP file not found Here is one instance from the BOINC log. Times noted below are UTC -5.00 Hrs). 6/29/2015 2:18:18 PM | SRBase | Sending scheduler request: To fetch work. |
|
30)
Message boards :
Number crunching :
TOP5000 entries
(Message 526)
Posted 5 Jan 2015 by Dr Who Fan +1 with Conan, vaughan, DerekL & al@ON. |
|
31)
Message boards :
Number crunching :
Work available??
(Message 427)
Posted 2 Jan 2015 by Dr Who Fan What happens is that when work dries up, people don't detach or set NNT - they just open up other projects and wait patiently for work to magically appear. This is what the majority of people do - set and leave. Exactly. Anyway, it's clear that people are content with the way Reb is running HIS project because every batch sells out. A BIG THANK YOU goes out to Reb for a very smooth running run project --- and the--- "cliff notes" he posts for us all to follow along with the progress! |