User of the day

User profile Profile Soderstromm
Hello, i'm from Russia and i believe that science will help humanity! Let's be friends! P.S. Sorry for my 'barbarian' english :)

Project total CPU time equivalent to: 10562 years, 102 days, 5 hours of Athlon 3500+ running stock app.

Best scores for active workunits/batches:

m4_vroln72_1: score: 1908411  settings: B:CG:NRBP:G127:ABCGDZEXFHJQLRMTNVPYSU
rieboooergqjmkeinulgmoegnesachleiubengeaetunenfensseitendrengonifekmysyn found by Condor


The reason why work generator is stopped
I have stopped the work generator because IMO it does not make sense to continue the batch that runs with the original ("naval") dictionary set, where upgraded dictionary sets have already failed with similar number of target restarts.

IMO it's better to try with another dictionary set and tweaked app.
Both cases, however, require major upgrades on the server side - for performance reasons, I have removed some of the functionalities it originally had and now I have to add them back. It's going to take 2-4 weeks because my job leaves me very little spare time. I'm also going to clean the database from any leftovers, there are still over 20k workunits in the db, probably most of them are broken WUs that accumulated over time (at some point there was a sudden failure of SSD drive where the database filesystem is located, it was replaced by RAID5 setup with the data restored from backup, but ~4500 workunits/results ended in messed up state). I'll wait a few days and then all the orphaned workunits / results will be removed.

Also, all future (larger) batches will be split into a group of smaller sub-batches. While the batch is running, the server requires access to all the results that were returned and if the database gets to big, performance suffers. It also makes creating 'offline' backups harder due to the amount of data in the db dump.

In a few days I'll post downloadable results from the previous batches in case anyone wants to take a look.
19 Apr 2017, 23:04:21 UTC · Comment

Recent changes in account creation
As everyone may have already noticed, the project has been heavily hit by spammers. For the last weeks I've been fighting with up to 10k registrations per day, mostly just empty accounts which were created for unknown reasons (very few of them actually posted anything on forums or created profile/spam team).
I've been looking into possible ways to filter out the spammers right where they start (registration) and after looking at a few of possible solutions, I made a patch for the BOINC server to use StopForumSpam databases. For now, the server does not allow access to registration script from any IP listed in SFS db and it also refuses to create account with email address which is blacklisted there. This immediately filtered out more than 99,9% of new accounts, the rest is reviewed manually and eventually spammers that slipped through registration are reported back to the SFS.

There is also a daemon scriptwhich runs in background, randomly picking account and checking it against the blacklists, all accounts registered with blacklisted email address will be gone sooner or later together with any team and/or profile they have created (the script works very slowly, checking one account every few minutes, as I dont want to stress the SFS API which is a great free service).
The script won't touch anyone who has any credits or even hosts attached, so legitimate accounts should be safe even if someone has their email blacklisted.
24 Aug 2016, 12:44:25 UTC · Comment

Work generator paused
Recently the work generator has been paused because the server needs extended database maintenance (there is a significant amount of workunits stuck in unknown state, which affect performance).
I'm also running data analysis on all the results returned so far, the process eats a lot of resources so probably the work generator will remain stopped until the data analysis is done.
24 Aug 2016, 12:23:43 UTC · Comment

FNYG MXHU broken
Today around 02:30 GMT+2 ThrasherX-17 from team Keep The Fire Alive! returned the plaintext of 76 letters long FNYG MXHU message:


The message says:

Which translates to:

"[To] Control from Submarine Base Wilhelmshaven: Radio message 1224 solved with RHV"

If you'd like to know more about the context of this message, read Dan Girard's explanation
20 Jun 2013, 8:01:37 UTC · Comment

Planned maintenance on April 18th
The company which is hosting part of my server (download mirror, domain and a few other things) announced that my VPS will be moved to another location (datacenter) on 18th of April.
The IP address is going to be changed so I think the server will be unavailable for at least couple of hours, maybe up to a day.

6 Apr 2013, 19:45:41 UTC · Comment

... more

News is available as an RSS feed   RSS

Copyright © 2017 TJM