VANISHED
6 Dec 2005 19:39:51 UTC
Topic 190310
(moderation:
Hi everyone, Well I thought I was up and running Einstein and Seti until the power went out during the night! The computer stays on, so, of course, it crashed.
All I can assume is that the crash made BOINC inoperative since the work I had done in both programs is gone. I just re-downloaded BOINC for the same two programs and am still getting the error msg that it cannot connect to the BOINC server. Says select computer, type localhost, and when I do I still get the same error message.
All help appreciated, Marianne
VANISHED
)
Check your firewall to make sure BOINC is allowed to connect to the internet.
Checked fire wall and
)
Checked fire wall and everything that says BOINC has full access
One error msg says BOINC
)
One error msg says BOINC manager not connected to BOINC client
RE: One error msg says
)
Exit BOINC (by right clicking on the icon in the System Tray), then try using the "Repair" option of the BOINC Installer program.
Marianne, Power outages
)
Marianne,
Power outages happen from time to time but it is quite unlikely that everything is gone or that BOINC is inoperative. Here is a checklist of things to look at to see what the situation really is. The important thing is not to panic and not to do things blindly without asking first. Chances are that the fix will be fairly easy.
* Open the GUI window and check each of the tabs "Projects", "Work", "Transfers" and "Messages". Tell us what you can see on each of those.
* Check the status message in the bottom right corner of the GUI window. It should say "Connected to localhost". If it says "Disconnected" then you need to attempt to make the connection. Use the "File" dropdown menu and click "Select computer ...". A dialog box will open and you can type in "localhost" and click OK. I don't think it will need a password but if it does just cut and paste the string that you can find in the file "gui_rpc_auth.cfg" in your BOINC folder.
* Once BOINC Manager is connected to the BOINC Daemon running in the background on your machine, all the "missing" stuff that you think you have lost should suddenly be there again.
* If this doesn't happen, it is possible that the power failure may have done damage to open files on your machine. Let's check the more likely things first though.
Normally, when BOINC starts up, the BOINC Daemon gets loaded in sufficient time for it to be able to respond to the Manager when the Manager tries to make the connection. When you get the message "not connected to client" it usually means that the Daemon (the client) wasn't ready (ie it started too slowly) when the Manager popped the question. This has been a problem in recent versions but it is supposed to be fixed in the version you are using (5.2.13). One of the factors is that Windows can be trying to start a heap of other stuff when your machine starts and this can cause the Daemon to start slowly. You might get more success by not trying to start automatically but do it manually by having a BOINC Manager Icon on your desktop to click after the traffic jam of the computer being powered on has cleared.
Please try the things listed here and report back. If you could copy and paste into your reply, the first 20 or so messages you get in your GUI messages window when you do a startup it would be very helpful to diagnose the problem if the problem persists.
Cheers,
Gary.