I´m not able to DL or report.

---

Now that things are starting to work again for most, there are a few that are still having some issues. Remember that with this huge outage the traffic is still very high from all the machines banging on the doors. If you are having problems you may want to take the time to at least stop and restart BOINC, or better yet stop BOINC, reboot, and restart. This usually resolves most of the communication problems after outages like this.

---

I am suddenly getting this:

5/25/2007 11:47:52 AM|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.

---

Dublin, California
Team: SETI.USA

I am suddenly getting this:

5/25/2007 11:47:52 AM|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.

me too on main
mayby some side efect of sql server crash a few mins ago ?

---

I am suddenly getting this:

5/25/2007 11:47:52 AM|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.

me too on main
mayby some side efect of sql server crash a few mins ago ?

Me Three 25/05/2007 19:52:21|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.

I thought for a second it could be an effect of installing BOINC 5.9.12 At least I am not alone in getting this problem.

Keith

I too got:-

25/05/2007 20:23:08|SETI@home Beta Test|Sending scheduler request: Requested by user
25/05/2007 20:23:08|SETI@home Beta Test|(not requesting new work or reporting completed tasks)
25/05/2007 20:23:13|SETI@home Beta Test|Scheduler RPC succeeded [server version 509]
25/05/2007 20:23:13|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.
25/05/2007 20:23:13|SETI@home Beta Test|Deferring communication for 1 hr 0 min 0 sec
25/05/2007 20:23:13|SETI@home Beta Test|Reason: requested by project

I also got the following when accessing both BETA and MAIN

Warning: mysql_pconnect() [function.mysql-pconnect]: Link to server lost, unable to reconnect in /disks/setifiler1/home/boincadm/projects/beta/html/inc/db.inc on line 22
Unable to connect to database - please try again later Error:

I think there's a database problem as on main I cannot access my results as the DB is "offline"

The expression "it never rains but it pours comes to mind.

Good luck to the team at Seti for fixing it!

I am suddenly getting this:

5/25/2007 11:47:52 AM|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.

Got the same message at 3:01 PM EDT, now I'm getting the dreaded HTTP error (see log snip below):

5/25/2007 4:21:27 PM|SETI@home Beta Test|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi
5/25/2007 4:21:27 PM|SETI@home Beta Test|Reason: To report completed tasks
5/25/2007 4:21:27 PM|SETI@home Beta Test|Reporting 4 tasks
5/25/2007 4:21:32 PM|SETI@home Beta Test|Scheduler request failed: HTTP internal server error
5/25/2007 4:21:32 PM|SETI@home Beta Test|Deferring scheduler requests for 27 minutes and 18 seconds

---

!!Stupidity should be PAINFUL!!

I also got the following when accessing both BETA and MAIN

Warning: mysql_pconnect() [function.mysql-pconnect]: Link to server lost, unable to reconnect in /disks/setifiler1/home/boincadm/projects/beta/html/inc/db.inc on line 22
Unable to connect to database - please try again later Error:

Good luck to the team at Seti for fixing it!

I should have said "............BETA and MAIN web sites"

Looks like scheduler connects work again. But I am still get no AP WUs. Has anybody got a AP WU today ?

---

...But I am still get no AP WUs. Has anybody got a AP WU today ?

No, there are no AP workunits at the moment. Remember, the last split produced only about 500 workunits.
I know you want to test your Mac-AP-app, don't you.

---

_\|/_
U r s

I too am amongst those receiving the:

5/28/2007 7:38:17 PM|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.


I have "Update"-ed preferences, BOINC 5.4.11, and while I am able to clear the problem for SETI Main - I am unable to clear the problem for SETI Beta/Astropulse. Good to note; however, that while BOINC is claiming not to recognize my access to Beta, the Forums still do, as evidenced by my being able to access my preferences and the ability to post... WEIRD!!!

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I was getting that from the main project. Then my results got thru. Now I'm getting that message again.

---

me@rescam.org

I am suddenly getting this:

