1) Message boards : Number crunching : BOINC 6.6.4 (Message 863426) Posted 8 Feb 2009 by muddocktor Post: I'm having the exact same problems as you are with 6.6.4 on my main rig. I just reinstalled to get the cuda client running on this machine and uninstalled the previous version (6.2.x) and ran ccleaner to get all the fragments left and installed 6.6.4 and the cuda files. It seems to be doing work, but I can't click on the tasks tab or it crashes out.

2) Message boards : Number crunching : cuda now running (Message 841057) Posted 17 Dec 2008 by muddocktor Post: Does this run alongside the other work I'm presently doing? Like my QX9650 is already processing 4 work units right now; if I upgrade the client and my drivers will I be processing 5 work units at one time (4 regular and one CUDA)? Also, will this run when you are using the optimized apps? Thanks in advance for any help you can provide.

3) Message boards : Number crunching : 0 credit for valid unit why??? (Message 836914) Posted 4 Dec 2008 by muddocktor Post: I just ran into this with a couple of AP work units myself and I tell you I am pissed about this. I dumped the rest of the AP junk off my laptop, which I was trying this out on and put the original appinfo.xml file back. I had over 83000 secs or cpu time in no no granted credit on a couple of work unit s and that is total BS too! I might try this again in 6 months to a year but until you people work the frigging bugs out I won't allow any AP work on any of my machines! If you can't tell by my tone of this post already I am really pissed you let this crap out to the general crunching population!

4) Message boards : Technical News : Blips and Bursts (Aug 07 2008) (Message 796398) Posted 11 Aug 2008 by muddocktor Post: Looks like they finally got in there and kicked the right box. At least I was able to upload all my finished work units just now on my work laptop, with a little manual coaxing by me. Now if they can just help us get some new work on our machines.

5) Message boards : Technical News : Ups and Downs (Aug 05 2008) (Message 793467) Posted 6 Aug 2008 by muddocktor Post: I sure hope you can clear up all the server problems soon, Matt.I have several machines with work results that won't upload and I've also had problems with my machines getting new work too. Good luck on getting the issues sorted tomorrow.

6) Message boards : Technical News : Rudy and Spider (Feb 28 2008) (Message 721481) Posted 3 Mar 2008 by muddocktor Post: Matt, the validators, even though the status page shows them as "running", are down, hung, in infinite loops, or otherwise not doing their jobs; and have been this way for at least 24 hours... [added] My pending, normally in the 1700-2900 range is now at 3700 and growing! [/add] Yeah, I was just coming here to see if there was an update on this myself. I saw my pending results balloon up from around 20k to around 55k credits over the weekend, with the majority of the ballooning happening since yesterday.

7) Message boards : Technical News : Merday Morn (Jun 11 2007) (Message 585631) Posted 12 Jun 2007 by muddocktor Post: I finally did get some work this evening for one fast machine that was out of work since yesterday but I am still having many many problems getting more work for my other machines.Here's a little snippet of some of my latest attempts for work: 6/11/2007 11:11:22 PM|SETI@home|Sending scheduler request: To fetch work 6/11/2007 11:11:22 PM|SETI@home|Requesting 1256065 seconds of new work 6/11/2007 11:11:42 PM|SETI@home|Scheduler RPC succeeded [server version 509] 6/11/2007 11:11:42 PM|SETI@home|Deferring communication for 11 sec 6/11/2007 11:11:42 PM|SETI@home|Reason: requested by project 6/11/2007 11:11:42 PM|SETI@home|Deferring communication for 1 min 0 sec 6/11/2007 11:11:42 PM|SETI@home|Reason: no work from project 6/11/2007 11:12:42 PM|SETI@home|Fetching scheduler list 6/11/2007 11:12:47 PM|SETI@home|Master file download succeeded 6/11/2007 11:12:52 PM|SETI@home|Sending scheduler request: To fetch work 6/11/2007 11:12:52 PM|SETI@home|Requesting 1256845 seconds of new work 6/11/2007 11:13:22 PM|SETI@home|Scheduler RPC succeeded [server version 509] 6/11/2007 11:13:22 PM|SETI@home|Deferring communication for 11 sec 6/11/2007 11:13:22 PM|SETI@home|Reason: requested by project 6/11/2007 11:13:22 PM|SETI@home|Deferring communication for 1 min 0 sec 6/11/2007 11:13:22 PM|SETI@home|Reason: no work from project 6/11/2007 11:14:22 PM|SETI@home|Sending scheduler request: To fetch work 6/11/2007 11:14:22 PM|SETI@home|Requesting 1257606 seconds of new work 6/11/2007 11:14:32 PM|SETI@home|Scheduler RPC succeeded [server version 509] 6/11/2007 11:14:32 PM|SETI@home|Deferring communication for 11 sec 6/11/2007 11:14:32 PM|SETI@home|Reason: requested by project 6/11/2007 11:14:32 PM|SETI@home|Deferring communication for 1 min 0 sec 6/11/2007 11:14:32 PM|SETI@home|Reason: no work from project 6/11/2007 11:15:32 PM|SETI@home|Sending scheduler request: To fetch work 6/11/2007 11:15:32 PM|SETI@home|Requesting 1258234 seconds of new work 6/11/2007 11:15:47 PM|SETI@home|Scheduler RPC succeeded [server version 509] 6/11/2007 11:15:47 PM|SETI@home|Deferring communication for 11 sec 6/11/2007 11:15:47 PM|SETI@home|Reason: requested by project 6/11/2007 11:15:47 PM|SETI@home|Deferring communication for 1 min 0 sec 6/11/2007 11:15:47 PM|SETI@home|Reason: no work from project 6/11/2007 11:16:47 PM|SETI@home|Sending scheduler request: To fetch work 6/11/2007 11:16:47 PM|SETI@home|Requesting 1259107 seconds of new work 6/11/2007 11:17:07 PM|SETI@home|Scheduler RPC succeeded [server version 509] 6/11/2007 11:17:07 PM|SETI@home|Deferring communication for 11 sec 6/11/2007 11:17:07 PM|SETI@home|Reason: requested by project 6/11/2007 11:17:07 PM|SETI@home|Deferring communication for 1 min 0 sec 6/11/2007 11:17:07 PM|SETI@home|Reason: no work from project I hope that you all can get some more work served up tomorrow so I can get my machines to get a healthy cache of extra work units built back up again.

