Posts by sorcrosc

1) Message boards : Bug tracker : Factorization '0' is incorrect: 0 is not a prime! (Message 1402)
Posted 15 May 2020 by sorcrosc
Post:
I removed the app_config.xml I was using to set the number of mt cores and let the settings from the site do the job. I don't know if this is related but I haven't had any problems since.
2) Message boards : Bug tracker : Factorization '0' is incorrect: 0 is not a prime! (Message 1400)
Posted 12 May 2020 by sorcrosc
Post:
I have a similar issue. Many workunits go up to 99%, then percentage drop to a very low value and stay there. If I suspend and resume, they end with error.
I checked amicable_checkpoint when percentage was 98 and after too. It says this:
0 0#


https://sech.me/boinc/Amicable/result.php?resultid=31448292
<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
Factorization '0' is incorrect: 0 is not a prime
SIGABRT: abort called
Stack trace (10 frames):
[0x437140]
[0x457be0]
[0x457ac9]
[0x52b2ea]
[0x405696]
[0x4067c0]
[0x4009a4]
[0x51ab66]
[0x51ad5a]
[0x426549]

Exiting...

</stderr_txt>
]]>
3) Message boards : News : Credits for the old application (search up to 2^64) doubled (Message 559)
Posted 4 Jul 2017 by sorcrosc
Post:
Hey, you are rewarding something like 50 20 times more than other projects. Why don't you think at lowering instead?
4) Message boards : Number crunching : Auto-ban faulty hosts (Message 485)
Posted 18 Jun 2017 by sorcrosc
Post:
Faulty hosts tend to fault in the same way (not finding amicable numbers at all), so if two faulty hosts meet on the same work unit, some numbers can be missed. Therefore I need to detect and disable such hosts as early as possible.


Thanks. I suggest to write this in the top post.

Do you think you can show in the workunit result page if there is some amicable number found?

I have disabled opencl on this computer (mesa package removed). Remaining opencl workunits aborted but one of them is ready to report and can't be aborted.
Please remove it from ban when possible. Thanks again.
5) Message boards : Number crunching : Auto-ban faulty hosts (Message 483)
Posted 18 Jun 2017 by sorcrosc
Post:
My host here has been banned:
https://sech.me/boinc/Amicable/show_host_detail.php?hostid=4574

I was testing my gpu in linux with mesa drivers. It was interesting because it's the first project I found to work with them. When I realized there were some failing workunits it was because I have seen the "Not accepting requests from this host" message, it was too late :)

Can you please explain the need for this banning? Isn't the validation mechanism enough for Amicable?


Thanks



©2020 Sergei Chernykh