Rieselsieve

[Brucifer]

I'm moving my rieselsive stuff over to Free-DC. Some people there to crunch with.

[mitro]

So whats so great about this project that its worth giving the crunching power to another team? Sorry, I guess I'd rather change projects than teams if I was feeling lonely. :roll:

[NeoGen]

One does feel better crunching with company, I know it well. :roll:

(What I'm about to write is "word has it that..." knowledge, because I never even tried the project. Please forgive me and correct me if I'm saying something wrong.)
I think the reason why Riesel Sieve isn't as popular as 17-or-Bust for example is because it needs some looking after. You have to manually reserve the ranges to sieve, and once crunched you have to go there again and mark them as done. (is it ranges or k's? don't know if it's the same thing...)

Anyways, for a couple of times that I did just what you said there mitro, without even thinking about it.
We got a team on Cell Computing, of which I'm the only participant. I've stopped running it for some time. And I'm also the only one participating in Evolution@Home for our team since it was added to the stats. (Haven't touched it in months too) A much more complicated project to manage and babysit than Riesel Sieve. Got a few results to submit for Evolution here, gotta see if I turn them in before their next stats update!

Anyways... don't mind all that I wrote. I get carried away sometimes. :lol:
Conclusion, no one will tell you what to do, so do what your heart tells ya 72CJ5. And don't stop coming by! :)

[NVM]

i only see about 3 posts a day here,at least in the last week. i find that amazing with the amount of your team members.

[Brucifer]

So whats so great about this project that its worth giving the crunching power to another team? Sorry, I guess I'd rather change projects than teams if I was feeling lonely. :roll:


Well since you ask.... :) My home base anyway is Free-DC. Some stuff I crunch there and other stuff I crunch other places. That's one of the things about Free-DC, you are free to crunch what you want, where you want. But as Neo mentioned, it gets rather boring crunching alone, or in this case sieving.

As for what's so great about the project? Well Lee Stephens is a friend, and I've been working at his project off and on. And yes, there are some semi-automated portions in sieving, but unlike the LLRNET, sieving doesn't run on autopilot. And sob is like that too,.. it has it's autopilot mode, and there is also sieving there, which you do a lot by hand. So in the grand scheme of crunching projects, it is a small project, with a very limited appeal, as most math related projects are.

So in the long and short of it all, if people are crunching something here that they aren't on FDC, then I crunch it here, and vice versa. Due to the small size of the project, the stats basically just tract what people do, and are not to the point like the boinc world or distributed.net in that the points remain with the team whether you stay or leave.

[NeoGen]

That's one of the things about Free-DC, you are free to crunch what you want, where you want.

I'll just add a small comment to all our recent new members that have been joining the Team in the last few days. (according to Ototero's report)
AMD Users is also a free Team. :cool:
Everyone's welcome in the forums, even if you don't crunch for us at all. :)

May the admins and the more ancient members of the Team correct me if that is not the spirit of this Team! :P

[Ototero]

As NVM says, we have huge numbers of crunchers, but very few want to post here.

But we do exist to crunch not to chat. The chatting is just a bonus. :D

[vaughan]

I'm afraid I have to admit that I don't really understand sieving. Last week I downloaded and installed what I think are the required elements for Rieselsieve. I got a 5 unit (I think its 5G?) reserved and ran Rieselator on a borged Athlon XP-M 2400. The 5G took approximately 18 hours to process and in the end there were no factors found. Consequently I had nothing to show for the time expended.

What was weird is that most other participants got at least 1 factor in a 5G run. I thought maybe I'm doing something wrong so I switched this PC back to SOB.

Sorry to see you leave us in RieselSieve 72CJ5 but as Neo observed you are free to crunch whatever and wherever you want in AMD Users.

[mitro]

Well... OK then... I got my answer and it was acceptable. :P

[Brucifer]

I'm afraid I have to admit that I don't really understand sieving. Last week I downloaded and installed what I think are the required elements for Rieselsieve. I got a 5 unit (I think its 5G?) reserved and ran Rieselator on a borged Athlon XP-M 2400. The 5G took approximately 18 hours to process and in the end there were no factors found. Consequently I had nothing to show for the time expended.


