Message boards :
Number crunching :
To force the correction right away, simply detach and then (re)attach the project.
Message board moderation
Author | Message |
---|---|
STE\/E Send message Joined: 29 Mar 03 Posts: 1137 Credit: 5,334,063 RAC: 0 |
This has got to be the most Stupid Advice I have ever heard of. What about all the Wu's that will be dumped when people take this advice and then everybody's sitting around for the next 2 weeks wondering why they can't get no Wu's Verified. It will be because of this advice, thats why... I suggest you just manually update your PC or PC,s, thats what I did and it wasn't that big of a deal, I have a lot of WU's Cached and just didn't feel like dumping them so they would have to be reissued in 2 weeks ... |
Team Jolt Cola Send message Joined: 21 Aug 99 Posts: 31 Credit: 2,015,228 RAC: 0 |
Seconded - don't do it, it buggers up all the WU's honest crunchers have done and we have to wait another several weeks before the WU is given to someone else and then comeas back before we get credit. Wake up berkeley - this is the real world, its called firewalls and PAT - just direct the traffic sideways seamlesasly without people binning dozens of WU's. M. |
Peart Send message Joined: 13 Jun 99 Posts: 7 Credit: 1,719,614 RAC: 0 |
Agreed. Let's see how long it will take before they remove the "advice" from the main page... if they ever do, that is. Sheesh. :( |
Keck_Komputers Send message Joined: 4 Jul 99 Posts: 1575 Credit: 4,152,111 RAC: 1 |
> Agreed. > > Let's see how long it will take before they remove the "advice" from the main > page... if they ever do, that is. > > Sheesh. :( > I would bet the advice will not be removed. Detaching and reattaching is the only option for people that attached to the setiboinc URL. Only if you are attached to http://setiathome.berkeley.edu will the update happen automatically after several failed attempts. John Keck BOINCing since 2002/12/08 |
Darren Send message Joined: 2 Jul 99 Posts: 259 Credit: 280,503 RAC: 0 |
> I would bet the advice will not be removed. Detaching and reattaching is the > only option for people that attached to the setiboinc URL. Only if you are > attached to http://setiathome.berkeley.edu will the update happen > automatically after several failed attempts. > John Keck > BOINCing since 2002/12/08 But surely there are very few people attached to the setiboinc url. The url was changed to the current one the day it went live, so only mostly beta testers would have ever been connected with that url in the first place. Additionally, they posted on June 22 for everyone to switch to the new url if you were using a different one. Even I changed the url that day - and I'm usually bringing up the rear when it comes to being current and on top of things - so I can't imagine that many are still using it. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
> > > I would bet the advice will not be removed. Detaching and reattaching is > the > > only option for people that attached to the setiboinc URL. Only if you > are > > attached to http://setiathome.berkeley.edu will the update happen > > automatically after several failed attempts. > > John Keck > > BOINCing since 2002/12/08 > > But surely there are very few people attached to the setiboinc url. > The url was changed to the current one the day it went live, so only mostly > beta testers would have ever been connected with that url in the first place. > Additionally, they posted on June 22 for everyone to switch to the new url if > you were using a different one. Even I changed the url that day - and I'm > usually bringing up the rear when it comes to being current and on top of > things - so I can't imagine that many are still using it. > For those of us that switched over a while back (or joined under the new URL) there is a much safer solution. Manually update ten or eleven times, and the new scheduler is found. > > [/url] |
JAF Send message Joined: 9 Aug 00 Posts: 289 Credit: 168,721 RAC: 0 |
> > > > > I would bet the advice will not be removed. Detaching and > reattaching is > > the > > > only option for people that attached to the setiboinc URL. Only if > you > > are > > > attached to http://setiathome.berkeley.edu will the update happen > > > automatically after several failed attempts. > > > John Keck > > > BOINCing since 2002/12/08 > > > > But surely there are very few people attached to the setiboinc > url. > > The url was changed to the current one the day it went live, so only > mostly > > beta testers would have ever been connected with that url in the first > place. > > Additionally, they posted on June 22 for everyone to switch to the new > url if > > you were using a different one. Even I changed the url that day - and > I'm > > usually bringing up the rear when it comes to being current and on top > of > > things - so I can't imagine that many are still using it. > > > > For those of us that switched over a while back (or joined under the new URL) > there is a much safer solution. Manually update ten or eleven times, and the > new scheduler is found. > > > > > > Just a wild guess, but one could probably update one of the .xml files in their Boinc seti directory? I was one of the "fools" who took the advice on the site to "simply detach and then (re)attach" .... |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
> For those of us that switched over a while back (or joined under the new URL) > there is a much safer solution. Manually update ten or eleven times, and the > new scheduler is found. Yes, but how do you do that on a Linux box? ;) We're letting it run its course at the moment. ---------------------- Jordâ„¢ |
Darren Send message Joined: 2 Jul 99 Posts: 259 Credit: 280,503 RAC: 0 |
> Just a wild guess, but one could probably update one of the .xml files in > their Boinc seti directory? Most of the xml files contain a reference to the source scheduler. Possibly just changing this url might correct it (but of course they didn't post the new url that it will use). All of my hosts are Linux, so I can't even force the manual updates. At this point, all of mine have already hit their low-water marks and downloaded Predictor work units since they couldn't contact seti. They continue to try as they have uploaded work units they want to report, so I'm just going to let them go while they run their course of absurdly long deferrals and eventually they'll tire themselves out and finally ask for a master file fetch. |
JAF Send message Joined: 9 Aug 00 Posts: 289 Credit: 168,721 RAC: 0 |
> > For those of us that switched over a while back (or joined under the new > URL) > > there is a much safer solution. Manually update ten or eleven times, and > the > > new scheduler is found. > > Yes, but how do you do that on a Linux box? ;) > We're letting it run its course at the moment. > ---------------------- > Jordâ„¢ > > > Sorry, I'm using a windows system and didn't realize the xml files weren't available to a linux system. I was upset over losing 20 hours of work and was just reponding with a "why couldn't they have output the information in a better format." |
EclipseHA Send message Joined: 28 Jul 99 Posts: 1018 Credit: 530,719 RAC: 0 |
> Sorry, I'm using a windows system and didn't realize the xml files weren't > available to a linux system. XML is there on all platforms I've seen, but on linux, boinc is not a "window", it's a command line process. There's no button.. there's a command line option -update_prefs, but it means starting/killing the process over and over.. One of my linux boxes did recover after about 4 hours, but the my main linux box is back doing Seti 1, so I see in a few months.... |
eberndl Send message Joined: 12 Oct 01 Posts: 539 Credit: 619,111 RAC: 3 |
Just a comment: I haven't had a single SETI WU in about 5 days, and for anyone with nothing cached, detatching and reattaching is a perfectly acceptable method of forcing the update... we delete nothing, so it makes everything just a little faster. Of course, I reattatch just moments after PAH requests about 14 x 3 = 42 h of work... *sigh* |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
> Of course, I reattatch just moments after PAH requests about 14 x 3 = 42 h of > work... *sigh* Which shouldn't matter, if you have set correct preferences for Seti@home. And off the 14 units PAH just sent you, there's probably a couple of charmm units in there as well, they run a lot quicker. Yet maybe you should reset your caching preferences in your Seti General preferences (in Your Account) to something with a lower low-water mark. Setting it to 0.1 days to 1 day may give you units earlier than setting it to 1 to 2 days. Do know that setting preferences for the last project you attached to will set these preferences for all[/b] BOINC projects you participate in. Read the small lettering at the top of the General preferences page. ---------------------- Jordâ„¢ |
Alex Send message Joined: 26 Sep 01 Posts: 260 Credit: 2,327 RAC: 0 |
For those people complaining about 'how to manually update' their linux boxes over a network: You can run your linux client using the '-allow_remote_gui_rpc' switch. When running boincview, you set up a location to point to your linux box's ip address, and then click the 'projects tab, and manually update using a rightclick. Then, you can use an app like Boincview to remotely view and adminster boinc over the network. I don't recommend using Boincview for long periods, as it (Boincview verson 0.7e) takes up 10% of my 2.2 ghz celeron's cpu under XP. link to boincview http://boincview.amanheis.de/ Boincview runs under windows, and I've made it run under wine (with a huge performance hit) |
Carl Cuseo Send message Joined: 18 Jan 02 Posts: 652 Credit: 34,312 RAC: 0 |
OK- I'm one of those who was doing the beta test and just noticed that my URL was never changed over to the new one as I had a full cache and did not want to trash the work. So now I cannot update and have a stack of units ready to report plus 3 days of unprocessed WU's I'd rather keep. In my boinc client state file I see this in part: (scheduler_url)http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi(/scheduler_url) (master_url)http://setiboinc.ssl.berkeley.edu/sah/(/master_url) (project_name)SETI@home(/project_name) (user_name>)Carl Cuseo(/user_name) (team_name)Carolyn's Clinic(/team_name).....etc less/more changed to )( Anyone tell me whay the scheduler & master lines hould look like to allow updates? Thanks...cc |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Carl, as a work-around you could try the following: Stop the BOINC GUI client. Start -> Run, type cmd {hit enter} Navigate to your BOINC folder using DOS commands: - example given: cd c:program filesboinc {hit enter} When you're there, simply type the following on the command line: boinc_cli -update_prefs http://setiathome.berkeley.edu {hit enter} This will start the CLI, will make sure you are contacting the correct scheduler for now. If it fails to make contact, press CTRL+Break. It's even easier if you make the above a shortcut on your windows desktop. - In Windows, navigate to your BOINC folder. - Resize the window you're working in so you can see part of your desktop. - Scroll down until you see boinc_cli.exe in the BOINC folder. - Right-click it, then move it to the desktop while you hold the right mouse button down. Over the desktop, let go of the RMB, then leftclick on Make Shortcut here. - Rightclick on the icon you just made, properties. - in the Target line, add a space and -update_prefs http://setiathome.berkeley.edu and press Apply. - doubleclick this icon when you want to start the CLI. To stop it, use CTRL+Break. ---------------------- Jordâ„¢ |
Keck_Komputers Send message Joined: 4 Jul 99 Posts: 1575 Credit: 4,152,111 RAC: 1 |
@carl (master_url)http://setiboinc.ssl.berkeley.edu/sah/(/master_url) That line should read: (master_url)http://setiathome.berkeley.edu/(/master_url) The setiboinc url will not work anymore. Looks like a detach and reattach are in your future. @darren It is possible to edit xml, it has to be done in several places though and if messed up it may require a reinstall to fix. 1) The line quoted above in client_state.xml 2) A similar line in the account..xml file. The file itself will also have to be renamed to 'account_setiathome.berkeley.edu.xml'. 3) The project folder will also have to be renamed to 'setiathome.berkeley.edu'. Expect the current workunit to error out even if done correctly. Other work in the queue should be preserved though. There may be other warning/error messages generated that will fix themselves. Be sure to exit the client while your editing, also do a restart or two to work out other to things that the client will fix on it's own. @to those running *nix or other CLI versions: I'm not sure if it works this way on the CLI versions, but on the GUI once you do the update command it keeps trying until a connection is made. So after about 12 hours of backoffs the client will have made enough attemps to get the new url from one update command. John Keck BOINCing since 2002/12/08 |
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0 |
> Which shouldn't matter, if you have set correct preferences for Seti@home. And > off the 14 units PAH just sent you, there's probably a couple of charmm units > in there as well, they run a lot quicker. Actually, the last 4 charmms I had took almost as long as a normal mfold. (40-45 minutes on my machine) <a> [/url] |
Darren Send message Joined: 2 Jul 99 Posts: 259 Credit: 280,503 RAC: 0 |
> @darren > It is possible to edit xml, it has to be done in several places though and if > messed up it may require a reinstall to fix. > > 1) The line quoted above in client_state.xml > > 2) A similar line in the account..xml file. The file itself will also have to > be renamed to 'account_setiathome.berkeley.edu.xml'. > > 3) The project folder will also have to be renamed to > 'setiathome.berkeley.edu'. > > Expect the current workunit to error out even if done correctly. Other work in > the queue should be preserved though. There may be other warning/error > messages generated that will fix themselves. Be sure to exit the client while > your editing, also do a restart or two to work out other to things that the > client will fix on it's own. I just let them all run their course and change it themselves. I've been connected to the correct master url since the day it went live (I changed them all from setiboinc to setiathome when the first notice came out on 22 June), so it was only the fetch url that had to update. Since I also do predictor, it was no problem for me to let everything fail on seti until it all got reset. FYI, it's only taking about 7 hours for them to correct on their own. The first 6 fails all only had a 1 minute deferral, then about 15 minutes, 45 minutes, 2 hours and 4 hours, respectively. All but 1 of 7 have already completed the cycle, but of course they're all loaded up to the hilt again with predictor units - so those will all finish tomorrow just in time for the WU shortage Rom mentioned ;-/ Darren |
CoolSpot Send message Joined: 26 Mar 00 Posts: 3 Credit: 103,556 RAC: 0 |
> Stop the BOINC GUI client. > Start -> Run, type cmd {hit enter} > Navigate to your BOINC folder using DOS commands: > - example given: cd c:program filesboinc {hit enter} > When you're there, simply type the following on the command line: > > boinc_cli -update_prefs http://setiathome.berkeley.edu {hit enter} > > This will start the CLI, will make sure you are contacting the correct > scheduler for now. If it fails to make contact, press CTRL+Break. I tried this but i only get "project http://setiathome.berkeley.edu not found" what should i do ? |
©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.