Busy busy weekend, mostly for Jeff (I was beside a lake high up in the Sierras the past four days). Long story short, while the multibeam stuff worked in beta, there were some database-related problems when the same binaries were set forth in the public project, and Jeff/Eric had to iron these out. There's still some clean up to do on this front: we may be stopping/restarting things over the next day or so, and enacting more changes during the outage tomorrow. If all goes well, this will be seamless. We're still waiting on that official press release, so we have time to get all the initial kinks out.

On top of that, a couple of our data servers needed to be kicked around. There is increased load as the new client continues to be distributed and work is being generated at a faster rate, causing NFS to freak out - a problem we have dealt with many times in the past. Rebooting usually clears that up, but bruno once again needed to be physically power cycled and nobody was here at the lab to do so until the following morning. We're doing research into web-enabled power strips in case we need to do such things remotely in the future. The heavy load is also hitting our workunit file server pretty hard, so we're still choked on sending out new work which will probably be the case until demand subsides a bit. Please be patient.

I got a lot of web-based work ahead of me as far as updating server status pages, etc. to pick up the changes with the way the multibeam data files behave.

- 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

Thanks for the heads-up.. much appreciated. Hope we'll be crunching without server issues soon. I know you guys are doing your best to achieve that!

Greetings,
Sander

---

Big Time Thanks for the UPDATE MAtt - Nice Work across the Board All @ Berkeley . . .

Technical question. Since installing the latest 5.10.13? client on my WinXP Pro system, it no longer will run as a service (when not logged in). I have been running this way since it was first offered but now it only processes if I'm logged in. I disconnected and reconnected without success. I uninistalled and reinstalled, taking care to set it as a service with the Admin account info. It then ran as a service for a few days and then the service would stop again. I can go into the services and start it but it stops again within a minute or two.

I have checked all the settings, tried setting it as a System-level service, and setting it back to Administrator (with proper login info), yet it continues even after all the disconnects and uninstalls.

Anyone have any clues?

---

It should also be noted that Eric is on vacation for a couple weeks....

---

Matt, could someone kick beta so that reporting results is possible? I'm getting:


8/13/2007 6:51:00 PM|SETI@home Beta Test|Message from server: Project encountered internal error: shared memory

when reporting results.
Possibly a re-start could clear this up?

---

.

Hello, from Albany, CA!...

While Eric is away, he has been selected as the User of the Day for Beta

While Eric is away, he has been selected as the User of the Day for Beta

More like User of the Week. At least.

---

me@rescam.org