It's entirely possible that you wouldn't have found one factor, but usually there's at least one. But you brought up one of the main problems that a lot of people don't spend time crunching on math projects.... and that is that really, except in a few cases, there really isn't much to show for the work you put into the project. In Rosetta, or the greatest majority of the boinc and other projects, everyone is crunching on the main banana. Each work unit is a part of the big picture. That isn't so with the math projects, at least to the point that the person in the street can see much of anything. While you didn't end up with any points in you 5G block Vaughn, you did eliminate a 5G block of numbers that didn't have to be crunched by LLR in a slow, long process. The only purpose of the sieving is to eliminate blacks of invalid factor candidates, so that the LLR process only needs to be run on a selected group of prospective factors. Athlons excel at sieving. P4's excel at running LLR.

And the siever doesn't get the glory. The individual running the LLR program that finds a prime is the one that gets the glory. In reality though, he/she more than likely wouldn't have found it without the aid of sieving. It's ike the race car driver gets all the glory, but the driver wouldn't be there without all the people behind the scenes.

[Brucifer]

It's all a rather moot point anyway.... the rieselsieve system isn't letting me change my team.

[AMDave]

Members Leaving Today
Brucifer departed to Free-DC
...he went that-a-way. :arrow:

nice crunchin' with ye.

I have the jersey.
Ooopla!
Here's the hill climb again :shock:

[bryanRS]

72CJ5 - Is the page giving you an error? Just not taking the team change? I'll look into the problem if you can give me some more info - I'd really like to have any bugs stomped out.

Ok, actually if you wouldn't mind checking it now. I played around with it a bit myself (since I don't change teams very often, I don't test the function often), and found that there was an if/else statement cancelling itself out and resorting to the session-stored TeamID for the FIRST time you try to change it, but then the chosen value the SECOND time it is changed. Looks like things work right now. Please let me know if I'm right, or still a fool :)

Bryan

Stats Administrator
RieselSieve Project

[AMDave]

Hi bryan :D

looks like you fixed it
according to the stats extract file Brucifer is now Free-DC
hence my post above
the quote is extracted from bok's stats pages and he's building from the extract file

Your project stats page at "teams.php?tid=8" also shows the same.

[Brucifer]

Bryan -- I shot a email to Lee, and he changed the stuff for me. So I haven't tried your revamped script.. -- Bruce

[Brucifer]

I just got off the rieselsieve site, and they are now looking at reviewing the team stats issue so that stuff crunched while a member of a team would stay with the team after a member moved. If you have input on this, go to the rieselsieve site and post your ten cents, or whatever it is. :)

Bruce

[AMDave]

Posted by Bryan[RS] at FDC:
http://free-dc.org/forum/showthread.php?s=&threadid=10485


Current Outage of All that is Rieselsieve

As you may (or may not have noticed), all of the RieselSieve Project has been down since about noon eastern. Some time this morning, our DNS was poisoned, and we have been working since to change nameservers, get dns records re-propogated, and try and determine how exaclty everything broke. That is why things come up as RieselSieve.com being non-existent, not just unresponsive. All servers are up and running, and as soon as the DNS comes back online, crunching will resume. Lee, Sean and I have been working, as I said, all day on this - and we're really sorry about the downtime. This is the first non-software related problem we've had, and it's hitting us hard. Hopefully before I leave for school tomorrow things will be back online. If they are, I'll post here...otherwise I'll post an update when I get home (6pm EST or so).

Thanks all for your patience.

Bryan
Stats Administrator
RieselSieve Project

:cry: my cache just ran out.
good luck bryan, Lee & team
hope you can sort it all out soon
can you suspend the WU timeouts ?

[Brucifer]

Yup, whatta bummer..... my two llrnet systems are empty too. Hopefully they get it running before my sieving ranges are completed, but that's getting pretty close too.

Too bad he didn't post the IP addresses of their stuff so that people could just add that to their hosts file and keep rolling along..... :(

[bryanRS]

