Looks like moving the server was successful. Let us know if you're having any problems with connecting the BOINC clients (it has a new IP address).

Hopefully the new home for MilkyWay will be a bit more stable. It has better air conditioning and a few other things.

---

4/25/2011 2:10:35 PM Milkyway@home update requested by user
4/25/2011 2:10:37 PM Milkyway@home Sending scheduler request: Requested by user.
4/25/2011 2:10:37 PM Milkyway@home Reporting 12 completed tasks, not requesting new tasks
4/25/2011 2:10:59 PM Project communication failed: attempting access to reference site
4/25/2011 2:11:00 PM Internet access OK - project servers may be temporarily down.
4/25/2011 2:11:02 PM Milkyway@home Scheduler request failed: Couldn't connect to server

I guess I am having a problem connecting

No upload/download server.

Working here now.

---

4/25/2011 2:10:35 PM Milkyway@home update requested by user
4/25/2011 2:10:37 PM Milkyway@home Sending scheduler request: Requested by user.
4/25/2011 2:10:37 PM Milkyway@home Reporting 12 completed tasks, not requesting new tasks
4/25/2011 2:10:59 PM Project communication failed: attempting access to reference site
4/25/2011 2:11:00 PM Internet access OK - project servers may be temporarily down.
4/25/2011 2:11:02 PM Milkyway@home Scheduler request failed: Couldn't connect to server

I guess I am having a problem connecting

i don't know exactly when your client tried to make the above contact with the server b/c your client displays the local time, not UTC. what time zone are you in? i'm on Eastern Time (i'm in Sarasota, FL, USA), and i got the same "failed communication" messages from my client at 2:20PM local time (14:20 UTC). apparently my client had already previously tried to contact the server several times without success, b/c it didn't try to make contact for another 3 hours, at which point it was 5:20PM local time (17:20 UTC). but my client DID establish contact on that attempt.

long story short, you need to try to contact the server again.

No upload/download server.

i'm not sure that has anything to do with people not being able to get work, as counter-intuitive as that may seem. the upload/download server has been offline for a week now, maybe longer...and i haven't had trouble getting work in the mean time. perhaps i'm wrong about this, but it would be one hell of a coincidence if the upload/download server just happened to be down every time i check the server status, and went back up after i left the web page. if that wasn't what you were getting at, my apologies for the misunderstanding...

---

I just tried again and got the same messages.

All good and running here.

Vaughan

---

All running fine here since the server was back up! Boinc 6.12.22

Nowi

---

Everything fine here. Bonic Version 6.12.22.
Client switched automatic to backup project (Collatz prio 0) and also back to milkyway (prio 800) without user interaction :-)
Performance pretty much the same as before

All seems OK here

---

Don't drink water, that's the stuff that rusts pipes

I just tried again and got the same messages.

Same issue here!
Do we have to reset or detach and lose the completed wus to get this to work?

No, what is means is your ISP still has the old DNS record cached.

You can wait until it updates or try a different DNS server like google's 8.8.8.8

---

how do you try a different DSN server?

Will the main page of the website be up again soon as well?

how do you try a different DSN server?

The old DNS address will be cached, so when your app goes to get it, its the old one. It does update quickly, but there are times when it doesnt happen.

If you get caught by this - and it will update in the end with no intervention - you can flush the DNS cache, that forces the PC to go looking for the correct one, not just use the one sitting in the DNS cache.

To flush DNS is easy, but Win 7 sometimes moans about admin privelidges,

For XP:
1.Open up a command prompt (Start > Run > "cmd.exe" > OK).
2.Type in the command "ipconfig /flushdns"

For Win7
1.Click the start button and navigate to the command prompt (Start > All Programs > Accessories > Command Prompt)
2.Make sure that you right click on the command prompt application and choose "Run as Administrator"
3.Type in the command "ipconfig /flushdns"

Dont type the quotes with either method. Note the space between the letter g and /

That will flush the DNS cache, and force the PC to go looking for the correct one.

Regards
Zy

I don't know if this is the right place, but there is something that is bothering me.
Since about the 7th of April I do not accumulate credits and since April 11 my average credit dropped from over 500 to below 100. When I look at my account page all workunits show validation errors.
I'm running Ubuntu 10.10.
SETI, Einstein and Rosetta are running normally, so I wonder, am I running Milkyway for nothing at all?

I can see what looks to be the error, but I'll have to let the experts answer with a cure.

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
APP: error reading search parameters file (for read): data_file == NULL
BOINC_APP_VERSION: 0.18
BOINC_APP_NAME: speedimic_sse3_32
COMPILER: icpc (ICC) 11.0 20090131
Code-Optimizations by Gipsel
Compiled by speedimic
called boinc_finish

</stderr_txt>
]]>

---

Don't drink water, that's the stuff that rusts pipes

Old optimised applications using app_info.xml file no longer work. The server no longer sends a parameter file and will not accept results results coming in a file.

You will need to detach and reattach and download the standard application. It will possibly be much slower than the optimised speedimic_sse3_32 you were previously using.

Thanks Chris and kashi!

I detached an reattached the project. We'll see if that was the only thing :))
Is there btw a new optimised version?

---

No, the best app is the one you download normally.

The applications were updated, thats why you fell over as your app_info file points to old applications which no longer exist, and therefore your machine falls over.

Just detatching and reattatching will not solve the issue as your app_info is still there pointing at an application that doesnt exist. You should take out the app_info file, then detatct/reattatch - but please abort any unused WUs, else they hang around to timeout after a detatch/reattatch. By aborting them first, they then get recycled immediately and potential wingmen dont have to wait for your timeout and a recrunch.

There may be some trips and traps to the app from your end as you are running Linux (I'm Windows 7), so might be handy for a linux user to come in here if there is anything need doing.

But for sure, whatever the scenario, you must get rid of current app_info, else they will still error out.

Regards
Zy