Outage related problem.


log in

Advanced search

Questions and Answers : Windows : Outage related problem.

Author Message
Profile Gary CharpentierProject donor
Volunteer tester
Avatar
Send message
Joined: 25 Dec 00
Posts: 12497
Credit: 6,808,520
RAC: 5,787
United States
Message 973624 - Posted: 25 Feb 2010, 2:11:54 UTC

http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=1752
Bringing some attention to this main project/beta project hiccup from the recent outage as few people read the beta Q&A.

I'm sure someone here has the answer.
____________

Profile ignorance is no excuse
Avatar
Send message
Joined: 4 Oct 00
Posts: 9529
Credit: 44,433,274
RAC: 0
Korea, North
Message 973795 - Posted: 25 Feb 2010, 16:56:00 UTC - in response to Message 973624.

if he somehow and for some reason reattached to setibeti as seti@home the data he had would be dumped by seti beta. I dont think this is a project problem but more of a user error
____________
In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

End terrorism by building a school

Profile Gary CharpentierProject donor
Volunteer tester
Avatar
Send message
Joined: 25 Dec 00
Posts: 12497
Credit: 6,808,520
RAC: 5,787
United States
Message 973867 - Posted: 25 Feb 2010, 21:37:36 UTC - in response to Message 973795.

if he somehow and for some reason reattached to setibeti as seti@home the data he had would be dumped by seti beta. I dont think this is a project problem but more of a user error

Don't think so. For a while staff had the Beta website re-directed to the main web site while it (both) was down. I suspect the computer attempted a connection then and got a bogus re-direct and the project renamed Beta as main. And there are several reports of this now so it isn't a single user.
____________

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24520
Credit: 521,431
RAC: 84
United States
Message 973868 - Posted: 25 Feb 2010, 21:39:21 UTC - in response to Message 973867.

if he somehow and for some reason reattached to setibeti as seti@home the data he had would be dumped by seti beta. I dont think this is a project problem but more of a user error

Don't think so. For a while staff had the Beta website re-directed to the main web site while it (both) was down. I suspect the computer attempted a connection then and got a bogus re-direct and the project renamed Beta as main. And there are several reports of this now so it isn't a single user.

That would be it. The address of the scheduler is embedded on the front page of the project page. He will have to detach BETA and re-attach.
____________


BOINC WIKI

[B^S] sTrey
Volunteer tester
Avatar
Send message
Joined: 30 May 99
Posts: 29
Credit: 13,304
RAC: 0
Message 973877 - Posted: 25 Feb 2010, 22:34:31 UTC
Last modified: 25 Feb 2010, 23:05:41 UTC

No way to edit client-side data? I was bit by this too, and am not too thrilled about all the hours of crunching that would be lost if I have to reset.


Edit: until the beta scheduler is enabled it's hard to tell, but I think fixing the scheduler URL (and project name) in client_state.xml has fixed this.

Profile Gary CharpentierProject donor
Volunteer tester
Avatar
Send message
Joined: 25 Dec 00
Posts: 12497
Credit: 6,808,520
RAC: 5,787
United States
Message 973935 - Posted: 26 Feb 2010, 3:20:31 UTC - in response to Message 973877.
Last modified: 26 Feb 2010, 3:37:06 UTC

No way to edit client-side data? I was bit by this too, and am not too thrilled about all the hours of crunching that would be lost if I have to reset.


Edit: until the beta scheduler is enabled it's hard to tell, but I think fixing the scheduler URL (and project name) in client_state.xml has fixed this.

I think a hand edit of the client state file may work. In the Beta project Pappa and I may have an answer or workaround. At least I was able to report my dozen work units.
____________

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24520
Credit: 521,431
RAC: 84
United States
Message 973951 - Posted: 26 Feb 2010, 5:17:23 UTC - in response to Message 973935.

No way to edit client-side data? I was bit by this too, and am not too thrilled about all the hours of crunching that would be lost if I have to reset.


Edit: until the beta scheduler is enabled it's hard to tell, but I think fixing the scheduler URL (and project name) in client_state.xml has fixed this.

I think a hand edit of the client state file may work. In the Beta project Pappa and I may have an answer or workaround. At least I was able to report my dozen work units.

You may also have to edit the account_*.xml file, and possibly the scheduler_reply_*.xml file.
____________


BOINC WIKI

Profile Gary CharpentierProject donor
Volunteer tester
Avatar
Send message
Joined: 25 Dec 00
Posts: 12497
Credit: 6,808,520
RAC: 5,787
United States
Message 973959 - Posted: 26 Feb 2010, 5:49:50 UTC - in response to Message 973951.

No way to edit client-side data? I was bit by this too, and am not too thrilled about all the hours of crunching that would be lost if I have to reset.


Edit: until the beta scheduler is enabled it's hard to tell, but I think fixing the scheduler URL (and project name) in client_state.xml has fixed this.

I think a hand edit of the client state file may work. In the Beta project Pappa and I may have an answer or workaround. At least I was able to report my dozen work units.

You may also have to edit the account_*.xml file, and possibly the scheduler_reply_*.xml file.

In my case the account_*.xml file was not corrupt and did not need any changes, it still held my valid Beta account key.
Isn't the scheduler_reply_*.xml file just a log and overwritten when you press update?
I do see something in the sched_request_*.xml file that looks like it points to main, not beta.
<global_preferences> <source_project>http://setiathome.berkeley.edu/</source_project>


In any case I reported work, they validated, and I got new work. I think that is what counts.

____________

[B^S] sTrey
Volunteer tester
Avatar
Send message
Joined: 30 May 99
Posts: 29
Credit: 13,304
RAC: 0
Message 973961 - Posted: 26 Feb 2010, 6:17:32 UTC - in response to Message 973935.

No way to edit client-side data? I was bit by this too, and am not too thrilled about all the hours of crunching that would be lost if I have to reset.


Edit: until the beta scheduler is enabled it's hard to tell, but I think fixing the scheduler URL (and project name) in client_state.xml has fixed this.

I think a hand edit of the client state file may work. In the Beta project Pappa and I may have an answer or workaround. At least I was able to report my dozen work units.


Yes, fixing the two lines in client_state.xml was all I had to do -- now that the scheduler is responding again all my work was reported also :-D

Thanks for mentioning that Gary, I wouldn't have tried reporting work again based on the server status page, without reading that you had reported yours.

Pepo
Volunteer tester
Avatar
Send message
Joined: 5 Aug 99
Posts: 308
Credit: 418,019
RAC: 0
Slovakia
Message 974041 - Posted: 26 Feb 2010, 14:21:13 UTC - in response to Message 973959.

I think a hand edit of the client state file may work. In the Beta project Pappa and I may have an answer or workaround. At least I was able to report my dozen work units.

You may also have to edit the account_*.xml file, and possibly the scheduler_reply_*.xml file.

In my case the account_*.xml file was not corrupt and did not need any changes, it still held my valid Beta account key.
Isn't the scheduler_reply_*.xml file just a log and overwritten when you press update?

And fter editing the two offending lines in client_state.xml and updating the Beta project, Beta's both sched_request_*.xml and sched_reply_*.xml files contained just valid beta URLs.

Questions and Answers : Windows : Outage related problem.

Copyright © 2014 University of California