http://setiweb.ssl.berkeley.edu/beta/ has gone AWOL. Usually during backup/outages the data driven pages are unavailable. This time I get the message:

Not Found
The requested URL /beta/ was not found on this server.

Apache/1.3.39 Server at setiweb.ssl.berkeley.edu Port 80

---

Sir Arthur C Clarke 1917-2008

http://setiweb.ssl.berkeley.edu/beta/ has gone AWOL. Usually during backup/outages the data driven pages are unavailable. This time I get the message:

Not Found
The requested URL /beta/ was not found on this server.

Apache/1.3.39 Server at setiweb.ssl.berkeley.edu Port 80

I saw that too about half an hour ago, but it seems to be back in operation now.

                                                               Joe

Thanks for pointing this out. This is now fixed. One of the replacement web servers wasn't config'ed right, so half the requests (randomly distributed between two servers) were breaking.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Now you've got the web server sorted out, could someone kick the business end, please?

I'm getting

17/10/2007 00:20:26|SETI@home Beta Test|Message from server: Project encountered internal error: shared memory

when I try to report completed Beta results.

Now you've got the web server sorted out, could someone kick the business end, please?

I'm getting

17/10/2007 00:20:26|SETI@home Beta Test|Message from server: Project encountered internal error: shared memory

when I try to report completed Beta results.

Restart Boinc, it fixes it sometimes.

17/10/2007 00:23:40|SETI@home Beta Test|Sending scheduler request: Requested by user
17/10/2007 00:23:40|SETI@home Beta Test|Requesting 173041 seconds of new work
17/10/2007 00:23:45|SETI@home Beta Test|Scheduler RPC succeeded [server version 509]
17/10/2007 00:23:45|SETI@home Beta Test|Deferring communication for 1 min 0 sec
17/10/2007 00:23:45|SETI@home Beta Test|Reason: no work from project


Claggy

---

Thanks for pointing this out. This is now fixed. One of the replacement web servers wasn't config'ed right, so half the requests (randomly distributed between two servers) were breaking.

- Matt

Thanks Matt, Working now.

Keith

Now you've got the web server sorted out, could someone kick the business end, please?

I'm getting

17/10/2007 00:20:26|SETI@home Beta Test|Message from server: Project encountered internal error: shared memory

when I try to report completed Beta results.

Restart Boinc, it fixes it sometimes.

17/10/2007 00:23:40|SETI@home Beta Test|Sending scheduler request: Requested by user
17/10/2007 00:23:40|SETI@home Beta Test|Requesting 173041 seconds of new work
17/10/2007 00:23:45|SETI@home Beta Test|Scheduler RPC succeeded [server version 509]
17/10/2007 00:23:45|SETI@home Beta Test|Deferring communication for 1 min 0 sec
17/10/2007 00:23:45|SETI@home Beta Test|Reason: no work from project

Claggy

It's on my octo, I lose ~20 mins crunch on three CPDNs every time I restart (long delay on checkpointing). I'll just hang on to the Beta WUs for now - they're not due until December. (and seriously, rebooting my client won't cure a selfish server that won't share its memory, it only gives me a better chance of working round it by hitting on the opposite parity scheduler. This one does need a project-side fix).

Now you've got the web server sorted out, could someone kick the business end, please?

I'm getting

17/10/2007 00:20:26|SETI@home Beta Test|Message from server: Project encountered internal error: shared memory

when I try to report completed Beta results.

Restart Boinc, it fixes it sometimes.

17/10/2007 00:23:40|SETI@home Beta Test|Sending scheduler request: Requested by user
17/10/2007 00:23:40|SETI@home Beta Test|Requesting 173041 seconds of new work
17/10/2007 00:23:45|SETI@home Beta Test|Scheduler RPC succeeded [server version 509]
17/10/2007 00:23:45|SETI@home Beta Test|Deferring communication for 1 min 0 sec
17/10/2007 00:23:45|SETI@home Beta Test|Reason: no work from project

Claggy

It's on my octo, I lose ~20 mins crunch on three CPDNs every time I restart (long delay on checkpointing). I'll just hang on to the Beta WUs for now - they're not due until December. (and seriously, rebooting my client won't cure a selfish server that won't share its memory, it only gives me a better chance of working round it by hitting on the opposite parity scheduler. This one does need a project-side fix).

Well, Boinc reported four times to Beta O.K, then got the Shared memory error
on the fifth attempt, so it works sometimes and not others, I've noticed there
would be repeated Shared memory error attempts, then one attempt works O.K,
Could it be the amount of traffic on Main/Beta?

Claggy

---

Well, Boinc reported four times to Beta O.K, then got the Shared memory error on the fifth attempt, so it works sometimes and not others, I've noticed there would be repeated Shared memory error attempts, then one attempt works O.K, Could it be the amount of traffic on Main/Beta?

Claggy

No, it's intrinsic to the server: either the server is working, or it isn't.

But there are two servers: often, one is working and the other one isn't. That seems to be the situation you're experiencing.

Well, Boinc reported four times to Beta O.K, then got the Shared memory error on the fifth attempt, so it works sometimes and not others, I've noticed there would be repeated Shared memory error attempts, then one attempt works O.K, Could it be the amount of traffic on Main/Beta?

Claggy

No, it's intrinsic to the server: either the server is working, or it isn't.

But there are two servers: often, one is working and the other one isn't. That seems to be the situation you're experiencing.

Well, couldn't report my last Beta WU, until i restarted Boinc, then reported
first time, see http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=2577543 , of course the next attempt got a S.M.E again!
Probably something about a restarted Boinc having less Baggage,
and so reports O.K, or something about timings of the actual reporting.

Claggy

---