Message boards :
Number crunching :
Work units started going down on my Linux computer.
Message board moderation
Author | Message |
---|---|
forward Send message Joined: 1 Jun 99 Posts: 53 Credit: 2,658,479 RAC: 0 |
Today my Linux computer uploaded 3 work units and my work unit count on the computer went from 51 to 48. It shows that my last connect time was June 15, with no connection for today. I am running Ned's clients and have had no problems with them. I deleted the clients I was using and downloaded them again from Ned's site. I will wait and see if this works. Any one have any other ideas to try? |
Fivestar Crashtest Send message Joined: 10 Dec 99 Posts: 226 Credit: 5,377,978 RAC: 0 |
Today my Linux computer uploaded 3 work units and my work unit count on the computer went from 51 to 48. It shows that my last connect time was June 15, with no connection for today. I am running Ned's clients and have had no problems with them. I deleted the clients I was using and downloaded them again from Ned's site. I will wait and see if this works. They don't keep all your work units on that list, the older ones drop off. And if you have a pretty big cache, your computer won't connect to get more until it is about drained. How often are you set to connect? You can do commands to make the work units that are done report here http://boinc.berkeley.edu/client_unix.php I am using Ned's client on a PIII and I have successfully used those commands to make units report. Then you could see if it is working ok. Pam |
forward Send message Joined: 1 Jun 99 Posts: 53 Credit: 2,658,479 RAC: 0 |
Today my Linux computer uploaded 3 work units and my work unit count on the computer went from 51 to 48. It shows that my last connect time was June 15, with no connection for today. I am running Ned's clients and have had no problems with them. I deleted the clients I was using and downloaded them again from Ned's site. I will wait and see if this works. I also have Ned's clients on a PIII and have it set for .50 days. I will try your suggestion. Thanks |
Ned Slider Send message Joined: 12 Oct 01 Posts: 668 Credit: 4,375,315 RAC: 0 |
Hi Folks, Nice to here you're using my clients :) Pam is correct - what you're seeing is normal. @ Pam - there's also a client for amd64 now Pam - you really should try that one too as it's much faster than the native berkeley client you're still using :) Regards, Ned *** My Guide to Compiling Optimised BOINC and SETI Clients *** *** Download Optimised BOINC and SETI Clients for Linux Here *** |
Fivestar Crashtest Send message Joined: 10 Dec 99 Posts: 226 Credit: 5,377,978 RAC: 0 |
Hi Folks, I have the native Berkeley on the newest AMD 64 but I did try to put the optimized client from you and another client on but could not get them to execute. The executable file seemed small, so I figured I was having a bad download night. And the other AMD 64 is running an optimized client I found somewhere else. You can tell by the benchmarks which is which, since the processor and the motherboards are the same. But I noticed the new machine is doing 2.2 sec timesteps on climateprediction.net, while the first AMD is doing 2.5 sec timesteps. I thought that was a little weird. The first AMD is screaming on SETI and is at the top of my computer list now. And I thought changing to the optmized BOINC did shorten the timestep some on the first machine for climate. So, the question is, did I just do a better job assembling my second machine (not so much fumbling with seating the heatsink) and that's why it's crunching climate better? And, will I get under two second timesteps when I get your BOINC client going? Or is there just some variation with processors? When problems at climate are cleared up, I will try for your client again and see what the difference is, and sorry if anyone is annoyed because I blathered on about a non-SETI project. Pam |
forward Send message Joined: 1 Jun 99 Posts: 53 Credit: 2,658,479 RAC: 0 |
Today my Linux computer uploaded 3 work units and my work unit count on the computer went from 51 to 48. It shows that my last connect time was June 15, with no connection for today. I am running Ned's clients and have had no problems with them. I deleted the clients I was using and downloaded them again from Ned's site. I will wait and see if this works. I still do not get any new work units done showing on Seti with my Linux computer no matter what clients I use for seti. I have had 5 work units uploaed since June 15 and none of them show up as being done on my stats. I switched my Linux computer over to Predictor and it is showing my work units done with no problems. I cannot figure out why Seti will not show my work units done. I registered my first 51 work units with my Linux computer on Seti with no problem. |
Fivestar Crashtest Send message Joined: 10 Dec 99 Posts: 226 Credit: 5,377,978 RAC: 0 |
IF Seti were running, you should have a boatload of units to report. I notice in the info for that computer, it says your average turnaround time is 0 days and your average upload rate is unknown. This sure looks like SETI quit working for you. If you are still attached to SETI, then it should switch between SETI and Predictor. Are you running BOINC in a command line window? Pam |
forward Send message Joined: 1 Jun 99 Posts: 53 Credit: 2,658,479 RAC: 0 |
Pam, I am very new to Linux, I bought the computer to learn Linux and run Seti. I think you would call it a command line window, it says shell on my computer. So far Predictor is working great. Seti is off the computer now, but when it was on the screen said it was downloading work, processing the work, and saying it was uploading the work, but for some reason the work was not getting back to Seti. I will keep trying to run Seti, as I want to find out if I am doing somthing wrong. It is strange to me that it was working fine and for some reason just stopped working. Thanks Richard |
©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.