8) Message boards : Technical News : Forum Decorum (May 21 2007) (Message 573185) Posted 21 May 2007 by muddocktor Post: Thank you for the update, Kevin. IMO, the lack of updates is part of the mounting frustration problem with a lot of folks, including me. Even though you are a scientist and not a "computer guy", you posting information such as this helps the project as a whole in that we crunching donators see that at least someone is on the job trying to get things running again. And with you posting up the info, it keeps the computer guys from having to take time away from fixing the problem to post info up here for us to read. I know that a lot of insinuations were posted in other threads and some of the posts went way too far, but they did insinuate a valid point. I am pretty new to the Seti project, having started about a year ago. But from what I gather, this Thumper croaking thing is the biggest problem Seti has had in years and it took a while to get Thumper II installed and running. And from what I have read here it sounds like some new server code broke a lot more stuff right around the time that Thumper went belly up too, which is making recovery much harder. But to me at least, it seems that you guys have a kind of "so what" attitude about the servers going wonky during the weekend (and this being the first weekend with Thumper II online too) and with Matt taking vacation with all that's happening too. Of course, Matt just might not have been able to reschedule his vacation due to timing or finances and I can understand that, but it seems to me that you guys kind of dropped the ball on support of the servers this last weekend. In normal times this probably wouldn't be an issue but you all are trying to get the project back up and running after a very protracted and hectic series of calamities and someone with the knowhow should have been on call to look into problems through this last weekend. And I would suggest that for the next few weekends it would be a good idea to have someone close by to look into problems too. The sooner you guys can sort out the problems you are running into and the longer that you can keep uploads and downloads coming and going, the sooner the project will get on a more even keel and then everyone can kick back and relax and watch football or racing or do whatever they want on the weekend.

9) Message boards : Cafe SETI : Is Berkeley really serious about SETI? (Message 572821) Posted 21 May 2007 by muddocktor Post: I guess we are just seeing the results of an operation run by academia and not business. Getting things back running smoothly after the big server crash doesn't seem to be a top priority with Berkeley; looks like they'd rather do gigs and go on vacations instead. I had participated in Stanford's big DC project, Folding@Home for 5 years before trying out Seti last year with 1 machine and then earlier this year switching most of my crunchers over to this project as I liked the BOINC interface much better than the clunky interface of F@H and I especially liked the way that BOINC let's me monitor each individual machine in the stats. F@H has nothing to compare to that, stats-wise. But at least the people involved with their project at Stanford don't just take off for a week or 2 when they have broken server code, like it is right now. It's just pretty damn pitiful right now and I'm about ready to abandon Seti and move on to a project that takes themselves a little more seriously.

10) Message boards : Technical News : Takin' Care of Business and Workin' Overtime (May 11 2007) (Message 565769) Posted 12 May 2007 by muddocktor Post: Thanks for the update and for you all working through the weekend to get Thumper back in operation, Kevin. I'll be looking forward to getting more work to crunch soon due to efforts by dedicated folks such as you all.

11) Message boards : Technical News : Pickup (May 11 2007) (Message 565353) Posted 11 May 2007 by muddocktor Post: Glad to hear that the server has finally made it there. Hopefully you won't have too much trouble getting all the database and drives and stuff going and making fresh work for us. Until you got Thumper (Thumper II maybe?) going, I will just keep my dual core machines helping the Stanford bunch fold some proteins through the weekend.

12) Questions and Answers : Getting started : BOINC is killing you. (Message 511536) Posted 1 Feb 2007 by muddocktor Post: I first tried out Seti and Boinc in August of 2006 with a machine I was retiring from the Folding@Home project and found that Boinc wasn't that hard to set up for me. I ran it for about a month or so before parting out that machine, but both Boinc and Seti left a decent impression on me then as being fairly reliable and easy to use. Fast forward to this month; I got pretty disgusted with some of the events happening with the F@H project and found that I was no longer having fun just running that project with my little crunching farm, so I decided to switch some machines to Boinc and Seti (since the forums I fold for also has a big Seti team too). I then set up Boinc on several of my computers with no real problems and attached them all to Seti (again, with no problems). I now have 5 machines crunching for Seti and it is going pretty painlessly and it seems that my machines are doing a fair amount of work. Now I can't compare Boinc to the Seti Classic program as I never tried Seti Classic. But to me the Boinc client was easy to set up and get running. One thing I did do was set my machines up to "Run Always" in the activity column as all my machines have 512 MB - 2 GB ram and most are dedicated crunchers. But I have no problems even with gaming on my main rig with Boinc running in the background, with 2 GB ram and a Core 2 Duo processor. One thing that might have helped me with setting up the Boinc client is the fact that I have been participating in the F@H project for 5 years, so I'm an experienced DC'er and knew that I would need to read around a little if I ran into problems setting the client up.

 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.