Panic Mode On (26) Server problems

Message boards : Number crunching : Panic Mode On (26) Server problems
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 10 · 11 · 12 · 13

AuthorMessage
Profile hiamps
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 4292
Credit: 72,971,319
RAC: 0
United States
Message 951375 - Posted: 1 Dec 2009, 14:14:20 UTC

Is this problem Client wide or just the newer clients? None of my 6.1.0 compuyers have had even a slight delay in downloads from what I see. Seems the only thing not being discussed here. Are people with older clients also having the download problems?
Official Abuser of Boinc Buttons...
And no good credit hound!
ID: 951375 · Report as offensive
wulf 21

Send message
Joined: 18 Apr 09
Posts: 93
Credit: 26,337,213
RAC: 43
Germany
Message 951381 - Posted: 1 Dec 2009, 14:44:59 UTC - in response to Message 951369.  

I'm not sure if you meant me, because you didn't "reply" but used "post to thread".

However, I didn't say anything about any http_debug log; I only said that I expect the cricket graphs to be at 50% if only one of two servers is running.

And I answered to Sutaru's post, as you can easily see in the header line of my post.

Gruß,
Gundolf


No, I didn't mean you in particular, I was referring to the whole discussion: if the download doesn't work when the .13 IP is the first one for BOINC but the debug log tells that it has tried both servers, it must be wrong (i.e. the log tells how it is supposed to work, but it doesn't really work that way)
ID: 951381 · Report as offensive
Profile Gundolf Jahn

Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 446,358
RAC: 0
Germany
Message 951403 - Posted: 1 Dec 2009, 15:30:28 UTC - in response to Message 951375.  

Is this problem Client wide or just the newer clients? None of my 6.1.0 compuyers have had even a slight delay in downloads from what I see. Seems the only thing not being discussed here. Are people with older clients also having the download problems?

I didn't have problems either with my 5.8.16 and 5.10.45 clients. However, they only downladed a handful of tasks since Thanksgiving, so that might have been the luck of the draw.

Gruß,
Gundolf
ID: 951403 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 951441 - Posted: 1 Dec 2009, 16:48:14 UTC

I hope that today's outage puts an end to the download problems.....

Have we had any official response about the problem yet? There was no tech news from Matt yesterday.
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 951441 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 951445 - Posted: 1 Dec 2009, 16:58:36 UTC

I activated the hosts file workround overnight and while I was busy today, so I wouldn't feel obliged to kittysit the shrubbery.... I'll disable it again during maintenance, so I'll see what happens when they come back up.

No, I haven't heard anything from SETI admin, but I have a shrewd suspicion that the 'Panic' threads, especially one as busy as this one, is one of the few parts of the message boards that they monitor: and I think Pappa has sent off some emails. So I reckon they know.

I've reported the fact that BOINC can't cope with a failed server on round-robin DNS, and passed on a tip I received by PM that the underlying bug in libcurl may have fixed within the last three weeks. In a way, I rather hope that Matt doesn't fix it tonight, so we have something to test a BOINC resolution against! But I can see how that wouldn't appeal to everyone....

ID: 951445 · Report as offensive
Profile hiamps
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 4292
Credit: 72,971,319
RAC: 0
United States
Message 951448 - Posted: 1 Dec 2009, 17:00:37 UTC - in response to Message 951445.  

I activated the hosts file workround overnight and while I was busy today, so I wouldn't feel obliged to kittysit the shrubbery.... I'll disable it again during maintenance, so I'll see what happens when they come back up.

No, I haven't heard anything from SETI admin, but I have a shrewd suspicion that the 'Panic' threads, especially one as busy as this one, is one of the few parts of the message boards that they monitor: and I think Pappa has sent off some emails. So I reckon they know.

I've reported the fact that BOINC can't cope with a failed server on round-robin DNS, and passed on a tip I received by PM that the underlying bug in libcurl may have fixed within the last three weeks. In a way, I rather hope that Matt doesn't fix it tonight, so we have something to test a BOINC resolution against! But I can see how that wouldn't appeal to everyone....


So Richard is the bug at seti or in the new client?
Official Abuser of Boinc Buttons...
And no good credit hound!
ID: 951448 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 951451 - Posted: 1 Dec 2009, 17:07:26 UTC - in response to Message 951448.  

So Richard is the bug at seti or in the new client?

The failure is at SETI.

The bug which means that BOINC can't cope properly with the failure is in BOINC, and has been in BOINC for many, many versions. But it's actually in a section of code which BOINC didn't write themselves, but borrowed from somewhere else to save time.

The originators of that 'borrowed' code think they've fixed it. BOINC will have to get hold of the new code, test it, incorporate it into BOINC, and test it again: there won't be a new version of BOINC with the - hopefully fixed - code for at least a couple of days.

And then we'll have to wait for vader (the problematic SETI server) to fail again before we can really test it: that usually happens every nine months or so, so maybe next summer?
ID: 951451 · Report as offensive
Profile hiamps
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 4292
Credit: 72,971,319
RAC: 0
United States
Message 951455 - Posted: 1 Dec 2009, 17:18:00 UTC - in response to Message 951451.  

So Richard is the bug at seti or in the new client?

The failure is at SETI.

The bug which means that BOINC can't cope properly with the failure is in BOINC, and has been in BOINC for many, many versions. But it's actually in a section of code which BOINC didn't write themselves, but borrowed from somewhere else to save time.

The originators of that 'borrowed' code think they've fixed it. BOINC will have to get hold of the new code, test it, incorporate it into BOINC, and test it again: there won't be a new version of BOINC with the - hopefully fixed - code for at least a couple of days.

And then we'll have to wait for vader (the problematic SETI server) to fail again before we can really test it: that usually happens every nine months or so, so maybe next summer?


So why have I seen it only on my hosts with updated clients? I checked quite often and neither of my Q6700's even hickupped the last few days. The only machine that even seems to have the problem at all is my new Windows 7 machine. It is the only machine I have had to restart since Saturday morning....

Just like asking Smart guys questions...chance to learn something.
Official Abuser of Boinc Buttons...
And no good credit hound!
ID: 951455 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 951459 - Posted: 1 Dec 2009, 17:30:03 UTC - in response to Message 951455.  
Last modified: 1 Dec 2009, 17:30:37 UTC

So Richard is the bug at seti or in the new client?

The failure is at SETI.

The bug which means that BOINC can't cope properly with the failure is in BOINC, and has been in BOINC for many, many versions. But it's actually in a section of code which BOINC didn't write themselves, but borrowed from somewhere else to save time.

The originators of that 'borrowed' code think they've fixed it. BOINC will have to get hold of the new code, test it, incorporate it into BOINC, and test it again: there won't be a new version of BOINC with the - hopefully fixed - code for at least a couple of days.

And then we'll have to wait for vader (the problematic SETI server) to fail again before we can really test it: that usually happens every nine months or so, so maybe next summer?


So why have I seen it only on my hosts with updated clients? I checked quite often and neither of my Q6700's even hickupped the last few days. The only machine that even seems to have the problem at all is my new Windows 7 machine. It is the only machine I have had to restart since Saturday morning....

Just like asking Smart guys questions...chance to learn something.

From your other posts, you usually use v6.1.0, I think?

That's Crunch3r's unofficial build, which is actually v5.10.[not very many] underneath the hood. That's the many, many versions ago that I was referring to. I'll try and dig out an exact number from the source code during the outage.
ID: 951459 · Report as offensive
Profile Pappa
Volunteer tester
Avatar

Send message
Joined: 9 Jan 00
Posts: 2562
Credit: 12,301,681
RAC: 0
United States
Message 951474 - Posted: 1 Dec 2009, 22:25:09 UTC

The problem with .13 has been fixed and tested. Please remove any workarounds

Regards

Please consider a Donation to the Seti Project.

ID: 951474 · Report as offensive
Previous · 1 . . . 10 · 11 · 12 · 13

Message boards : Number crunching : Panic Mode On (26) Server problems


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.