Can't attach to the project
20 Feb 2005 16:01:48 UTC
Topic 187765
(moderation:
When I try to attach I'm getting the following messages:
http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:15 - Project prefs: no separate prefs for home; using your defaults
--- - 2005-02-20 15:58:16 - Insufficient work; requesting more
--- - 2005-02-20 15:58:19 - Insufficient work; requesting more
http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:19 - Requesting 6890 seconds of work
http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:19 - Sending request to scheduler: http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:22 - Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
--- - 2005-02-20 15:58:22 - H1_1459.9__1460.0_0.1_T00_Test02: error in element
Einstein@Home - 2005-02-20 15:58:22 - Can't parse work unit in scheduler reply
Einstein@Home - 2005-02-20 15:58:22 - SCHEDULER_REPLY::parse(): no close tag
Einstein@Home - 2005-02-20 15:58:24 - Resetting project
Einstein@Home - 2005-02-20 15:58:24 - Detaching from project
Can't attach to the project
)
Are you using the latest Boinc version (4.19)?
If so then there could be something wrong with Einstein@home server.
Laryea
Yes it's 4.19
)
Yes it's 4.19
From what i can see you have
)
From what i can see you have 5 computers that look the same on your account. I suspect that you have tried 5 times and the scheduler has given you a WU etch of those times. Haven’t got a clue. Usually i would say restart the machine and try again and if that don’t help and Einstein is your only project, uninstall BOINC and delete the BOINC folder and install it again. But i suspect you already tried all of that.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
I set up two computers and
)
I set up two computers and got that error the first time on both, the second time it worked, but seems in my stats my machines got a WU attached to them that was never sent, that will need to be cleared up, or just left to expire, but dont like having WU's that i cant complete in my stats right from the startup.
I did have two of each host, but as i couldnt tell which was which merged them, should have worked it out and deleted the two ghost ones.
> When I try to attach I'm
)
> When I try to attach I'm getting the following messages:
>
> http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:15 - Project prefs: no
> separate prefs for home; using your defaults
> --- - 2005-02-20 15:58:16 - Insufficient work; requesting more
> --- - 2005-02-20 15:58:19 - Insufficient work; requesting more
> http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:19 - Requesting 6890 seconds
> of work
> http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:19 - Sending request to
> scheduler: http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
> http://einstein.phys.uwm.edu/ - 2005-02-20 15:58:22 - Scheduler RPC to
> http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
> --- - 2005-02-20 15:58:22 - H1_1459.9__1460.0_0.1_T00_Test02: error in
> element
> Einstein@Home - 2005-02-20 15:58:22 - Can't parse work unit in scheduler
> reply
> Einstein@Home - 2005-02-20 15:58:22 - SCHEDULER_REPLY::parse(): no close tag
> Einstein@Home - 2005-02-20 15:58:24 - Resetting project
> Einstein@Home - 2005-02-20 15:58:24 - Detaching from project
If anybody else has gotten this error I would appreciate if you could post your client output and any other relevant information here.
One of the side effects of this problem is that you end up with multiple hosts and results when you should only have gotten one of each. If you have had this problem you should go to your account click on your computers http://einstein.phys.uwm.edu/hosts_user.php
and merge your computers to help clean up the mess.
I currently do not know what is going wrong but we are trying to solve this problem as fast as we can.
Sorry.
It would be very helpful to
)
It would be very helpful to us if you could look in your BOINC installation directory and post the file called sched_reply.xml. If there is any line containing your account key (this will start with an 'authenticator' tag) just edit out that line, please.
Bruce
Director, Einstein@Home
- scheduler_reply message
)
- scheduler_reply
message priority="low">Server can't open log file
request_delay>3600
project_is_down />
/scheduler_reply>
had to clip the first
> - scheduler_reply >
)
> - scheduler_reply
> message priority="low">Server can't open log file
> request_delay>3600
> project_is_down />
> /scheduler_reply>
>
> had to clip the first
Could you please post the time/date stamp of the 'can't open log file' message?
Bruce
Director, Einstein@Home
> > - scheduler_reply > >
)
> > - scheduler_reply
> > message priority="low">Server can't open log file
> > request_delay>3600
> > project_is_down />
> > /scheduler_reply>
> >
> > had to clip the first
>
> Could you please post the time/date stamp of the 'can't open log file'
> message?
>
> Bruce
>
Attached fine, hopefuly if the problem is still occuring someone will be able to drop a time stamp
Dont have that, thats the complete file, and boinc has been restarted and such after that, ive got E@H working now, but thats the error others ive talked to get as well, seems to happen the first time like i mentioned before, then works after that, others had to try more times.
I still have a machine to attach, if i get the same error i can give you a timestamp.
> > Could you please post the
)
> > Could you please post the time/date stamp of the 'can't open log file'
> > message?
> >
> > Bruce
> >
>
> Attached fine, hopefuly if the problem is still occuring someone will be able
> to drop a time stamp
>
> Dont have that, thats the complete file, and boinc has been restarted and such
> after that, ive got E@H working now, but thats the error others ive talked to
> get as well, seems to happen the first time like i mentioned before, then
> works after that, others had to try more times.
>
> I still have a machine to attach, if i get the same error i can give you a
> timestamp.
I am hopeful that I have fixed this 'first attachment' bug about 12 hours ago (at 4am local time!) on the server side. Such errors may still occur for users behind proxy servers. This is a problem that will be fixed in the next core client release.
Bruce
Director, Einstein@Home