- Dec 11, 1999
- 16,357
- 4,052
- 75
ODLK1
BOINC-project ODLK1 continues to solve the problem of BOINC-project ODLK.
The project generates a database of canonical forms (CF) of diagonal Latin squares (DLS) of order 10 having orthogonal diagonal Latin squares (ODLS).
Jan. 2018, Working Project. CPU Only. Windows, Linux and FreeBSD.
Have you tried different isp? I once had similar problem across different projects and switching the isp (land cable isp to mobile phone) would do the trick.aw p00p! I haven't been able to connect to that in two months. It just times out everytime.
This may wind up being as bad as the MOD_PYTHON project.Half an hour ago the web site was slow, now it is completely DDoS'd.
I can't get to the web site either. Adding project in boinc manager times out.
Have you tried different isp? I once had similar problem across different projects and switching the isp (land cable isp to mobile phone) would do the trick.
I try using my mobile browser and it's still down. So, as Stefan said, it's DDoS'd.Alas, that's not an option.
It took me about two hours to create my own account (i.e.: add it in the first host via boincmgr, set nickname + team affiliation + basic preferences in the web interface).Adding project in boinc manager times out.
I hate this MOD_PYTHON project. When it's selected it's always ERRORing out.
via Google translate:Sébastien at the LAF forum said:Le tirage au sort du projet n'est pas totalement aléatoire. Cela nécessite une action manuelle pour la validation du projet.
Ces temps-ci, j'ai tendance à oublier de valider.
It works, if you shut down the client on the target machine and edit all relevant lines into client_state.xml, then restart the client. I haven't done this with ODLK1, but with other projects on two or three occasions. (This requires same machine architecture of course.)I don't suppose it works to copy the bigger files from one machine to another?
One PC which I added maybe 5 hours ago is still struggling to download the large (not) exe files. This PC is away from the others, and it's late night here now, otherwise I would perform the sneakernet transaction now which Ken asked about.It takes a lot of effort but I'm getting there.
Though without uploads, I have nothing to go on what's happening. Except two things: (a) The error'ed tasks have the same elapsed time as successfully completed tasks. (b) Task state goes from running to 100 % -> aborted -> computation error. So perhaps this is the type of boinc bug with a race condition between execution finish and writing of the output files.
I completed a number of tasks by now. And while all looks well on a Linux Xeon E3v3 so far, I get a high fraction of computation errors on Linux single-socket and dual-socket Xeon E5v4. [...] perhaps this is the type of boinc bug with a race condition between execution finish and writing of the output files.
Thanks. It's the familiar error:You can open client_state.xml in notepad++ and scroll through that file to find those WUs, can you search by WU name to see status, in the xml it will have the stdout and that should tell you whats going on
<stderr_out>
<![CDATA[
<message>
finish file present too long
</message>
<stderr_txt>
21:02:20 (6393): called boinc_finish(0)
</stderr_txt>
]]>
</stderr_out>