Now getting a different error from the server, but it's still preventing reporting results and downloading new work:

12/2/2008 8:14:43 AM Sending scheduler request: To fetch work. Requesting 1521479 seconds of work, reporting 21 completed tasks
12/2/2008 8:14:48 AM Scheduler request succeeded: got 0 new tasks
12/2/2008 8:14:48 AM Message from server: Server error: can't attach shared memory

---

Have you changed your settings to srv4?

If not try this.

message 57462

Note the correction - the new line should read:

<scheduler_url>http://srv4.boinc.bakerlab.org/rosetta_cgi/cgi</scheduler_url>

---

Well, that's a great fix if you have a couple of computers near you that you can perform the edits on, but I've got 20+ running all over the office and getting to each one to edit a few files would be pretty tough.

Any other suggestions?

---

Well, that's a great fix if you have a couple of computers near you that you can perform the edits on, but I've got 20+ running all over the office and getting to each one to edit a few files would be pretty tough.

Any other suggestions?

that is what the team recommended.
it is worth the hassle now to be able to properly communicate in the future.

Well, that's a great fix if you have a couple of computers near you that you can perform the edits on, but I've got 20+ running all over the office and getting to each one to edit a few files would be pretty tough.

Any other suggestions?

Yes. Try waiting a day (or more if the computers are not on overnight). BOINC seems to download the master file if it can't connect for a while.

Yes. Try waiting a day (or more if the computers are not on overnight). BOINC seems to download the master file if it can't connect for a while.

Exactly. BOINC will resolve the problem. It just goes through a few retries and timer delays before finding the new information. It eventually will fetch the "master file" again and then know to hit the new server.

---

Rosetta Moderator: Mod.Sense

Hope it does get the master file sooner or later, how are people who don't 'watch' their BOINC installations on a regular basis going to know to change these files?

---

Ok, I played around with some of my computers that hadn't fixed themselves yet, and I discovered that after 11 "project is down" messages, the next try will download the master file. It doesn't matter if the messages are from normal retries or from pressing update.

If you press update, you only need to wait until the "project is down" message appears in the messages tab. The usual 4 minute wait between requests doesn't apply here.

Can someone confirm if this works with other versions of BOINC? (I'm using 5.2.13)

I'm not getting the 'project is down' message. I'm getting the 'can't attach to shared memory' message.

---

Same here

I'm not getting the 'project is down' message. I'm getting the 'can't attach to shared memory' message.

---

This works for the 'can't attach to shared memory' problem as well. Just keep hitting the 'update' button.

---

Ok, I played around with some of my computers that hadn't fixed themselves yet, and I discovered that after 11 "project is down" messages, the next try will download the master file. It doesn't matter if the messages are from normal retries or from pressing update.

If you press update, you only need to wait until the "project is down" message appears in the messages tab. The usual 4 minute wait between requests doesn't apply here.

Can someone confirm if this works with other versions of BOINC? (I'm using 5.2.13)

With so old client it could be an idea to upgrade...

As for getting the new scheduler-url, BOINC-client since v3 (if not even earlier), will re-read the master-file if 10 failed connections. As "failed connection" doesn't only count instances there the server is down/unreachable, but also instances there client asks for work but scheduling-server doesn't give you any work 10 times in a row. So, most clients should get the new url after a few hours.

So, most users should have gotten the new url by now. If they've not got it, possible reasons are:
1; Then tried to download master-url the web-server was unreachable (the front-page, not the scheduling-server). If can't download the master-url, the BOINC-client will wait 24 hours before re-trying... For old clients, (don't remember exact version), the delay for failed master-url is 1 week...
2; Not sure if it's a problem for anyone, but as far as the web goes, it is possible client is getting served-up an old copy of front-page...

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

I'm not getting the 'project is down' message. I'm getting the 'can't attach to shared memory' message.

That must be a difference in BOINC versions. Mine gives the same "shared memory" error, followed by a "Project is down" message in red (which makes it easy to see).

I took the easier route,if you do not have any work units waiting to upload or report detach from the project then reattach and lo-and-behold problem solved now happily crunching away.

---

If you can't take a joke you should never have joined.

Nice fix everyone!

I'm back in action!

---

This fix worked for me on a G4 Mac dual 533...

---