5/25/2007 11:47:52 AM|SETI@home Beta Test|Message from server: Can't find host record Invalid or missing account key. Visit this project's web site to get an account key.

Have you noticed a side effect of this? A host that gets that message will show in the B.M. Statistics tab a graph that ends in 0.0 credit.

Clearly a data-base disconnect issue.

Some one was in on the 28'th working on it. But no joy.

(The 28'th is a U.S.A holiday, what dedication: thanks!)

Getting these now, something broken?

6/1/2007 2:37:25 PM|SETI@home Beta Test|Scheduler request failed: server returned nothing (no headers, no data)
6/1/2007 2:37:25 PM|SETI@home Beta Test|Deferring communication for 6 min 25 sec
6/1/2007 2:37:25 PM|SETI@home Beta Test|Reason: scheduler request failed

---

Anyone else getting the no headers error (see snip below - all times EDT)?

6/4/2007 10:05:46 AM|SETI@home Beta Test|Sending scheduler request: To fetch work
6/4/2007 10:05:46 AM|SETI@home Beta Test|Requesting 8261 seconds of new work, and reporting 2 completed tasks
6/4/2007 10:05:47 AM||Project communication failed: attempting access to reference site
6/4/2007 10:05:48 AM||Access to reference site succeeded - project servers may be temporarily down.
6/4/2007 10:05:51 AM|SETI@home Beta Test|Scheduler request failed: server returned nothing (no headers, no data)
6/4/2007 10:05:51 AM|SETI@home Beta Test|Deferring communication for 1 min 6 sec
6/4/2007 10:05:51 AM|SETI@home Beta Test|Reason: scheduler request failed

Started sporadically last night and consistently since 10:00 AM EDT today.

---

!!Stupidity should be PAINFUL!!

I had to shutdown Boinc and reboot system before mine would upload. Went as soon as I came back up.

Anyone else getting the no headers error (see snip below - all times EDT)?

6/4/2007 10:05:46 AM|SETI@home Beta Test|Sending scheduler request: To fetch work
6/4/2007 10:05:46 AM|SETI@home Beta Test|Requesting 8261 seconds of new work, and reporting 2 completed tasks
6/4/2007 10:05:47 AM||Project communication failed: attempting access to reference site
6/4/2007 10:05:48 AM||Access to reference site succeeded - project servers may be temporarily down.
6/4/2007 10:05:51 AM|SETI@home Beta Test|Scheduler request failed: server returned nothing (no headers, no data)
6/4/2007 10:05:51 AM|SETI@home Beta Test|Deferring communication for 1 min 6 sec
6/4/2007 10:05:51 AM|SETI@home Beta Test|Reason: scheduler request failed

Started sporadically last night and consistently since 10:00 AM EDT today.

LTDInvestments... welcome..!!
I hope you will enjoy beta.


My linux box is getting some work, but mostly after seeing some

Scheduler request failed: server returned nothing (no headers, no data)

Boinc version 5.8.16

No need to reboot I think, problem seems to be server-sided.
Malaria and Docking are responding perfect on the same pc.

;-)

---

Having the same problem, even after rebooting.

6/5/2007 8:03:58 AM|SETI@home Beta Test|Sending scheduler request: Requested by user
6/5/2007 8:03:58 AM|SETI@home Beta Test|Reporting 1 tasks
6/5/2007 8:03:59 AM||Project communication failed: attempting access to reference site
6/5/2007 8:04:00 AM||Access to reference site succeeded - project servers may be temporarily down.
6/5/2007 8:04:03 AM|SETI@home Beta Test|Scheduler request failed: server returned nothing (no headers, no data)
6/5/2007 8:04:03 AM|SETI@home Beta Test|Deferring communication for 1 min 0 sec
6/5/2007 8:04:03 AM|SETI@home Beta Test|Reason: scheduler request failed

---

[color= blue][u]SETI@home classic workunits = 5,906 with CPU time of 60,377 hours[/u][/color]