The Doctor may be suffering from hangovers with the DNS changes 14 days or so ago. Might be wise for him to flush his dns cache perhaps? That has worked for others. If that fails he could use a proxy. I'll find the thread with the details in. That may help too....as it has for others.

Edit: http://setiathome.berkeley.edu/forum_thread.php?id=18042 has some proxy info in it.

Regards

Ned, what do you think of the results on my trace? Something fishy towards the end, no?

Not really.

Reverse-DNS problems are pretty common, and unless we're talking mail servers, things will generall work with broken rDNS.

The ping times are reasonable.

Ok. Thanks. Just asking cause I don't remember seeing that come up before.

ok, last resort here.
I am powering off and clearing all dns and routing tables here at the lab and rebot from a cold start all routers, hubs, and computers. If that doesn't do it and everything else still works [like it does right now with no problems] them I am dumping boinc!

doc

Guys, I've been sort of following along here (mostly in my sleep) so if this isn't pertinent, please disregard and slap me around after I wake up. Running traceroute from my Linux machine to setiboincdata.ssl.berkeley.edu, it seems to stop at the same point mentioned,
"8 UC-Berkeley.demarc.cogentco.com (66.250.4.74) 70.477 ms 66.128 ms 67.650 ms"
but I don't have, or haven't had any connect problems at all.

Ned, what do you think of the results on my trace? Something fishy towards the end, no?

Not really.

Reverse-DNS problems are pretty common, and unless we're talking mail servers, things will generall work with broken rDNS.

The ping times are reasonable.

ok, here is the complete tracert log:

Unable to resolve target system name setiboincdata.ssl.berley.edu.

C:Documents and SettingsDr. D.H.Chevalier>tracert 66.28.250.125

Tracing route to 66.28.250.125 over a maximum of 30 hops

1

I am about to dump some 92 work units down the drain and regain computer power if Bonic doesn't get it's act together!

All I am running is SETI

doc

It might be good to look at the log for any hints as to why you have work waiting to upload.

It sounds like you're getting to the scheduler (on Berkeley's wire) but not to the upload/download servers (on the Cogent wire).

here is a portion of my message log:

8/10/2005 12:00:30 AM||schedule_cpus: must schedule
8/10/2005 12:00:31 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
8/10/2005 12:00:32 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
8/10/2005 12:14:03 AM|SETI@home|Started upload of 27oc03aa.19746.3280.834636.41_0_0
8/10/2005 12:14:24 AM|SETI@home|Temporarily failed upload of 27oc03aa.19746.3280.834636.41_0_0: -106
8/10/2005 12:14:24 AM|SETI@home|Backing off 1 hours, 45 minutes, and 14 seconds on upload of file 27oc03aa.19746.3280.834636.41_0_0
8/10/2005 12:50:30 AM|SETI@home|Started upload of 26fe05aa.10476.19728.709662.235_3_0
8/10/2005 12:50:52 AM|SETI@home|Temporarily failed upload of 26fe05aa.10476.19728.709662.235_3_0: -106
8/10/2005 12:50:52 AM|SETI@home|Backing off 2 hours, 52 minutes, and 23 seconds on upload of file 26fe05aa.10476.19728.709662.235_3_0
8/10/2005 12:53:47 AM|SETI@home|Started download of 26fe05aa.10476.26800.834662.85
8/10/2005 12:54:09 AM|SETI@home|Temporarily failed download of 26fe05aa.10476.26800.834662.85: -106
8/10/2005 12:54:09 AM|SETI@home|Backing off 2 hours, 35 minutes, and 49 seconds on download of file 26fe05aa.10476.26800.834662.85
8/10/2005 1:00:30 AM||schedule_cpus: time 3600.078125

doc

It isn't BOINC problem, it is a SETI BOINC problem. Consider re-allocating the CPU power to other BOINC projects which ARE running well. For me, that is Climate and Einstein, but there are another couple of projects as well.

I am about to dump some 92 work units down the drain and regain computer power if Bonic doesn't get it's act together!

All I am running is SETI

doc

Dr., not to be presuming anything, but have you looked at the messages as to why you can't upload? There have been a lot of problems, but that seems like a long time not to be able to upload. I don't have as many units as you do, but there has never been more than 24hrs of uploading problems on my end.

Yes, the messages only say, scheduling successful; however, nothing happens and the screen saver says no work unit (I.E. Bonic is idle)

doc

I’m not complaining but…

It seems to me that with the transitioner backlog now down to 0 hours that the in progress and waiting for validation numbers should be dropping. They are not, in fact those numbers are still rising. Without more information from the developers on what is happening at the Berkeley end a diagnosis is difficult. Are all our client computers simply overwhelming the old Berkeley servers with completed work units? Maybe! If this is so is there another solution other than Berkeley shutting down every Wednesday for 3 hours to do a database backup?[quote]

I observed that also, and agree there might be a problem.

[quote]Why are so many of our brothers and sisters having to resort to proxy’s to contact the Berkeley servers when they were not having problems before? Since there has been no info from Berkeley on this Tigher could you post on whether you and your helpers were able to figure anything out on this and your conclusions? I am very interested in this problem. Thanks!

Why did the cheerleaders get their pom-pom’s burned?

Bottom line is that I see a great need for one of the developers to post some information officially, on this site concerning problems and what is being planned to address those problems. And I mean posting at least 2 or 3 times per week. Not once every 6 to 8 weeks or longer as has been the custom with little to no real information. My feeling right now is that Berkeley, Boinc/Seti are operating like a person stumbling around in the dark with nowhere to go, no direction and no plan. Matt and JM7 are here almost every night posting and answering questions. They are very informative and greatly appreciated by us on the forums but I am sure they are here on their own time and not being compensated. An official source is needed with timely information on the problems being experienced in the system and the solutions.

And another thing…the plan to entice the crunchers at Classic to make the move here, now, is not going well. The suggestion is being taken as insulting at the Classic site as well it should be. If Berkeley is indeed waiting for the 2 billion mark for advertising and marketing purposes, maybe we should be going back to Classic and make that goal happen sooner. After all, we benefit from Classic’s demise, not the other way around. Something to think about!

I have 23 computers running or did run boinc. They have been waiting for 7 days to dump and reload work units. every other week this is the same problem.

I am about to dump some 92 work units down the drain and regain computer power if Bonic doesn't get it's act together!