Just to copy my post from Free-DC (one quick word - since the LLRNet server is on a dynamic IP, I'd recommend using the dynamic updating address, or you can use the IP and just check for updates (#rieselsieve on irc.freenode.net is best - RieselStatsBot and B2 will have the same IP, just do a WHOIS).


Another update, before Lee arrives home from work. We're still running on those no-ip servers:

Main Website (Including Forums): http://rieselsieve.redirectme.net
Stats Website: http://llrnet.redirectme.net

LLRNet Main Server: llrnet.redirectme.net, port 7000, or use 216.196.211.194 UPDATE as of 6:00 pm EST, 12/6
LLRNet Double Check Server: dc-llrnet.redirectme.net, port 7000 or use 24.210.29.64

Updates will follow as we get information from Godaddy.


Thanks all for your patience - we got DNS poisoned, and are still trying to recover/repropogate things.

Bryan

Stats Administrator
RieselSieve Project

[bryanRS]

Sorry, looks like another IP refresh. Here's the new ip's:

216.68.186.52 rieselsieve.com
216.68.186.52 llrnet.rieselsieve.com
24.210.29.64 dc.rieselsieve.com

Godaddy initially blamed our problems on our DNS provider. When Lee finally convinced them that REGISTRAR-HOLD kept us out of the Verisign Root File, (therefore removing us from the Internet), they apologized and agreed that it was their fault. As of this afternoon, they had started to process the change, removing the hold, and beginning the propogation process - since it had not really started yet, we're still talking up to 36-48 hours before this mess is fixed. Obviously, since the nameservers are live, we're hoping for a much faster turnaround.

I will say we've already started a discussion about how to avoid this problem from occuring again. One thing that I am pushing for (and had been a previous idea) is to have built-in failover servers in the llrnet client. This, of course, needs to be programmed. Any assistance with LUA programming would be greatly appreciated, if anyone can help I'm going to try to look into this myself.

Another thing will be changing Lee to a static connection in January. He's working that out with his ISP, and we're looking forward to the change. One more change is the possibility of registering a mirror domain (i.e, rieselsieve.net) and having the DNS go through another provider. This, of course, would only be useful if the failover server I mentioned above is worked out. Also, team proxies are on the horizon - I've found the code that sets up how a proxy is handled, now I just have to figure out how to communicate the user info individually. It's going to take some time.

Thanks for everyone's support and watchful eyes during this difficult time. Hopefully this clears out any problems that we would have faced in 2006....and beyond. Hold on - just a little more time till we're back.

Bryan
Stats Administrator
RieselSieve Project

[Brucifer]

Unfortunately I blew an A/C/ compressor tonight that cools my computer room. So I'm going to be going offline for a couple of months until all the holiday stuff is out of the way and I get a buck or two saved up to replace the bugger. :(

[AMDave]

Thanks bryan.
The problem may still exist, but with your work-around working like a treat it looks like many of us are still kickin'ass.
I can't help with the LUA upgrade tho'. Not in my kit bag I'm afraid.

72CJ5
when it rains it pours!
We had a sudden lightning storm while I was on my way home from work.
My son was shutting the network down (9yrs old and smart :D ) when the power flickered and went out.
Thanks to his quick thinking I only lost one machine.
Unfortunately, his games machine :(
It seems to be repairable though.
Unit testing shows it's should just be the HDD (I hope).

That puts 3 machines on my workbench at once :shock:

Nowhere near as bad as your A/C, but I can empathise.

What a bummer.

[Brucifer]

Sorry to hear that AMDave :( I guess it's just the way the stars are aligned or something... I'm calling the people we have a contract with, and see what the dirty deed is going to cost. but I'm sure not holding my breath on it.

And just to stay on topic here, the latest IP addresses don't work anymore, so I can't connect to the rieselsieve project either. Maybe down the road I'll get back on it when I get this A/C issue straightened out. Maybe by then the rieselsieve dns will be working.

[bryanRS]

New IP's again. Godaddy has communicated with Internic, and hopefully this gets flushed out soon.

216.196.208.201 rieselsieve.com
216.196.208.201 llrnet.rieselsieve.com
24.210.29.64 dc.rieselsieve.com


Bruce - sorry about your A/C problems. Although, I will say, I hope that our DNS is fixed long before a few months :)

Bryan

[AMDave]

72CJ5

I didn't go the hosts file mod.

I simply commented out the host name in the client config file and added a line with the llrnet.redirectme.net hostname instead.

It has been working for me no problems.
When the problem is fixed I can swap it back, or I may not bother as it seems to work a treat.

[bryanRS]

Well, I finally have some good news. Our Zone File has been created at the root nameservers. This means that we're going to be out of the woods soon. We just have to wait for the ip's to propogate through - and all will be back on line. I know right now the dynamic IP doesn't seem to have updated, so some servers are resolving rieselsieve.com incorrectly. One more HOSTS file update, and then we'll be able to use regular DNS around midnight EST (5:00 GMT). Thanks again everyone!

216.196.209.194 rieselsieve.com
216.196.209.194 llrnet.rieselsieve.com
24.210.29.64 dc.rieselsieve.com


Bryan

[bryanRS]

As of about 11 pm EST, DNS was restored. Everything is back up and running over at Rieselsieve. Thanks again to everyone for working through this with us.

Bryan

[AMDave]

Thank the project team for us.
Y'all done good.
=D<