Unable to connect to Einstein Server
27 Feb 2005 10:01:37 UTC
Topic 188080
(moderation:
Could you please advise me what to do about the following error message.
Einstein@Home - 2005-02-27 09:56:40 - Message from server: Misconfigured BOINC installation or proxy-server problems!
Unable to connect to Einstein Server
)
> Could you please advise me what to do about the following error message.
>
> Einstein@Home - 2005-02-27 09:56:40 - Message from server: Misconfigured BOINC
> installation or proxy-server problems!
Ric, I've been waiting for someone to ask me this question! There has been a persistent problem, which we think has something to do with the way in which BOINC is installed or configured in some cases, which causes machines to register themselves more than once.
I see that you have a machine called 'bluenose'. Is this the machine showing the problem, or is it another machine?
Bruce
Director, Einstein@Home
> > I see that you have a
)
>
> I see that you have a machine called 'bluenose'. Is this the machine showing
> the problem, or is it another machine?
Yes my machine name is Bluenose. How is that significant?
Ciao Ric
Some days ago i detached one
)
Some days ago i detached one of my machines (Boinc 4.19, CPDN and LHC) from Einstein, today i re-attached it. And i got the same message like Ric:
Einstein@Home - 2005-02-27 19:37:20 - Message from server: Misconfigured BOINC installation or proxy-server problems!
But following it downloaded all necessary files.
-
CPDN had slot 0, LHC had slot 1. The installation of Einstein had not opened slot 2.
Now, crunching has switched from LHC to Einstein and suddenly is Einstein in slot 1, no slot for LHC.
It seems, all is in confusion.
Have i to detach and re-attach LHC and Einstein again?
wolmic
Now, one Hour later, crunching has switched from Einstein to LHC and has opened Slot 2 for LHC.
It seems, all is o.k.
Heureka !
Ric, I just got the same
)
Ric,
I just got the same message on my Laptop (Mac), only minutes ago. I found it was still crunching an old WU with a quite outdated App (4.74), apparently because the machine is switched off most of the time and quite busy with other things (compiling) when on. The Result must have been far beyond the deadline.
I stopped the client, deleted the min_rpc_time line from client_state.xml (well, it was deferring communication for 23h and I was a bit too impatient to wait that long) and started the client with --update_prefs to force a server contact. All worked well, it downloaded new work and the latest App. Resetting the project should have the same effect.
BM
BM
Okay, Thanks for the info
)
Okay, Thanks for the info folks.
When I posted the initial message I assumed, the error message was self explanatory. From the responses I've got obviously not as the others who've received similar error messages do not seem to have anything in common. To explain that comment a fuller explanation of the error is necessary.
I had not attached to Einstein before. I had just activated my account and was trying to make my initial attachment to the server.
After receiving the error, Boinc detached from Einstein and einstein was no longer in my project list.
As the others who've posted, seemed to think reattaching to the project I thought I might try it again ( I had tried it before with the same result).
The only thing I did differently this time was to include the space at the front of the account id that appeared in the email sending the attachment information.
I don't know whether it's significant but that space seems to have made a difference. Boinc is has downloaded various files and reporting Einstein as ready to run.
Ciao Ric
Well, detaching (manually or
)
Well, detaching (manually or automaticcally) and attaching (again) is even more drastic than resetting the project, but should achieve the same. I don't think that the blank made a difference, then.
BM
BM